From: <iodophlymiaelo@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: raw aio write guarantee
Date: Wed, 28 Sep 2005 09:42:50 -0700 [thread overview]
Message-ID: <98b62faa05092809423ac837bc@mail.gmail.com> (raw)
In-Reply-To: <200509280923.j8S9Nkgq028579@turing-police.cc.vt.edu>
On 9/28/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Wed, 28 Sep 2005 01:56:05 PDT, iodophlymiaelo@gmail.com said:
>
> > I was asking what a user-application can do to prevent data loss, not
> > an application-user.
>
> Right. However, if you actually care about the distinction between "made it
> to the disk cache" and "made it to the platter", those are things you'll
> want to address - in particular, if you have one of the evil disk drives
> I mentioned, there's very little a user application can do to work around it.
>
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 ;-)
next prev parent reply other threads:[~2005-09-28 16:42 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 [this message]
2005-09-28 20:13 ` Kyle Moffett
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=98b62faa05092809423ac837bc@mail.gmail.com \
--to=iodophlymiaelo@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--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