LKML Archive on
help / color / mirror / Atom feed
* Re: Fix(es) for ext2 fsync bug
       [not found] <20070214195453.GB7521@nifty>
@ 2007-02-14 21:08 ` sfaibish
  0 siblings, 0 replies; only message in thread
From: sfaibish @ 2007-02-14 21:08 UTC (permalink / raw)
  To: Valerie Henson, linux-fsdevel
  Cc: Can Sar, Junfeng Yang, Dawson Engler, Theodore Ts'o, kernel list


Maybe it is not only our (FS people) problem. We probably need to
bring the kernel people judge as ext2 and ext3 are the base Linux FS.
I add the kernel list for opinion.


On Wed, 14 Feb 2007 14:54:54 -0500, Valerie Henson  
<> wrote:

> Just some quick notes on possible ways to fix the ext2 fsync bug that
> eXplode found.  Whether or not anyone will bother to implement it is
> another matter.
> Background: The eXplode file system checker found a bug in ext2 fsync
> behavior.  Do the following: truncate file A, create file B which
> reallocates one of A's old indirect blocks, fsync file B.  If you then
> crash before file A's metadata is all written out, fsck will complete
> the truncate for file A... thereby deleting file B's data.  So fsync
> file B doesn't guarantee data is on disk after a crash.  Details:
> Two possible solutions I can think of:
> * Rearrange order of duplicate block checking and fixing file size in
>   fsck.  Not sure how hard this is. (Ted?)
> * Keep a set of "still allocated on disk" block bitmaps that gets
>   flushed whenever a sync happens.  Don't allocate these blocks.
>   Journaling file systems already have to do this.
> -VAL
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel"  
> in
> the body of a message to
> More majordomo info at

Using Opera's revolutionary e-mail client:

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-02-14 22:03 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20070214195453.GB7521@nifty>
2007-02-14 21:08 ` Fix(es) for ext2 fsync bug sfaibish

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).