diff options
| author | Eric Sandeen <sandeen@redhat.com> | 2008-05-26 18:29:46 +0200 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2008-05-26 18:29:46 +0200 |
| commit | 571640cad3fda6475da45d91cf86076f1f86bd9b (patch) | |
| tree | a97ff3da9b60251c68358cd000c217cb37915ea2 /lib/klist.c | |
| parent | jbd2: Fix barrier fallback code to re-lock the buffer head (diff) | |
| download | linux-571640cad3fda6475da45d91cf86076f1f86bd9b.tar.xz linux-571640cad3fda6475da45d91cf86076f1f86bd9b.zip | |
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>
Diffstat (limited to 'lib/klist.c')
0 files changed, 0 insertions, 0 deletions