From: Jan Kara <jack@suse.cz>
To: armangau_philippe@emc.com
Cc: jakj@j-a-k-j.com, jack@suse.cz, ric@popimap.lss.emc.com,
ext3-users@redhat.com, linux-ext4@vger.kernel.org,
csar@stanford.edu
Subject: Re: Ext3 behavior on power failure
Date: Wed, 28 Mar 2007 17:00:03 +0200 [thread overview]
Message-ID: <20070328150003.GE29587@duck.suse.cz> (raw)
In-Reply-To: <A74E8B4A356D8143B79BBEB839421F300415A86B@CORPUSMX20B.corp.emc.com>
On Wed 28-03-07 10:17:33, armangau_philippe@emc.com wrote:
> In my case the disk cache is not a problem - We use an emc disk array
> the write cache is protected -
> Once the data has made over the disk array we can assume it is safe -
Then if you are able to reproduce the situation that not all data
is written after fsync(); poweroff; that is a bug worth reporting..
Honza
>
> -----Original Message-----
> From: John Anthony Kazos Jr. [mailto:jakj@j-a-k-j.com]
> Sent: Wednesday, March 28, 2007 9:17 AM
> To: Jan Kara
> Cc: wheeler, richard; armangau, philippe; ext3-users@redhat.com;
> linux-ext4@vger.kernel.org; csar@stanford.edu
> Subject: Re: Ext3 behavior on power failure
>
> > 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?
>
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2007-03-28 14:53 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 [this message]
2007-04-18 21:49 ` Bruno Wolff III
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=20070328150003.GE29587@duck.suse.cz \
--to=jack@suse.cz \
--cc=armangau_philippe@emc.com \
--cc=csar@stanford.edu \
--cc=ext3-users@redhat.com \
--cc=jakj@j-a-k-j.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ric@popimap.lss.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).