On Tuesday 22 January 2008, Al Boldi wrote: > Chris Mason wrote: > > Running fsync in data=ordered means that all of the dirty blocks on the > > FS will get written before fsync returns. > > Hm, that's strange, I expected this kind of behaviour from data=journal. > > data=writeback should return immediatly, which seems it does, but > data=ordered should only wait for metadata flush, it shouldn't wait for > filedata flush. Are you sure it waits for both?
I over simplified. data=ordered means that all data blocks are written before the metadata that references them commits. So, if you add 1GB to a fileA in a transaction and then run fsync(fileB) in the same transaction, the 1GB from fileA is sent to disk (and waited on) before the fsync on fileB returns. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
