Re: [Ext2-devel] Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11)

2005-03-07 Thread Junfeng Yang
Thanks a lot Andreas. Your message clarifies everything. > In ext3 this case is handled because the filesystem won't reallocate the > metadata blocks freed from file A before they have been committed to disk. > Also, the operations on file A are guaranteed to complete before or with >

Re: [Ext2-devel] Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11)

2005-03-07 Thread Andreas Dilger
On Mar 07, 2005 14:55 -0800, Junfeng Yang wrote: > > fsync on ext2 only really guarantees that the data has reached > > the disk, what the disk does it outside the realm of the fs. > > If the ide drive has write back caching enabled, the data just > > might only be in cache. If the power is

Re: [Ext2-devel] Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11)

2005-03-07 Thread Andreas Dilger
On Mar 07, 2005 14:55 -0800, Junfeng Yang wrote: fsync on ext2 only really guarantees that the data has reached the disk, what the disk does it outside the realm of the fs. If the ide drive has write back caching enabled, the data just might only be in cache. If the power is removed right

Re: [Ext2-devel] Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11)

2005-03-07 Thread Junfeng Yang
Thanks a lot Andreas. Your message clarifies everything. In ext3 this case is handled because the filesystem won't reallocate the metadata blocks freed from file A before they have been committed to disk. Also, the operations on file A are guaranteed to complete before or with operations on