http://bugzilla.kernel.org/show_bug.cgi?id=14354 --- Comment #82 from Alexey Fisher <bug-track@xxxxxxxxxxxxxxxxx> 2009-10-17 15:23:20 --- I double checking it now, but is seems to be this patch: commit 91ac6f43317c0bf99969665f98016548011dfa38 Author: Frank Mayhar <fmayhar@xxxxxxxxxx> Date: Wed Sep 9 22:33:47 2009 -0400 ext4: Make non-journal fsync work properly Teach ext4_write_inode() and ext4_do_update_inode() about non-journal mode: If we're not using a journal, ext4_write_inode() now calls ext4_do_update_inode() (after getting the iloc via ext4_get_inode_loc()) with a new "do_sync" parameter. If that parameter is nonzero _and_ we're not using a journal, ext4_do_update_inode() calls sync_dirty_buffer() instead of ext4_handle_dirty_metadata(). This problem was found in power-fail testing, checking the amount of loss of files and blocks after a power failure when using fsync() and when not using fsync(). It turned out that using fsync() was actually worse than not doing so, possibly because it increased the likelihood that the inodes would remain unflushed and would therefore be lost at the power failure. Signed-off-by: Frank Mayhar <fmayhar@xxxxxxxxxx> Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx> -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
