1fsck.gfs2(8) System Manager's Manual fsck.gfs2(8)
2
6 fsck.gfs2 - Offline GFS and GFS2 file system checker
7
10 fsck.gfs2 [OPTION]... DEVICE
11
14 All computers must have the filesystem unmounted before running
15 fsck.gfs2. Failure to unmount from all nodes in a cluster will likely
16 result in filesystem corruption.
17
20 fsck.gfs2 will check that the GFS or GFS2 file system on a device is
21 structurally valid. It should not be run on a mounted file system. If
22 file system corruption is detected, it will attempt to repair the file
23 system. There is a limit to what fsck.gfs2 can do. If important file
24 system structures are destroyed, such that the checker cannot determine
25 what the repairs should be, reparations could fail.
26 GFS2 is a journaled file system, and as such should be able to repair
28 damage to the file system on its own. However, faulty hardware has the
29 ability to write incomplete blocks to a file system thereby causing
30 corruption that GFS2 cannot fix. The first step to ensuring a healthy
31 file system is the selection of reliable hardware (i.e. storage systems
32 that will write complete blocks - even in the event of power failure).
33 Note: Most file system checkers will not check the file system if it is
35 "clean" (i.e. unmounted since the last use). The fsck.gfs program
36 behaves differently because the storage may be shared among several
37 nodes in a cluster, and therefore problems may have been introduced on
38 a different computer. Therefore, fsck.gfs2 will always check the file
39 system unless the -p (preen) option is used, in which case it follows
40 special rules (see below).
41 fsck.gfs2 will log to the system log on start and exit to aid debugging
43 and administration.
44
46 -a Same as the -p (preen) option.
47 -f Force checking even if the file system seems clean.
49 -h Help.
51 This prints out the proper command line usage syntax.
53 -q Quiet.
55 -n No to all questions.
57 By specifying this option, fsck.gfs2 will only show the changes
59 that would be made, but not make any changes to the filesystem.
60 -p Preen (same as -a: automatically repair the file system if it is
62 dirty, and safe to do so, otherwise exit.)
63 Note: If the file system has locking protocol lock_nolock, the
65 file system is considered a non-shared storage device and the
66 fsck is deemed safe. However, fsck.gfs2 does not know whether
67 it was called automatically from the init process, due to
68 options in the /etc/fstab file. Therefore, if the locking pro‐
69 tocol is lock_dlm and -a or -p was specified, fsck.gfs2 cannot
70 determine whether the disk is mounted by other nodes in the
71 cluster. Therefore, the fsck is deemed to be unsafe and a warn‐
72 ing is given if any damage or dirty journals are found. In that
73 case, the file system should be unmounted from all nodes in the
74 cluster and fsck.gfs2 should be run manually without the -a or
75 -p options.
76 -V Version.
78 Print out the program version information.
80 -v Verbose operation.
82 Print more information while running.
84 -y Yes to all questions.
86 By specifying this option, fsck.gfs2 will not prompt before mak‐
88 ing changes.
89 fsck.gfs2(8)