[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A74E8B4A356D8143B79BBEB839421F300415A86B@CORPUSMX20B.corp.emc.com>
Date: Wed, 28 Mar 2007 10:17:33 -0400
From: armangau_philippe@....com
To: <jakj@...-k-j.com>, <jack@...e.cz>
Cc: <ric@...imap.lss.emc.com>, <ext3-users@...hat.com>,
<linux-ext4@...r.kernel.org>, <csar@...nford.edu>
Subject: RE: Ext3 behavior on power failure
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 -
Thx
Philippe
-----Original Message-----
From: John Anthony Kazos Jr. [mailto:jakj@...-k-j.com]
Sent: Wednesday, March 28, 2007 9:17 AM
To: Jan Kara
Cc: wheeler, richard; armangau, philippe; ext3-users@...hat.com;
linux-ext4@...r.kernel.org; csar@...nford.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?
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists