System information

Note
Although an fsck. xfs binary is present in the xfsprogs package, this is present only to
satisfy initscripts that look for an fsck. filesystem binary at boot time. fsck. xfs
immediately exits with an exit code of 0.
Another thing to be aware of is that older xfsprogs packages contain an xfs_check tool. This
tool is very slow and does not scale well for large filesystems. As such, it has been depreciated
in favor of xfs_repai r -n.
A clean log on a filesystem is required for xfs_repai r to operate. If the filesystem was not cleanly
unmounted, it should be mounted and unmounted prior to using xfs_repai r. If the log is corrupt
and cannot be replayed, the -L option may be used to zero the log.
Important
The -L option must only be used if the log cannot be replayed. The option discards all
metadata updates in the log and will result in further inconsistencies.
It is possible to run xfs_repai r in a dry run, check-only mode by using the -n option. No changes
will be made to the filesystem when this option is specified.
xfs_repai r takes very few options. Commonly used options include:
-n
No modify mode. Check-only operation.
-L
Z ero metadata log. Use only if log cannot be replayed with mount.
-m maxmem
Limit memory used during run to maxmem MB. 0 can be specified to obtain a rough estimate
of the minimum memory required.
-l lo g d ev
Specify the external log device, if present.
All options for xfs_repai r are specified in the xfs_repai r(8) manual page.
The following eight basic phases are performed by xfs_repai r while running:
1. Inode and inode blockmap (addressing) checks.
2. Inode allocation map checks.
3. Inode size checks.
4. Directory checks.
5. Pathname checks.
Red Hat Ent erprise Lin ux 6 St orage Admin ist rat io n G uide
88