MAN page from OpenSuSE gfs2-utils-3.1.9-lp152.3.5.x86_64.rpm
Section: Maintenance Commands (8)Index
fsck.gfs2 - Offline GFS and GFS2 file system checker
All computers must
have the filesystem unmounted before runningfsck.gfs2. Failure to unmount from all nodes in a cluster will likely resultin filesystem corruption.
fsck.gfs2 will check that the GFS or GFS2 file system on a device is structurally valid.It should not be run on a mounted file system. If file system corruption isdetected, it will attempt to repair the file system. There is a limit to whatfsck.gfs2 can do. If important file system structures are destroyed, such thatthe checker cannot determine what the repairs should be, reparations couldfail.
GFS2 is a journaled file system, and as such should be able to repair damage tothe file system on its own. However, faulty hardware has the ability to writeincomplete blocks to a file system thereby causing corruption that GFS2 cannotfix. The first step to ensuring a healthy file system is the selection ofreliable hardware (i.e. storage systems that will write complete blocks - evenin the event of power failure).
Note: Most file system checkers will not check the file system if it is"clean" (i.e. unmounted since the last use). The fsck.gfs program behavesdifferently because the storage may be shared among several nodes in acluster, and therefore problems may have been introduced on a differentcomputer. Therefore, fsck.gfs2 will always check the file system unlessthe -p (preen) option is used, in which case it follows special rules(see below).
fsck.gfs2 will log to the system log on start and exit to aid debugging andadministration.
- Same as the -p (preen) option.
- Force checking even if the file system seems clean.
This prints out the proper command line usage syntax.
- No to all questions.
By specifying this option, fsck.gfs2 will only show the changes thatwould be made, but not make any changes to the filesystem.
- Preen (same as -a: automatically repair the file system if it is dirty,and safe to do so, otherwise exit.)
Note: If the file system has locking protocol lock_nolock, the file systemis considered a non-shared storage device and the fsck is deemed safe.However, fsck.gfs2 does not know whether it was called automaticallyfrom the init process, due to options in the /etc/fstab file. Therefore, ifthe locking protocol is lock_dlm and -a or -p was specified, fsck.gfs2cannot determine whether the disk is mounted by other nodes in the cluster.Therefore, the fsck is deemed to be unsafe and a warning is givenif any damage or dirty journals are found. In that case, the file systemshould be unmounted from all nodes in the cluster and fsck.gfs2 should berun manually without the -a or -p options.
Print out the program version information.
- Verbose operation.
Print more information while running.
- Yes to all questions.
By specifying this option, fsck.gfs2 will not prompt before makingchanges.
This document was created byman2html,using the manual pages.