Red Hat GFS 6.0 -, Administrator'S Manual

Page: 123 / 192

Chapter 9. Managing GFS 109
File
Specifies the file from which to get information.
The
gfs_tool
command provides additional action flags (options) not listed in this section. For more
information about other
gfs_tool
action flags, refer to the
gfs_tool
man page.
9.11.2. Examples
This example reports extended file system usage about file system
/gfs
.
gfs_tool df /gfs
This example reports extended file status about file
/gfs/datafile
.
gfs_tool stat /gfs/datafile
9.12. Repairing a File System
When nodes fail with the file system mounted, file system journaling allows fast recovery. However, if
a storage device loses power or is physically disconnected, file system corruption may occur. (Journal-
ing cannot be used to recover from storage subsystem failures.) When that type of corruption occurs,
the GFS file system can be recovered by using the
gfs_fsck
command.
The
gfs_fsck
command must only be run on a file system that is unmounted from all nodes.
Note
On nodes running Red Hat GFS 6.0 for Red Hat Enterprise Linux 3 Update 5 and later, the
gfs_fsck
command has changed from previous releases of Red Hat GFS in the following ways:
•
You can no longer set the interactive mode with [Ctrl]-[C]. Pressing [Ctrl]-[C] now cancels the
gfs_fsck
command. Do not press [Ctr]-[C] unless you want to cancel the command.
•
You can increase the level of verbosity by using the
-v
flag. Adding a second
-v
flag increases the
level again.
•
You can decrease the level of verbosity by using the
-q
flag. Adding a second
-q
flag decreases
the level again.
•
The
-n
option opens a file system as read-only and answers no to any queries automatically.
The option provides a way of trying the command to reveal errors without actually allowing the
gfs_fsck
command to take effect.
Refer to the
gfs_fsck
man page,
gfs_fsck(8)
, for additional information about other command
options.
9.12.1. Usage
gfs_fsck
-y
BlockDevice