<3>xfs_repair<1> [ <3>-nLvVd<1> ] [ <3>-o<1> subopt[=value] ]
	[<3>-l<1> logdev] [<3>-r<1> rtdev] xfs_special
 .8v
<3>xfs_repair<1> <3>-f<1> [ <3>-nLvVd<1> ] [ <3>-o<1> subopt[=value] ]
	[<3>-l<1> logfile] [<3>-r<1> rtfile] file

-f

Specifies that the special device is actually a file (see the <2>mkfs.xfs<1> <3>-d<1> <2>file<1> option). This might happen if an image copy of a filesystem has been copied or written into an ordinary file. This option implies that any external log or realtime section is also in an ordinary file.

-L

Force Log Zeroing. Forces xfs_repair to zero the log even if it is dirty (contains metadata changes). When using this option the filesystem will likely appear to be corrupt, and can cause the loss of user files and/or data.

-l

Specifies the device special file where the filesystem's external log resides. Only for those filesystems which use an external log. See the <2>mkfs.xfs<1> <3>-l<1> option, and refer to xfs(5) for a detailed description of the XFS log.

-r

Specifies the device special file where the filesystem's realtime section resides. Only for those filesystems which use a realtime section. See the <2>mkfs.xfs<1> <3>-r<1> option, and refer to xfs(5) for a detailed description of the XFS realtime section.

-n

No modify mode. Specifies that xfs_repair should not modify the filesystem but should only scan the filesystem and indicate what repairs would have been made.

-o

Override what the program might conclude about the filesystem if left to its own devices. The assume_xfs suboption specifies that the filesystem is an XFS filesystem. Normally, if xfs_repair cannot find an XFS superblock, it checks to see if the filesystem is an EFS filesystem before it tries to regenerate the XFS superblock. If the assume_xfs option is in effect, xfs_repair will assume that the filesystem is an XFS filesystem and will ignore an EFS superblock if one is found.

-v

Verbose output.

-d

Repair dangerously. Allow xfs_repair to repair an XFS filesystem mounted read only. This is typically done on a root fileystem from single user mode, immediately followed by a reboot. Checks Performed Inconsistencies corrected include the following:

1.

Inode and inode blockmap (addressing) checks: bad magic number in inode, bad magic numbers in inode blockmap blocks, extents out of order, incorrect number of records in inode blockmap blocks, blocks claimed that are not in a legal data area of the filesystem, blocks that are claimed by more than one inode.

2.

Inode allocation map checks: bad magic number in inode map blocks, inode state as indicated by map (free or in-use) inconsistent with state indicated by the inode, inodes referenced by the filesystem that do not appear in the inode allocation map, inode allocation map referencing blocks that do not appear to contain inodes.

3.

Size checks: number of blocks claimed by inode inconsistent with inode size, directory size not block aligned, inode size not consistent with inode format.

4.

Directory checks: bad magic numbers in directory blocks, incorrect number of entries in a directory block, bad freespace information in a directory leaf block, entry pointing to an unallocated (free) or out of range inode, overlapping entries, missing or incorrect dot and dotdot entries, entries out of hashvalue order, incorrect internal directory pointers, directory type not consistent with inode format and size.

5.

Pathname checks: files or directories not referenced by a pathname starting from the filesystem root, illegal pathname components.

6.

Link count checks: link counts that do not agree with the number of directory references to the inode.

7.

Freemap checks: blocks claimed free by the freemap but also claimed by an inode, blocks unclaimed by any inode but not appearing in the freemap.

8.

Super Block checks: total free block and/or free i-node count incorrect, filesystem geometry inconsistent, secondary and primary superblocks contradictory.

Orphaned files and directories (allocated, in-use but unreferenced) are reconnected by placing them in the lost+found directory. The name assigned is the inode number. Disk Errors xfs_repair aborts on most disk I/O errors. Therefore, if you are trying to repair a filesystem that was damaged due to a disk drive failure, steps should be taken to ensure that all blocks in the filesystem are readable and writeable before attempting to use xfs_repair to repair the filesystem. A possible method is using dd(8) to copy the data onto a good disk. lost+found The directory lost+found does not have to already exist in the filesystem being repaired. If the directory does not exist, it is automatically created. If the <2>lost+found<1> directory already exists, the <2>lost+found<1> directory is deleted and recreated every time <2>xfs_repair<1> runs. This ensures that there are no name conflicts in <2>lost+found<1>. However, if you rename a file in <2>lost+found<1> and leave it there, if <2>xfs_repair<1> is run again, that file is renamed back to its inode number. Corrupted Superblocks XFS has both primary and secondary superblocks. <2>xfs_repair<1> uses information in the primary superblock to automatically find and validate the primary superblock against the secondary superblocks before proceeding. Should the primary be too corrupted to be useful in locating the secondary superblocks, the program scans the filesystem until it finds and validates some secondary superblocks. At that point, it generates a primary superblock. Quotas If quotas are in use, it is possible that <2>xfs_repair<1> will clear some or all of the filesystem quota information. If so, the program issues a warning just before it terminates. If all quota information is lost, quotas are disabled and the program issues a warning to that effect.

Note that <2>xfs_repair<1> does not check the validity of quota limits. It is recommended that you check the quota limit information manually after <2>xfs_repair<1>. Also, space usage information is automatically regenerated the next time the filesystem is mounted with quotas turned on, so the next quota mount of the filesystem may take some time.