From: Torrey Hoffman <thoffman@arnor.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"'Oliver S.'" <Follow.Me@gmx.net>
Subject: RE: questions regarding Journalling-FSes and w-cache reordering
Date: 09 Apr 2003 14:35:55 -0700 [thread overview]
Message-ID: <1049924154.5404.26.camel@torrey.et.myrio.com> (raw)
In-Reply-To: <1049919134.10871.5.camel@dhcp22.swansea.linux.org.uk>
On Wed, 2003-04-09 at 13:12, Alan Cox wrote:
> On Mer, 2003-04-09 at 20:52, Mudama, Eric wrote:
> > ATA hard drives are allowed to reorder/merge/etc their write caches if write
> > cache is enabled. With write caching enabled, there is no guarantee that
> > dirty data will be flushed in any specific order, nor does the ATA protocol
> > support any such ordering beyond the global flush cache command.
>
> To cheer people up further by the way, not all ATA drives support cache
> flush, some drives dont support write cache disable and others implement
> write/verify as write.
Can anyone recommend some decent 120 GB or larger IDE drives which don't
play these games?
I'd like to build a reliable ~1 TB RAID 5 from IDE drives. I will
gladly give up performance for high reliability and low cost.
My current 240 GB RAID 5 is built from five 60 GB Maxtor IDEs, with a
Reiser FS on it. I use hdparm to disable write cache... unless Maxtor
ignores that? Does anyone know? I can check the exact model numbers
of the drives if it matters.
Is there documentation anywhere that says which drives cut corners?
Any other suggestions on how to build a cheap but reliable RAID?
Thanks in advance,
--
Torrey Hoffman <thoffman@arnor.net>
next prev parent reply other threads:[~2003-04-09 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 19:52 Mudama, Eric
2003-04-09 20:12 ` Alan Cox
2003-04-09 21:35 ` Torrey Hoffman [this message]
2003-04-10 17:39 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 19:33 Oliver S.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1049924154.5404.26.camel@torrey.et.myrio.com \
--to=thoffman@arnor.net \
--cc=Follow.Me@gmx.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®