From: Bruno Wolff III <bruno@wolff.to>
To: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>
Cc: csar@stanford.edu, linux-ext4@vger.kernel.org,
Jan Kara <jack@suse.cz>,
ext3-users@redhat.com, Ric Wheeler <ric@emc.com>
Subject: Re: Ext3 behavior on power failure
Date: Wed, 18 Apr 2007 16:49:04 -0500 [thread overview]
Message-ID: <20070418214904.GA10541@wolff.to> (raw)
In-Reply-To: <alpine.DEB.0.83.0703280915400.30460@sigma.j-a-k-j.com>
On Wed, Mar 28, 2007 at 09:17:27 -0400,
"John Anthony Kazos Jr." <jakj@j-a-k-j.com> wrote:
> > If you fsync() your data, you are guaranteed that also your data are
> >safely on disk when fsync returns. So what is the question here?
>
> Pardon a newbie's intrusion, but I do know this isn't true. There is a
> window of possible loss because of the multitude of layers of caching,
> especially within the drive itself. Unless there is a super_duper_fsync()
> that is able to actually poll the hardware and get a confirmation that the
> internal buffers are purged?
That is why you need to disable write caching of the drives or use cache
flushes via write barriers (if the stack of block devices all support them)
if the hardware cache isn't battery backed or the device doesn't support
returning the status of particular commands.
Of course nothing is perfectly safe.
next prev parent reply other threads:[~2007-04-18 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A74E8B4A356D8143B79BBEB839421F3004023496@CORPUSMX20B.corp.emc.com>
2007-03-23 10:47 ` Ext3 behavior on power failure Ric Wheeler
2007-03-28 12:40 ` Jan Kara
2007-03-28 13:17 ` John Anthony Kazos Jr.
2007-03-28 13:29 ` Jan Kara
2007-03-28 14:17 ` armangau_philippe
2007-03-28 15:00 ` Jan Kara
2007-04-18 21:49 ` Bruno Wolff III [this message]
2007-03-28 23:00 ` Ric Wheeler
2007-03-29 8:00 ` Jan Kara
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=20070418214904.GA10541@wolff.to \
--to=bruno@wolff.to \
--cc=csar@stanford.edu \
--cc=ext3-users@redhat.com \
--cc=jack@suse.cz \
--cc=jakj@j-a-k-j.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ric@emc.com \
/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).