testing/util-linux
SHA256
3
0
Fork 0
forked from pool/util-linux
Code Pull Requests Activity
737b1a31db
util-linux/util-linux-ng-2.19.1-barrier_documentation.patch
Marcus Meissner 1806747cca Accepting request 226509 from home:sbrabec:branches:Base:System 
- Merge fixes and features from SLE11 (bnc#831868):
  * Detect squashfs version <= 3 as squashfs3 and version >= 4 as
    squashfs. (mszeredi@suse.cz,
    util-linux-ng-2.16-squashfs3-detect.patch, bnc#666893)
  * add sfdisk-warn-about-2TB-limit.patch (puzel@novell.com,
    bnc#495657)
  * Document barrier option in mount.8 (jack@suse.cz,
    hvogel@suse.de,
    util-linux-ng-2.19.1-barrier_documentation.patch, bnc#489740)
  * lscpu: improve hypervisor detection (puzel@novell.com,
    fate#310255)
    - util-linux-lscpu-improve-hypervisor-detection.patch
  * umount: avoid calling readlink on mountpoints if not necessary
    - add: umount-avoid-readlink.patch (puzel@suse.com, bnc#794529)
  * fix file conflict between util-linux and s390-32
    (puzel@suse.com, bnc#805684)
  * util-linux-update-default-commit-interval.patch:
    mount(8): update default commit interval (puzel@suse.com,
    bnc#809480)
  * Obsolete no more packaged uuid-runtime.
- Add uname26 (util-linux-setarch-uname26.patch, FATE#313476).

OBS-URL: https://build.opensuse.org/request/show/226509
OBS-URL: https://build.opensuse.org/package/show/Base:System/util-linux?expand=0&rev=227
2014-03-20 08:19:43 +00:00

132 lines
7.0 KiB
Diff
Raw Blame History

From: Jan Kara <jack@suse.cz>
Subject: Update documentation of mount(8) about barrier mount options
Signed-off-by: Jan Kara <jack@suse.cz>
Index: util-linux-2.24.1/sys-utils/mount.8
===================================================================
--- util-linux-2.24.1.orig/sys-utils/mount.8
+++ util-linux-2.24.1/sys-utils/mount.8
@@ -1524,12 +1524,13 @@ ordered mode.
Abort the journal if an error occurs in a file data buffer in ordered mode.
.TP
.BR barrier=0 " / " barrier=1 "
-This enables/disables barriers. barrier=0 disables it, barrier=1 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 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.
+This disables / enables the use of write barriers in the jbd code. barrier=0
+disables, barrier=1 enables (default). This also requires an IO stack which can
+support barriers, and if jbd gets an error on a barrier write, it will disable
+barriers again with a warning. Write barriers enforce proper on-disk ordering
+of journal commits, making volatile disk write caches safe to use, at some
+performance penalty. If your disks are battery-backed in one way or another,
+disabling barriers may safely improve performance.
.TP
.BI commit= nrsec
Sync all data and metadata every
@@ -1577,15 +1578,9 @@ enabled older kernels cannot mount the d
This will enable 'journal_checksum' internally.
.TP
.BR barrier=0 " / " barrier=1 " / " barrier " / " nobarrier
-This enables/disables the use of write barriers in the jbd code. barrier=0
-disables, barrier=1 enables. This also requires an IO stack which can support
-barriers, and if jbd gets an error on a barrier write, it will disable again
-with a warning. Write barriers enforce proper on-disk ordering of journal
-commits, making volatile disk write caches safe to use, at some performance
-penalty. If your disks are battery-backed in one way or another, disabling
-barriers may safely improve performance. The mount options "barrier" and
-"nobarrier" can also be used to enable or disable barriers, for consistency
-with other ext4 mount options.
+These mount options have the same effect as in ext3. The mount options
+"barrier" and "nobarrier" are added for consistency with other ext4 mount
+options.
The ext4 filesystem enables write barriers by default.
.TP
@@ -2266,13 +2261,13 @@ Enable POSIX Access Control Lists. See t
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
+This disables / enables the use of write barriers in the journaling code.
+barrier=none disables, barrier=flush enables (default). This also requires an
+IO stack which can support barriers, and if reiserfs gets an error on a barrier
+write, it will disable barriers again with a warning. 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.
+safe to use, at some performance penalty. If your disks are battery-backed in
+one way or another, disabling barriers may safely improve performance.
.SH "Mount options for romfs"
None.
Index: util-linux-2.24.1/mount-deprecated/mount.8
===================================================================
--- util-linux-2.24.1.orig/mount-deprecated/mount.8
+++ util-linux-2.24.1/mount-deprecated/mount.8
@@ -1389,12 +1389,13 @@ in files after a crash and journal recov
.RE
.TP
.BR barrier=0 " / " barrier=1 "
-This enables/disables barriers. barrier=0 disables it, barrier=1 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 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.
+This disables / enables the use of write barriers in the jbd code. barrier=0
+disables, barrier=1 enables (default). This also requires an IO stack which can
+support barriers, and if jbd gets an error on a barrier write, it will disable
+barriers again with a warning. Write barriers enforce proper on-disk ordering
+of journal commits, making volatile disk write caches safe to use, at some
+performance penalty. If your disks are battery-backed in one way or another,
+disabling barriers may safely improve performance.
.TP
.BI commit= nrsec
Sync all data and metadata every
@@ -1433,15 +1434,9 @@ enabled older kernels cannot mount the d
This will enable 'journal_checksum' internally.
.TP
.BR barrier=0 " / " barrier=1 " / " barrier " / " nobarrier
-This enables/disables the use of write barriers in the jbd code. barrier=0
-disables, barrier=1 enables. This also requires an IO stack which can support
-barriers, and if jbd gets an error on a barrier write, it will disable again
-with a warning. Write barriers enforce proper on-disk ordering of journal
-commits, making volatile disk write caches safe to use, at some performance
-penalty. If your disks are battery-backed in one way or another, disabling
-barriers may safely improve performance. The mount options "barrier" and
-"nobarrier" can also be used to enable or disable barriers, for consistency
-with other ext4 mount options.
+These mount options have the same effect as in ext3. The mount options
+"barrier" and "nobarrier" are added for consistency with other ext4 mount
+options.
The ext4 filesystem enables write barriers by default.
.TP
@@ -2099,13 +2094,13 @@ Enable POSIX Access Control Lists. See t
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
+This disables / enables the use of write barriers in the journaling code.
+barrier=none disables, barrier=flush enables (default). This also requires an
+IO stack which can support barriers, and if reiserfs gets an error on a barrier
+write, it will disable barriers again with a warning. 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.
+safe to use, at some performance penalty. If your disks are battery-backed in
+one way or another, disabling barriers may safely improve performance.
.SH "Mount options for romfs"
None.
View Git Blame Copy Permalink