Messages in this thread | | | Date | Mon, 7 Mar 2005 16:25:27 -0800 (PST) | From | Junfeng Yang <> | Subject | Re: [Ext2-devel] Re: [CHECKER] crash after fsync causing serious FS corruptions (ext2, 2.6.11) |
| |
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 file B so fsync(B) will also cause the changes from A to > be flushed to disk at the same time (this is guaranteed to complete before > fsync(B) returns).
In order words, each fsync essentailly triggers a jbd commit, right?
-Junfeng
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |