From: Kyle Moffett <mrmacman_g4@mac.com>
To: iodophlymiaelo@gmail.com
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
linux-kernel@vger.kernel.org
Subject: Re: raw aio write guarantee
Date: Wed, 28 Sep 2005 16:13:04 -0400 [thread overview]
Message-ID: <7F0D0031-D142-4231-A162-014137051DB1@mac.com> (raw)
In-Reply-To: <98b62faa05092809423ac837bc@mail.gmail.com>
On Sep 28, 2005, at 12:42:50, iodophlymiaelo@gmail.com wrote:
> Erm, is the hardware problem really as great as you're implying?
> Have you personally encountered any bad drives made by reputable
> brands? Mostly I've only heard only of people crying wolf and then
> realizing it was a problem with their reasoning or with the
> assumption that fsync() actually works properly on kernel X, where
> X doesn't even have to be that ancient a version of linux ;-)
No, I've seen several sample cases on this list of drives where the
IDE or SCSI cache flush commands did not trigger any disk activity
and the only way to force it out of the cache was to write several
meg of garbage to some file. In some cases (Like RAID cards with
good battery backup, for example), they may ignore the flush cache
command as it isn't really useful (although on such good cards, they
usually haw a way to turn it off, too).
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$ L++++(+
++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+++ t+(+
++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r !y?(-)
------END GEEK CODE BLOCK------
prev parent reply other threads:[~2005-09-28 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 7:12 raw aio write guarantee iodophlymiaelo
2005-09-28 7:57 ` Valdis.Kletnieks
2005-09-28 8:56 ` iodophlymiaelo
2005-09-28 9:23 ` Valdis.Kletnieks
2005-09-28 16:42 ` iodophlymiaelo
2005-09-28 20:13 ` Kyle Moffett [this message]
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=7F0D0031-D142-4231-A162-014137051DB1@mac.com \
--to=mrmacman_g4@mac.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=iodophlymiaelo@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).