1fsck.gfs2(8)                System Manager's Manual               fsck.gfs2(8)
2
3
4

NAME

6       fsck.gfs2 - Offline GFS and GFS2 file system checker
7
8

SYNOPSIS

10       fsck.gfs2 [OPTION]... DEVICE
11
12

WARNING

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
18

DESCRIPTION

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
27       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
34       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
42       fsck.gfs2 will log to the system log on start and exit to aid debugging
43       and administration.
44

OPTIONS

46       -a     Same as the -p (preen) option.
47
48       -f     Force checking even if the file system seems clean.
49
50       -h     Help.
51
52              This prints out the proper command line usage syntax.
53
54       -q     Quiet.
55
56       -n     No to all questions. By specifying this option,  fsck.gfs2  will
57              only  show  the  changes  that  would  be made, but not make any
58              changes to the filesystem.
59
60              This option may not be used with the -y or -p/-a options.
61
62       -p     Automatically repair ("preen") the file system if  it  is  dirty
63              and safe to do so, otherwise exit.
64
65              If  the file system has locking protocol lock_nolock, it is con‐
66              sidered a non-shared storage device and it is  considered  safe.
67              If  the locking protocol is lock_dlm and -a or -p was specified,
68              the check is  considered  unsafe  as  it  cannot  be  determined
69              whether the device is mounted by other nodes in the cluster.  In
70              this case a warning is given if any damage or dirty journals are
71              found.  The  file system should then be unmounted from all nodes
72              in the cluster and fsck.gfs2 should be run manually without  the
73              -a or -p options.
74
75              This option may not be used with the -n or -y options.
76
77       -V     Print out the program version information.
78
79       -v     Verbose operation.
80
81              Print more information while running.
82
83       -y     Yes  to all questions. By specifying this option, fsck.gfs2 will
84              not prompt before making changes.
85
86              This option may not be used with the -n or -p/-a options.
87
88
89
90                                                                  fsck.gfs2(8)