Jan Kara wrote: > On Wed 14-01-09 11:35:50, Eric Sandeen wrote: >> Jan Kara wrote: >>> To be really safe that the data hit the platter, we should also flush drive's >>> writeback caches on fsync and for O_SYNC files or O_DIRSYNC inodes. >> Seems sane, but aren't we getting really divergent behavior here between >> ext2, ext3, and ext4 w.r.t. drive cache flushing for sync paths? > Well, but ext3/4 should do a barrier on a transaction commit (if the user > really cares about data integrity) and hence it implicitely does the same. > > Honza Sorry, just now catching up with that other thread, which addresses this topic. :) But yes, this seems correct... (OTOH, I thought SuSE was carrying a patch which did add this blkdev_flush to sync for ext3...) -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
