This patch removes a note that the barrier option is automatically turned off if the underlaying device doesn't support I/O barriers. So far I understand it's default on, means "barriers" option is applied which should not make any problems if the underlaying device supports something or not. There is by the kernel or gfs2-utils no automatically detection going on which changes this mount option. However there could be third party software which has an automatically detection but this isn't part of kernel or gfs2-utils collection and the user is running out of scope of this manpage entry.
Additional this patch adds a point at the end of the manpage section entry which seems to be missing. Signed-off-by: Alexander Aring <aahri...@redhat.com> --- gfs2/man/gfs2.5 | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/gfs2/man/gfs2.5 b/gfs2/man/gfs2.5 index 8f67ce23..38d97bb1 100644 --- a/gfs2/man/gfs2.5 +++ b/gfs2/man/gfs2.5 @@ -127,11 +127,10 @@ in kernel version 2.6.30 and above. .TP \fBbarrier\fP This option, which defaults to on, causes GFS2 to send I/O barriers -when flushing the journal. The option is automatically turned off -if the underlying device does not support I/O barriers. We highly -recommend the use of I/O barriers with GFS2 at all times unless -the block device is designed so that it cannot lose its write cache -content (e.g. its on a UPS, or it doesn't have a write cache) +when flushing the journal. We highly recommend the use of I/O barriers +with GFS2 at all times unless the block device is designed so that it +cannot lose its write cache content (e.g. its on a UPS, or it doesn't +have a write cache). .TP \fBcommit=\fP\fIsecs\fR This is similar to the ext3 \fBcommit=\fP option in that it sets -- 2.26.3
