On Fri, 19 Dec 2008, Yan Zheng wrote: > > I noticed some data and metadata getting out of sync on disk, despite > > wrapping my writes with btrfs transactions. After digging into it a bit, > > it appears to be a larger problem with inode size/data getting written > > during a regular commit. > > [...] > > This is the desired behaviour of data=ordered. Btrfs transaction commit > don't flush data, and metadata wont get updated until data IO complete. > > http://article.gmane.org/gmane.comp.file-systems.btrfs/869/match=new+data+ordered+code Ah, right, so it is. I think what I'm looking for then is a mount mode to get the old behavior, such that each commit flushes previously written data. Probably a call to btrfs_wait_ordered_extents() in btrfs_commit_transaction(), or something along those lines... sage -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
