[BACK]Return to xfs_repair.html CVS log [TXT][DIR] Up to [Development] / xfs-website.orig / manpages
File: [Development] / xfs-website.orig / manpages / xfs_repair.html (download) (as text)

Revision 1.4, Thu Jan 25 19:55:31 2001 UTC (16 years, 8 months ago) by xfs
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +250 -267 lines 

Man pages update.

<html>
<head>
<meta name="Content-Style" content="text/css">
</head>
<body>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#Checks Performed">Checks Performed</a><br>
<a href="#Disk Errors">Disk Errors</a><br>
<a href="#lost+found">lost+found</a><br>
<a href="#Corrupted Superblocks">Corrupted Superblocks</a><br>
<a href="#Quotas">Quotas</a><br>
<a href="#DIAGNOSTICS">DIAGNOSTICS</a><br>
<a href="#EXIT STATUS">EXIT STATUS</a><br>
<a href="#BUGS">BUGS</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<!-- Creator     : groff version 1.16.1  -->
<!-- CreationDate: Wed Jan 24 01:42:54 2001
 -->
<!-- Total number of pages: 4 -->
<!-- Page: 1 -->
<!-- left  margin: 220 -->
<!-- right margin: 750 -->
<a name="NAME"></a><h2>NAME</h2><p style="margin-left: 18%"><font size=3>xfs_repair - repair an XFS filesystem</font></p>
<a name="SYNOPSIS"></a><h2>SYNOPSIS</h2><p style="margin-left: 18%"><font size=3><B>xfs_repair</B></font> <font size=3>[</font> <font size=3><B>-n</B></font> <font size=3>] [</font> <font size=3><B>-o</B></font> <font size=3>subopt[=value] ] xfs_special</font></p>
<p style="margin-left: 18%"><font size=3><B>xfs_repair -f</B></font> <font size=3>[</font> <font size=3><B>-n</B></font> <font size=3>] [</font> <font size=3><B>-o</B></font> <font size=3>subopt[=value] ] ... file</font></p>
<a name="DESCRIPTION"></a><h2>DESCRIPTION</h2><p style="margin-left: 18%"><font size=3><I>xfs_repair</I></font> <font size=3>repairs corrupt or damaged XFS filesystems (see</font> <font size=3><I>xfs</I></font><font size=3>(5)). The filesystem is specified using the</font> <font size=3><I>xfs_special</I></font> <font size=3>argument which should be the device name of the disk partition or volume containing the filesystem. If given the name of a block device,</font> <font size=3><I>xfs_repair</I></font> <font size=3>will attempt to find the raw device associated with the specified block device and will use the raw device instead.</font></p>
<p style="margin-left: 18%"><font size=3>Regardless, the filesystem to be repaired must be unmounted, otherwise, the resulting filesystem may be inconsistent or corrupt.</font></p>
<p style="margin-left: 18%"><font size=3>The options to</font> <font size=3><I>xfs_repair</I></font> <font size=3>are:</font>
<table width="99%" rules="none" frame="none" cols="3" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="18%">
</p>
</td>
<td valign="top" align="left" width="18%">
<p><font size=3><B>-f</B></font></p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>Specifies that the special device is actually a file (see the</font> <font size=3><I>mkfs.xfs</I></font> <font size=3><B>-d</B></font> <font size=3><I>file</I></font> <font size=3>option). This might happen if an image copy of a filesystem has been copied or written into an ordinary file.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="18%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3><B>-n</B></font></p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>No modify mode. Specifies that</font> <font size=3><I>xfs_repair</I></font> <font size=3>should not modify the filesystem but should only scan the filesystem and indicate what repairs would have been made.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="18%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3><B>-o</B></font></p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>Override what the program might conclude about the filesystem if left to its own devices.</font></p>
<p><font size=3>The</font> <font size=3><B>assume_xfs</B></font> <font size=3>suboption specifies that the filesystem is an XFS filesystem. Normally, if</font> <font size=3><I>xfs_repair</I></font> <font size=3>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</font> <font size=3><B>assume_xfs</B></font> <font size=3>option is in effect,</font> <font size=3><I>xfs_repair</I></font> <font size=3>will assume that the filesystem is an XFS filesystem and will ignore an EFS superblock if one is found.</font></p>
</td>
</tr>
</table>
</p>
<a name="Checks Performed"></a><h2>Checks Performed</h2><p style="margin-left: 16%"><font size=3>Inconsistencies corrected include the following:</font>
<table width="98%" rules="none" frame="none" cols="3" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</p>
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>1.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=3>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.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>2.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=3>Inode allocation map checks: bad magic number in inode map blocks, inode state as indicated by map (free or in&shy;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.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>3.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=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.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>4.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=3>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.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>5.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=3>Pathname checks: files or directories not referenced by a pathname starting from the filesystem root, illegal pathname components.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>6.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=3>Link count checks: link counts that do not agree with the number of directory references to the inode.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>7.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=3>Freemap checks: blocks claimed free by the freemap but also claimed by an inode, blocks unclaimed by any inode but not appearing in the</font></p>
</td>
</tr>
</table>
<br>
</p>

<!-- Page: 2  -->
<!-- left  margin: 220 -->
<!-- right margin: 750 -->

<table width="98%" rules="none" frame="none" cols="3" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="16%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>8.</font></p>
</td>
<td valign="top" align="left" width="64%">
<p><font size=3>freemap.</font></p>
<p><font size=3>Super Block checks: total free block and/or free i&shy;node count incorrect, filesystem geometry inconsistent, secondary and primary superblocks contradictory.</font></p>
</td>
</tr>
</table>
<p style="margin-left: 16%"><font size=3>Orphaned files and directories (allocated, in&shy;use but unreferenced) are reconnected by placing them in the</font> <font size=3><I>lost+found</I></font> <font size=3>directory. The name assigned is the inode number.</font></p>
<a name="Disk Errors"></a><h2>Disk Errors</h2><p style="margin-left: 16%"><font size=3><I>xfs_repair</I></font> <font size=3>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</font> <font size=3><I>xfs_repair</I></font> <font size=3>to repair the filesystem. A possible method is using</font> <font size=3><I>dd</I></font><font size=3>(8) to copy the data onto a good disk.</font></p>
<a name="lost+found"></a><h2>lost+found</h2><p style="margin-left: 16%"><font size=3>The directory</font> <font size=3><I>lost+found</I></font> <font size=3>does not have to already exist in the filesystem being repaired. If the directory does not exist, it is automatically created. If the</font> <font size=3><I>lost+found</I></font> <font size=3>directory already exists, the</font> <font size=3><I>lost+found</I></font> <font size=3>directory is deleted and recreated every time</font> <font size=3><I>xfs_repair</I></font> <font size=3>runs. This ensures that there are no name conflicts in</font> <font size=3><I>lost+found</I></font><font size=3>. However, if you rename a file in</font> <font size=3><I>lost+found</I></font> <font size=3>and leave it there, if</font> <font size=3><I>xfs_repair</I></font> <font size=3>is run again, that file is renamed back to its inode number.</font></p>
<a name="Corrupted Superblocks"></a><h2>Corrupted Superblocks</h2><p style="margin-left: 16%"><font size=3>XFS has both primary and secondary superblocks.</font> <font size=3><I>xfs_repair</I></font> <font size=3>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.</font></p>
<a name="Quotas"></a><h2>Quotas</h2><p style="margin-left: 16%"><font size=3>If quotas are in use, it is possible that</font> <font size=3><I>xfs_repair</I></font> <font size=3>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.</font></p>
<p style="margin-left: 16%"><font size=3>Note that</font> <font size=3><I>xfs_repair</I></font> <font size=3>does not check the validity of quota limits. It is recommended that you check the quota limit information manually after</font> <font size=3><I>xfs_repair</I></font><font size=3>. 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.</font></p>
<a name="DIAGNOSTICS"></a><h2>DIAGNOSTICS</h2><p style="margin-left: 18%"><font size=3><I>xfs_repair</I></font> <font size=3>issues informative messages as it proceeds indicating what it has found that is abnormal or any corrective action that it has taken. Most of the messages are completely understandable only to those who are knowledgeable about the structure of the filesystem. Some of the more common messages are explained here. Note that the language of the messages is slightly different if</font> <font size=3><I>xfs_repair</I></font> <font size=3>is run in no&shy;modify mode because the program is not changing anything on disk. No&shy;modify mode indicates what it would do to repair the filesystem if run without the no&shy;modify flag.</font></p>
<p style="margin-left: 18%"><font size=3>disconnected inode</font> <font size=3><B>xxxx</B></font><font size=3>, moving to</font> <font size=3><I>lost+found</I></font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>An inode numbered</font> <font size=3><B>xxxx</B></font> <font size=3>was not connected to the filesystem directory tree and was reconnected to the</font> <font size=3><I>lost+found</I></font> <font size=3>directory. The inode is assigned the name of its inode number (i&shy;number). If a</font> <font size=3><I>lost+found</I></font> <font size=3>directory does not exist, it is automatically created.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>disconnected dir inode</font> <font size=3><B>xxxx</B></font><font size=3>, moving to</font> <font size=3><I>lost+found</I></font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>As above only the inode is a directory inode. If a directory inode is attached to</font> <font size=3><I>lost+found</I></font><font size=3>, all of its children (if any) stay attached to the directory and therefore get automatically reconnected when the directory is reconnected.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>imap claims in&shy;use inode</font> <font size=3><B>xxxx</B></font> <font size=3>is free, correcting imap</font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>The inode allocation map thinks that inode</font> <font size=3><B>xxxx</B></font> <font size=3>is free whereas examination of the inode indicates that the inode may be in use (although it may be disconnected). The program updates the inode allocation map.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>imap claims free inode</font> <font size=3><B>xxxx</B></font> <font size=3>is in use, correcting imap</font><br>
</p>

<!-- Page: 3  -->
<!-- left  margin: 220 -->
<!-- right margin: 750 -->

<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>The inode allocation map thinks that inode</font> <font size=3><B>xxxx</B></font> <font size=3>is in use whereas examination of the inode indicates that the inode is not in use and therefore is free. The program updates the inode allocation map.</font></p>
</td>
</tr>
</table>
<p style="margin-left: 18%"><font size=3>resetting inode</font> <font size=3><B>xxxx</B></font> <font size=3>nlinks from</font> <font size=3><B>x</B></font> <font size=3>to</font> <font size=3><B>y</B></font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>The program detected a mismatch between the number of valid directory entries referencing inode</font> <font size=3><B>xxxx</B></font> <font size=3>and the number of references recorded in the inode and corrected the the number in the inode.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3><B>fork&shy;type</B></font> <font size=3>fork in ino</font> <font size=3><B>xxxx</B></font> <font size=3>claims used block</font> <font size=3><B>yyyy</B></font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>Inode</font> <font size=3><B>xxxx</B></font> <font size=3>claims a block</font> <font size=3><B>yyyy</B></font> <font size=3>that is used (claimed) by either another inode or the filesystem itself for metadata storage. The</font> <font size=3><B>fork&shy;type</B></font> <font size=3>is either</font> <font size=3><B>data</B></font> <font size=3>or</font> <font size=3><B>attr</B></font> <font size=3>indicating whether the problem lies in the portion of the inode that tracks regular data or the portion of the inode that stores XFS attributes. If the inode is a real&shy;time (rt) inode, the message says so. Any inode that claims blocks used by the filesystem is deleted. If two or more inodes claim the same block, they are both deleted.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3><B>fork&shy;type</B></font> <font size=3>fork in ino</font> <font size=3><B>xxxx</B></font> <font size=3>claims dup extent ...</font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>Inode</font> <font size=3><B>xxxx</B></font> <font size=3>claims a block in an extent known to be claimed more than once. The offset in the inode, start and length of the extent is given. The message is slightly different if the inode is a real&shy;time (rt) inode and the extent is therefore a real&shy;time (rt) extent.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>inode</font> <font size=3><B>xxxx</B></font> <font size=3>&shy; bad extent ...</font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>An extent record in the blockmap of inode</font> <font size=3><B>xxxx</B></font> <font size=3>claims blocks that are out of the legal range of the filesystem. The message supplies the start, end, and file offset of the extent. The message is slightly different if the extent is a real&shy;time (rt) exent.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>bad</font> <font size=3><B>fork&shy;type</B></font> <font size=3>fork in inode</font> <font size=3><B>xxxx</B></font>
<table width="99%" rules="none" frame="none" cols="3" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="18%">
</p>
</td>
<td valign="top" align="left" width="18%">
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>There was something structurally wrong or inconsistent with the data structures that map offsets to filesystem blocks.</font></p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="18%">
</td>
<td valign="top" align="left" width="18%">
<p><font size=3>cleared inode</font> <font size=3><B>xxxx</B></font></p>
</td>
<td valign="top" align="left" width="63%">
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="18%">
</td>
<td valign="top" align="left" width="18%">
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>There was something wrong with the inode that was uncorrectable so the program freed the inode. This usually happens because the inode claims blocks that are used by something else or the inode itself is badly corrupted. Typically, this message is preceded by one or more messages indicating why the inode needed to be cleared.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>bad attribute fork in inode</font> <font size=3><B>xxxx</B></font><font size=3>, clearing attr fork</font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>There was something wrong with the portion of the inode that stores XFS attributes (the attribute fork) so the program reset the attribute fork. As a result of this, all attributes on that inode are lost.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>correcting nextents for inode</font> <font size=3><B>xxxx</B></font><font size=3>, was</font> <font size=3><B>x</B></font> <font size=3>&shy; counted</font> <font size=3><B>y</B></font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>The program found that the number of extents used to store the data in the inode is wrong and corrected the number. The message refers to nextents if the count is wrong on the number of extents used to store attribute information.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>entry</font> <font size=3><B>&quot;name&quot;</B></font> <font size=3>in dir</font> <font size=3><B>xxxx</B></font> <font size=3>not consistent with .. value (</font><font size=3><B>yyyy</B></font><font size=3>) in dir ino</font> <font size=3><B>xxxx</B></font><font size=3>, junking entry</font> <font size=3><B>&quot;name&quot;</B></font> <font size=3>in directory inode</font> <font size=3><B>xxxx</B></font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>The entry</font> <font size=3><B>&quot;name&quot;</B></font> <font size=3>in directory inode</font> <font size=3><B>xxxx</B></font> <font size=3>references a directory inode</font> <font size=3><B>yyyy</B></font><font size=3>. However, the .. entry in directory</font> <font size=3><B>yyyy</B></font> <font size=3>does not point back to directory</font> <font size=3><B>xxxx</B></font><font size=3>, so the program deletes the entry</font> <font size=3><B>&quot;name&quot;</B></font> <font size=3>in directory inode</font> <font size=3><B>xxxx</B></font><font size=3>. If the directory inode</font> <font size=3><B>yyyy</B></font> <font size=3>winds up becoming a disconnected inode as a result of this, it is moved to</font> <font size=3><I>lost+found</I></font> <font size=3>later.</font></p>
</td>
</tr>
</table>
</p>
<p style="margin-left: 18%"><font size=3>entry</font> <font size=3><B>&quot;name&quot;</B></font> <font size=3>in dir</font> <font size=3><B>xxxx</B></font> <font size=3>references already connected dir ino</font> <font size=3><B>yyyy</B></font><font size=3>, junking entry</font> <font size=3><B>&quot;name&quot;</B></font> <font size=3>in directory inode</font> <font size=3><B>xxxx</B></font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>The entry</font> <font size=3><B>&quot;name&quot;</B></font> <font size=3>in directory inode</font> <font size=3><B>xxxx</B></font> <font size=3>points to a directory inode</font> <font size=3><B>yyyy</B></font> <font size=3>that is known to be a child of another directory. Therefore, the</font></p>
</td>
</tr>
</table>
<br>
</p>

<!-- Page: 4  -->
<!-- left  margin: 220 -->
<!-- right margin: 750 -->

<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>entry is invalid and is deleted. This message refers to an entry in a small directory. If this were a large directory, the last phrase would read &quot;will clear entry&quot;.</font></p>
</td>
</tr>
</table>
<p style="margin-left: 18%"><font size=3>entry references free inode</font> <font size=3><B>xxxx</B></font> <font size=3>in directory</font> <font size=3><B>yyyy</B></font><font size=3>, will clear entry</font>
<table width="99%" rules="none" frame="none" cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td valign="top" align="left" width="36%">
</p>
</td>
<td valign="top" align="left" width="63%">
<p><font size=3>An entry in directory inode</font> <font size=3><B>yyyy</B></font> <font size=3>references an inode</font> <font size=3><B>xxxx</B></font> <font size=3>that is known to be free. The entry is therefore invalid and is deleted. This message refers to a large directory. If the directory were small, the message would read &quot;junking entry ...&quot;.</font></p>
</td>
</tr>
</table>
</p>
<a name="EXIT STATUS"></a><h2>EXIT STATUS</h2><p style="margin-left: 18%"><font size=3><I>xfs_repair &shy;n</I></font> <font size=3>(no modify node) will return a status of 1 if filesystem corruption was detected and 0 if no filesystem corruption was detected.</font> <font size=3><I>xfs_repair</I></font> <font size=3>run without the &shy;n option will always return a status code of 0.</font></p>
<a name="BUGS"></a><h2>BUGS</h2><p style="margin-left: 18%"><font size=3><I>xfs_repair</I></font> <font size=3>does not do a thorough job on XFS extended attributes. The structure of the attribute fork will be consistent, but only the contents of attribute forks that will fit into an inode are checked. This limitation will be fixed in the future.</font></p>
<p style="margin-left: 18%"><font size=3>The no&shy;modify mode (</font><font size=3><B>-n</B></font> <font size=3>option) is not completely accurate. It does not catch inconsistencies in the freespace and inode maps, particularly lost blocks or subtly corrupted maps (trees).</font></p>
<p style="margin-left: 18%"><font size=3>The no&shy;modify mode can generate repeated warnings about the same problems because it cannot fix the problems as they are encountered.</font></p>
<a name="SEE ALSO"></a><h2>SEE ALSO</h2><p style="margin-left: 18%"><font size=3>dd(1), mkfs.xfs(8), xfs_check(8), xfs(5).</font><br>
</p>
</body>
</html>