On Thu, 15 November 2007 18:59:19 -0800, Andrew Morton wrote: > On Fri, 16 Nov 2007 11:47:27 +0900 Hisashi Hifumi <hifumi.hisashi@xxxxxxxxxxxxx> wrote: > > > Currently fdatasync is identical to fsync in ext3,4. > > I think fdatasync should skip journal flush in data=ordered and data=writeback mode > > because this syscall is not required to synchronize the metadata. > > I suppose so. Although one wonders what earthly point there is in syncing > a file's data if we haven't yet written out the metadata which is required > for locating that data. > > IOW, fdatasync() is only useful if the application knows that it is overwriting > already-instantiated blocks. > > In which case it might as well have used fsync(). For ext2-style filesystems, > anyway. fsync() will sync an inode even if only i_atime was changed. fdatasync() would ignore such changes. I guess atime was the major reason for creating fdatasync() in the first place. The patch I sent you just minutes ago sorta documents this. I_DIRTY_DATASYNC was added with patch-2.4.0-test12 for just this reason. So basically an application can almost always use fdatasync() instead of fsync() and rely on the kernel to only cut corners, if doing so will not endanger the data synced to disk. Jörn -- Joern's library part 6: http://www.gzip.org/zlib/feldspar.html - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
