Oh ok. I read this in the man page and assumed that it's on by default: flushoncommit, noflushoncommit (default: on)
This option forces any data dirtied by a write in a prior transaction to commit as part of the current commit. This makes the committed state a fully consistent view of the file system from the application’s perspective (i.e., it includes all completed file system operations). This was previously the behavior only when a snapshot was created. Disabling flushing may improve performance but is not crash-safe. Maybe this needs a correction? On Fri, Aug 4, 2017 at 12:52 PM, Adam Borowski <kilob...@angband.pl> wrote: > On Fri, Aug 04, 2017 at 12:15:12PM +0530, Shyam Prasad N wrote: >> Is flushoncommit not a default option on version >> 4.4? Do I need specifically set this option? > > It's not the default. > > -- > ⢀⣴⠾⠻⢶⣦⠀ What Would Jesus Do, MUD/MMORPG edition: > ⣾⠁⢰⠒⠀⣿⡁ • multiplay with an admin char to benefit your mortal > ⢿⡄⠘⠷⠚⠋⠀ • abuse item cloning bugs (the five fishes + two breads affair) > ⠈⠳⣄⠀⠀⠀⠀ • use glitches to walk on water -- -Shyam -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html