|
 |
35732a |
commit f81fd07bdf8cf9f87c603754e3e5b89ed5445bf8
|
|
|
35732a |
Author: Andrew Price <anprice@redhat.com>
|
|
|
35732a |
Date: Thu Oct 17 13:12:31 2019 +0100
|
|
|
35732a |
|
|
|
35732a |
fsck.gfs2(8): Manpage updates
|
|
|
35732a |
|
|
|
35732a |
- Improve style consistency with the other manpages
|
|
|
35732a |
- Remove an unnecessary paragraph that gives a misleading impression of
|
|
|
35732a |
gfs2's device atomicity requirements (rhbz#1693000)
|
|
|
35732a |
- Add "See Also" section
|
|
|
35732a |
- "fsck.gfs" -> "fsck.gfs2"
|
|
|
35732a |
- Various other language tweaks
|
|
|
35732a |
|
|
|
35732a |
Signed-off-by: Andrew Price <anprice@redhat.com>
|
|
|
35732a |
|
|
|
35732a |
diff --git a/gfs2/man/fsck.gfs2.8 b/gfs2/man/fsck.gfs2.8
|
|
|
35732a |
index b2b326fb..9e9f9250 100644
|
|
|
35732a |
--- a/gfs2/man/fsck.gfs2.8
|
|
|
35732a |
+++ b/gfs2/man/fsck.gfs2.8
|
|
|
35732a |
@@ -1,11 +1,11 @@
|
|
|
35732a |
.TH fsck.gfs2 8
|
|
|
35732a |
|
|
|
35732a |
.SH NAME
|
|
|
35732a |
-fsck.gfs2 - Offline GFS and GFS2 file system checker
|
|
|
35732a |
+fsck.gfs2 - offline GFS and GFS2 file system checker
|
|
|
35732a |
|
|
|
35732a |
.SH SYNOPSIS
|
|
|
35732a |
.B fsck.gfs2
|
|
|
35732a |
-[\fIOPTION\fR]... \fIDEVICE\fR
|
|
|
35732a |
+[\fIoptions\fR] \fIdevice\fR
|
|
|
35732a |
|
|
|
35732a |
.SH WARNING
|
|
|
35732a |
All computers \fImust\fP have the filesystem unmounted before running
|
|
|
35732a |
@@ -13,30 +13,22 @@ fsck.gfs2. Failure to unmount from all nodes in a cluster will likely result
|
|
|
35732a |
in filesystem corruption.
|
|
|
35732a |
|
|
|
35732a |
.SH DESCRIPTION
|
|
|
35732a |
-fsck.gfs2 will check that the GFS or GFS2 file system on a device is structurally valid.
|
|
|
35732a |
-It should not be run on a mounted file system. If file system corruption is
|
|
|
35732a |
-detected, it will attempt to repair the file system. There is a limit to what
|
|
|
35732a |
-fsck.gfs2 can do. If important file system structures are destroyed, such that
|
|
|
35732a |
-the checker cannot determine what the repairs should be, reparations could
|
|
|
35732a |
-fail.
|
|
|
35732a |
+fsck.gfs2 will check that the GFS or GFS2 file system on a device is
|
|
|
35732a |
+structurally valid. It should not be run on a mounted file system. If file
|
|
|
35732a |
+system corruption is detected, it will attempt to repair the file system.
|
|
|
35732a |
+There is a limit to what fsck.gfs2 can do. If important file system structures
|
|
|
35732a |
+are destroyed, such that the checker cannot determine what the repairs should
|
|
|
35732a |
+be, reparations could fail.
|
|
|
35732a |
|
|
|
35732a |
-GFS2 is a journaled file system, and as such should be able to repair damage to
|
|
|
35732a |
-the file system on its own. However, faulty hardware has the ability to write
|
|
|
35732a |
-incomplete blocks to a file system thereby causing corruption that GFS2 cannot
|
|
|
35732a |
-fix. The first step to ensuring a healthy file system is the selection of
|
|
|
35732a |
-reliable hardware (i.e. storage systems that will write complete blocks - even
|
|
|
35732a |
-in the event of power failure).
|
|
|
35732a |
-
|
|
|
35732a |
-Note: Most file system checkers will not check the file system if it is
|
|
|
35732a |
-"clean" (i.e. unmounted since the last use). The fsck.gfs program behaves
|
|
|
35732a |
-differently because the storage may be shared among several nodes in a
|
|
|
35732a |
-cluster, and therefore problems may have been introduced on a different
|
|
|
35732a |
-computer. Therefore, fsck.gfs2 will always check the file system unless
|
|
|
35732a |
-the -p (preen) option is used, in which case it follows special rules
|
|
|
35732a |
+Other file system checkers will not check the file system if it is "clean"
|
|
|
35732a |
+(i.e. unmounted since the last use). With gfs2, storage may be shared among
|
|
|
35732a |
+several nodes in a cluster, and therefore problems may have been introduced on
|
|
|
35732a |
+a different computer. Therefore, fsck.gfs2 will always check the file system
|
|
|
35732a |
+unless the -p (preen) option is used, in which case it follows special rules
|
|
|
35732a |
(see below).
|
|
|
35732a |
|
|
|
35732a |
-fsck.gfs2 will log to the system log on start and exit to aid debugging and
|
|
|
35732a |
-administration.
|
|
|
35732a |
+fsck.gfs2 will log a message to the system log on start and exit to aid
|
|
|
35732a |
+debugging and administration.
|
|
|
35732a |
.SH OPTIONS
|
|
|
35732a |
.TP
|
|
|
35732a |
\fB-a\fP
|
|
|
35732a |
@@ -86,3 +78,8 @@ Yes to all questions. By specifying this option, fsck.gfs2 will not prompt befor
|
|
|
35732a |
changes.
|
|
|
35732a |
|
|
|
35732a |
This option may not be used with the \fB-n\fP or \fB-p\fP/\fB-a\fP options.
|
|
|
35732a |
+
|
|
|
35732a |
+.SH SEE ALSO
|
|
|
35732a |
+.BR gfs2 (5),
|
|
|
35732a |
+.BR gfs2_jadd (8),
|
|
|
35732a |
+.BR gfs2_grow (8)
|