ext4: enable barriers by default
authorEric Sandeen <sandeen@redhat.com>
Mon, 26 May 2008 16:29:46 +0000 (12:29 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Mon, 26 May 2008 16:29:46 +0000 (12:29 -0400)
commit571640cad3fda6475da45d91cf86076f1f86bd9b
treea97ff3da9b60251c68358cd000c217cb37915ea2
parent034772b068be62a79470d6c1b81b01fbe27793ac
ext4: enable barriers by default

I can't think of any valid reason for ext4 to not use barriers when
they are available;  I believe this is necessary for filesystem
integrity in the face of a volatile write cache on storage.

An administrator who trusts that the cache is sufficiently battery-
backed (and power supplies are sufficiently redundant, etc...)
can always turn it back off again.

SuSE has carried such a patch for ext3 for quite some time now.

Also document the mount option while we're at it.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Mingming Cao <cmm@us.ibm.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Documentation/filesystems/ext4.txt
fs/ext4/super.c