diff options
| author | Jan Kara | 2010-01-13 18:07:33 +0100 |
|---|---|---|
| committer | Karel Zak | 2010-01-22 10:34:00 +0100 |
| commit | 701094844451477c68d9503a5d4926f6493d9ddd (patch) | |
| tree | 7ebc4118a7b9d8e5344d6a2426d828deda6ff69f /mount/mount.8 | |
| parent | namei: fix man page formatting (diff) | |
| download | kernel-qcow2-util-linux-701094844451477c68d9503a5d4926f6493d9ddd.tar.gz kernel-qcow2-util-linux-701094844451477c68d9503a5d4926f6493d9ddd.tar.xz kernel-qcow2-util-linux-701094844451477c68d9503a5d4926f6493d9ddd.zip | |
mount: update documentation about barrier mount options
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'mount/mount.8')
| -rw-r--r-- | mount/mount.8 | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/mount/mount.8 b/mount/mount.8 index 217071ec5..2888b46d9 100644 --- a/mount/mount.8 +++ b/mount/mount.8 @@ -1267,7 +1267,11 @@ in files after a crash and journal recovery. .TP .BR barrier=0 " / " barrier=1 " This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. -The ext3 filesystem does not enable write barriers by default. +Write barriers enforce proper on-disk ordering of journal commits, making +volatile disk write caches safe to use, at some performance penalty. The ext3 +filesystem does not enable write barriers by default. Be sure to enable +barriers unless your disks are battery-backed one way or another. Otherwise +you risk filesystem corruption in case of power failure. .TP .BI commit= nrsec Sync all data and metadata every @@ -1932,6 +1936,15 @@ manual page. Enable POSIX Access Control Lists. See the .BR acl (5) manual page. +.TP +.BR barrier=none " / " barrier=flush " +This enables/disables the use of write barriers in the journaling code. +barrier=none disables it, barrier=flush enables it. Write barriers enforce +proper on-disk ordering of journal commits, making volatile disk write caches +safe to use, at some performance penalty. The reiserfs filesystem does not +enable write barriers by default. Be sure to enable barriers unless your disks +are battery-backed one way or another. Otherwise you risk filesystem +corruption in case of power failure. .SH "Mount options for romfs" None. |