gfs_fsck - Offline GFS file system checker

gfs_fsck [OPTION]... DEVICE

All GFS nodes must have the GFS filesystem unmounted before running gfs_fsck. Failure to unmount all nodes may result in filesystem corruption.

gfs_fsck will check that the GFS file system on a device is structurally valid. It should not be run on a mounted file system. If file system corruption is detected, it will attempt to repair the file system. There is a limit to what gfs_fsck can do. If important file system structures are destroyed, such that the checker can not determine what the repairs should be, reparations could fail.

GFS is a journaled file system, and as such should be able to repair damages to the file system on its own. However, faulty hardware has the ability to write incomplete blocks to a file system thereby causing corruption that GFS can not fix. The first step to ensuring a healthy file system is the selection of reliable hardware (i.e. storage systems that will write complete blocks - even in the event of power failure).

-h

Help.

This prints out the proper command line usage syntax.

-n

No to all questions.

By specifying this option, gfs_fsck will only show the changes that would be made, not make any changes to the filesystem.

-q

Quiet.

-V

Version.

Print out the current version name.

-v

Verbose operation.

Print more information while running.

-y

Yes to all questions.

By specifying this option, gfs_fsck will not prompt before making changes.