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

Revision 1.2, Tue Apr 25 00:26:32 2000 UTC (17 years, 6 months ago) by cattelan
Branch: MAIN
Changes since 1.1: +1 -1 lines 

Make the body white

<html>
<head>
<meta name="Content-Style" content="text/css">
</head>
<body bgcolor="white">
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#CONCEPTS">CONCEPTS</a><br>
<a href="#COMMANDS">COMMANDS</a><br>
<a href="#blockfree">blockfree</a><br>
<a href="#TYPES">TYPES</a><br>
<a href="#rtbitmap">rtbitmap</a><br>
<a href="#DIAGNOSTICS">DIAGNOSTICS</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<!-- Creator     : groff version 1.15  -->
<!-- CreationDate: Mon Apr 24 10:40:31 2000
 -->
<!-- Total number of pages: 10 -->
<!-- Page: 1 -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<a name="NAME"></a><h2>NAME</h2><p><font size=3>xfs_db, xfs_db64 - debug an XFS filesystem</p>
<a name="SYNOPSIS"></a><h2>SYNOPSIS</h2>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="56.1538%">
<p><font size=3><B>xfs_db</B> <font size=3>[ <font size=3><B>-c</B> <font size=3>cmd ] ... [ <font size=3><B>-p</B> <font size=3>prog ] [ <font size=3><B>-r</B> <font size=3>] [ <font size=3><B>-x</B> <font size=3>] xfs_special</p>
<p><font size=3><B>xfs_db -f</B> <font size=3>[ <font size=3><B>-c</B> <font size=3>cmd ] ... [ <font size=3><B>-p</B> <font size=3>prog ] [ <font size=3><B>-f</B> <font size=3>] [ <font size=3><B>-r</B> <font size=3>] [ <font size=3><B>-x</B> <font size=3>] file</p>
<p><font size=3><B>xfs_db64</B> <font size=3>[ <font size=3><B>-c</B> <font size=3>cmd ] ... [ <font size=3><B>-p</B> <font size=3>prog ] [ <font size=3><B>-f</B> <font size=3>] [ <font size=3><B>-r</B> <font size=3>] [ <font size=3><B>-x</B> <font size=3>] xfs_special</p>
<p><font size=3><B>xfs_db64 -f</B> <font size=3>[ <font size=3><B>-c</B> <font size=3>cmd ] ... [ <font size=3><B>-p</B> <font size=3>prog ] [ <font size=3><B>-r</B> <font size=3>] [ <font size=3><B>-x</B> <font size=3>] file</p>
</td>
<td valign="top" align="left"  width="43.8462%">
</td>
</tr>
</table>
<br>
<a name="DESCRIPTION"></a><h2>DESCRIPTION</h2><p><font size=3><I>xfs_db</I> <font size=3>is used to examine an XFS filesystem. Under rare circumstances it can also be used to modify an XFS filesystem, but that task is normally left to <font size=3><I>xfs_repair</I><font size=3>(1M) or to scripts such as <font size=3><I>xfs_chver</I> <font size=3>that run <font size=3><I>xfs_db</I><font size=3>.</p>
<p><font size=3><I>xfs_db64</I> <font size=3>is a 64-bit version of <font size=3><I>xfs_db</I> <font size=3>which is not as susceptible to running out of memory. It is available only on 64-bit capable systems.</p>
<p><font size=3>The options to <font size=3><I>xfs_db</I> <font size=3>are:</p>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="6.9231%">
<p><font size=3><B>-c</B> <font size=3><I>cmd</p>
</I></td>
<td valign="top" align="left"  width="2.3077%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3><I>xfs_db</I> <font size=3>commands may be run interactively (the default) or as arguments on the command line. Multi- ple <font size=3><B>-c</B> <font size=3>arguments may be given. The commands are run in the sequence given, then the program exits. This is the mechanism used to implement <font size=3><I>xfs_check</I><font size=3>(1M).</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="6.9231%">
<p><font size=3><B>-f</p>
</B></td>
<td valign="top" align="left"  width="2.3077%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Specifies that the filesystem image to be processed is stored in a regular file (see the <font size=3><I>mkfs_xfs</I> <font size=3><B>-d</B> <font size=3><I>file</I> <font size=3>option). This might happen if an image copy of a filesystem has been made into an ordinary file with <font size=3><I>xfs_copy</I><font size=3>(1M).</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="6.9231%">
<p><font size=3><B>-p</B> <font size=3><I>prog</p>
</I><p><font size=3><B>-r</p>
</B></td>
<td valign="top" align="left"  width="2.3077%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set the program name for prompts and some error messages, the default value is <font size=3><I>xfs_db</I> <font size=3>or <font size=3><I>xfs_db64</I><font size=3>.</p>
<p><font size=3>Open <font size=3><I>file</I> <font size=3>or <font size=3><I>xfs_special</I> <font size=3>read-only. This option is required if <font size=3><I>xfs_special</I> <font size=3>is a mounted filesystem. It is<br>
only necessary to omit this flag if a command that changes data (<font size=3><B>write</B><font size=3>, <font size=3><B>blocktrash</B><font size=3>) is to be used.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="6.9231%">
<p><font size=3><B>-x</p>
</B></td>
<td valign="top" align="left"  width="2.3077%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Specifies expert mode. This enables the <font size=3><B>write</B> <font size=3>command.</p>
</td>
</tr>
</table>
<br>
<a name="CONCEPTS"></a><h2>CONCEPTS</h2><p><font size=3><I>xfs_db</I> <font size=3>commands can be broken up into two classes. Most commands are for the navigation and display of data structures in the filesystem. Other commands are for scanning the filesystem in some way.</p>
<p><font size=3>Commands which are used to navigate the filesystem structure take arguments which reflect the names of filesys- tem structure fields. There can be multiple field names separated by dots when the underlying structures are nested, as in C. The field names can be indexed (as an array index) if the underlying field is an array. The array indices can be specified as a range, two numbers separated by a dash.</p>
<p><font size=3><I>xfs_db</I> <font size=3>maintains a current address in the filesystem. The granularity of the address is a filesystem structure. This can be a filesystem block, an inode or quota (smaller than a filesystem block), or a directory block (could be larger than a filesystem block). There are a variety of commands to set the current address. Associated with the cur- rent address is the current data type, which is the structural type of this data. Commands which follow the struc- ture of the filesystem always set the type as well as the address. Commands which examine pieces of an individ- ual file (inode) need the current inode to be set, this is done with the <font size=3><B>inode</B> <font size=3>command.</p>
<p><font size=3>The current address/type information is actually maintained in a stack that can be explicitly manipulated with the <font size=3><B>push</B><font size=3>, <font size=3><B>pop</B><font size=3>, and <font size=3><B>stack</B> <font size=3>commands. This allows for easy examination of a nested filesystem structure. Also, the last several locations visited are stored in a ring buffer which can be manipulated with the <font size=3><B>forward</B><font size=3>, <font size=3><B>back, and ring</B> <font size=3>commands.</p>
<p><font size=3>XFS filesystems are divided into a small number of allocation groups. <font size=3><I>xfs_db</I> <font size=3>maintains a notion of the current allo- cation group which is manipulated by some commands. The initial allocation group is 0.</p>
<a name="COMMANDS"></a><h2>COMMANDS</h2><p><font size=3>Many commands have extensive online help. Use the <font size=3><B>help</B> <font size=3>command for more details on any command.</p>
<p><font size=3><B>a</B> <font size=3>See the <font size=3><B>addr</B> <font size=3>command.</p>
<p><font size=3><B>ablock</B> <font size=3><I>filoff</p>
</I>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set current address to the offset <font size=3><I>filoff</I> <font size=3>(a filesystem block number) in the attribute area of the current<br>
inode.</p>
</td>
</tr>
</table>
<p><font size=3><B>addr</B> <font size=3>[ <font size=3><I>field-expression</I> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Set current address to the value of the <font size=3><I>field-expression</I><font size=3>. This is used to ``follow'' a reference in one<br>
<span style=" text-indent: 0.6000in;"></span>structure to the object being referred to. If no argument is given the current address is printed.<br>
</p>

<!-- Page: 2  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<p><font size=3><B>agf</B> <font size=3>[ <font size=3><I>agno</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set current address to the AGF block for allocation group <font size=3><I>agno</I><font size=3>. If no argument is given use the current<br>
allocation group.</p>
</td>
</tr>
</table>
<p><font size=3><B>agfl</B> <font size=3>[ <font size=3><I>agno</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set current address to the AGFL block for allocation group <font size=3><I>agno</I><font size=3>. If no argument is given use the cur-<br>
rent allocation group.</p>
</td>
</tr>
</table>
<p><font size=3><B>agi</B> <font size=3>[ <font size=3><I>agno</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set current address to the AGI block for allocation group <font size=3><I>agno</I><font size=3>. If no argument is given use the current<br>
allocation group.</p>
</td>
</tr>
</table>
<p><font size=3><B>b</B> <font size=3>See the <font size=3><B>back</B> <font size=3>command.</p>
<p><font size=3><B>back</B> <font size=3>Move to the previous location in the position ring.</p>
<a name="blockfree"></a><h2>blockfree</h2><p><span style=" text-indent: 0.6000in;"></span><font size=3>Free block usage information collected by the last execution of the <font size=3><B>blockget</B> <font size=3>command. This must be<br>
<span style=" text-indent: 0.6000in;"></span>done before another <font size=3><B>blockget</B> <font size=3>command can be given, presumably with different arguments than the<br>
<span style=" text-indent: 0.6000in;"></span>previous one.</p>
<p><font size=3><B>blockget</B> <font size=3>[ <font size=3><B>-npsv</B> <font size=3>] [ <font size=3><B>-b</B> <font size=3><I>bno</I> <font size=3>] ... [ <font size=3><B>-i</B> <font size=3><I>ino</I> <font size=3>] ...<br>
<span style=" text-indent: 0.6000in;"></span>Get block usage and check filesystem consistency. The information is saved for use by a subsequent<br>
<span style=" text-indent: 0.6000in;"></span><B>blockuse</B><font size=3>, <font size=3><B>ncheck</B><font size=3>, or <font size=3><B>blocktrash</B> <font size=3>command. See <font size=3><I>xfs_check</I><font size=3>(1M) for more information.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-b</B> <font size=3>option is used to specify filesystem block numbers about which verbose information should be<br>
<span style=" text-indent: 0.6000in;"></span>printed.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-i</B> <font size=3>option is used to specify inode numbers about which verbose information should be printed.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-n</B> <font size=3>option is used to save pathnames for inodes visited, this is used to support the <font size=3><I>xfs_ncheck</I><font size=3>(1M)<br>
<span style=" text-indent: 0.6000in;"></span>command. It also means that pathnames will be printed for inodes that have problems. This option uses<br>
<span style=" text-indent: 0.6000in;"></span>a lot of memory so is not enabled by default.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-p</B> <font size=3>option causes error messages to be prefixed with the filesystem name being processed. This is<br>
<span style=" text-indent: 0.6000in;"></span>useful if several copies of <font size=3><I>xfs_db</I> <font size=3>are run in parallel.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-s</B> <font size=3>option restricts output to severe errors only. This is useful if the output is too long otherwise.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-v</B> <font size=3>option enables verbose output. Messages will be printed for every block and inode processed.</p>
<p><font size=3><B>blocktrash</B> <font size=3>[ <font size=3><B>-n</B> <font size=3><I>c</I> <font size=3>] [ <font size=3><B>-x</B> <font size=3><I>a</I> <font size=3>] [ <font size=3><B>-y</B> <font size=3><I>b</I> <font size=3>] [ <font size=3><B>-s</B> <font size=3><I>s</I> <font size=3>] [ <font size=3><B>-0123</B> <font size=3>] [ <font size=3><B>-t</B> <font size=3><I>t</I> <font size=3>] ...<br>
<span style=" text-indent: 0.6000in;"></span>Trash randomly selected filesystem metadata blocks. Trashing occurs to randomly selected bits in the<br>
<span style=" text-indent: 0.6000in;"></span>chosen blocks. This command is available only in debugging versions of <font size=3><I>xfs_db</I><font size=3>. It is useful for testing<br>
<span style=" text-indent: 0.6000in;"></span><I>xfs_repair</I><font size=3>(1M) and <font size=3><I>xfs_check</I><font size=3>(1M).<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-0</B><font size=3>, <font size=3><B>-1</B><font size=3>, <font size=3><B>-2</B><font size=3>, and <font size=3><B>-3</B> <font size=3>options (mutually exclusive) set the operating mode for <font size=3><B>blocktrash</B><font size=3>. In <font size=3><B>-0<br>
<span style=" text-indent: 0.6000in;"></span></B>mode, changed bits are cleared. In <font size=3><B>-1</B> <font size=3>mode, changed bits are set. In <font size=3><B>-2</B> <font size=3>mode, changed bits are<br>
<span style=" text-indent: 0.6000in;"></span>inverted. In <font size=3><B>-3</B> <font size=3>mode, changed bits are randomized.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-n</B> <font size=3>option supplies the count of block-trashings to perform (default 1).<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-s</B> <font size=3>option supplies a seed to the random processing.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-t</B> <font size=3>option gives a type of blocks to be selected for trashing. Multiple <font size=3><B>-t</B> <font size=3>options may be given. If no<br>
<span style=" text-indent: 0.6000in;"></span><B>-t</B> <font size=3>options are given then all metadata types can be trashed.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-x</B> <font size=3>option sets the minimum size of bit range to be trashed. The default value is 1.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-y</B> <font size=3>option sets the maximum size of bit range to be trashed. The default value is 1024.</p>
<p><font size=3><B>blockuse</B> <font size=3>[ <font size=3><B>-n</B> <font size=3>] [ <font size=3><B>-c</B> <font size=3><I>blockcount</I> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Print usage for current filesystem block(s). For each block, the type and (if any) inode are printed.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-c</B> <font size=3>option specifies a count of blocks to process. The default value is 1 (the current block only).</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>The <font size=3><B>-n</B> <font size=3>option specifies that file names should be printed. The prior <font size=3><B>blockget</B> <font size=3>command must have also<br>
specified the <font size=3><B>-n</B> <font size=3>option.</p>
</td>
</tr>
</table>
<p><font size=3><B>bmap</B> <font size=3>[ <font size=3><B>-a</B> <font size=3>] [ <font size=3><B>-d</B> <font size=3>] [ <font size=3><I>block</I> <font size=3>[ <font size=3><I>len</I> <font size=3>] ]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Show the block map for the current inode. The map display can be restricted to an area of the file with the <font size=3><I>block</I> <font size=3>and <font size=3><I>len</I> <font size=3>arguments. If <font size=3><I>block</I> <font size=3>is given and <font size=3><I>len</I> <font size=3>is omitted then 1 is assumed for len.<br>
The <font size=3><B>-a</B> <font size=3>and <font size=3><B>-d</B> <font size=3>options are used to select the attribute or data area of the inode, if neither option is given then both areas are shown.</p>
</td>
</tr>
</table>
<p><font size=3><B>check</B> <font size=3>See the <font size=3><B>blockget</B> <font size=3>command.</p>
<p><font size=3><B>convert</B> <font size=3><I>type number</I> <font size=3>[ <font size=3><I>type number</I> <font size=3>] ... <font size=3><I>type</p>
</I>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Convert from one address form to another. The known <font size=3><I>type</I><font size=3>s, with alternate names, are: <font size=3><B>agblock</B> <font size=3>or <font size=3><B>agbno</B> <font size=3>(filesystem block within an allocation group), <font size=3><B>agino</B> <font size=3>or <font size=3><B>aginode</B> <font size=3>(inode number within an alloca- tion group), <font size=3><B>agnumber</B> <font size=3>or <font size=3><B>agno</B> <font size=3>(allocation group number), <font size=3><B>bboff</B> <font size=3>or <font size=3><B>daddroff</B> <font size=3>(byte offset in a <font size=3><B>daddr</B><font size=3>), <font size=3><B>blkoff</B> <font size=3>or <font size=3><B>fsboff</B> <font size=3>or <font size=3><B>agboff</B> <font size=3>(byte offset in a <font size=3><B>agblock</B> <font size=3>or <font size=3><B>fsblock</B><font size=3>), <font size=3><B>byte</B> <font size=3>or <font size=3><B>fsbyte</B> <font size=3>(byte address in filesys- tem), <font size=3><B>daddr</B> <font size=3>or <font size=3><B>bb</B> <font size=3>(disk address, 512-byte blocks), <font size=3><B>fsblock</B> <font size=3>or <font size=3><B>fsb</B> <font size=3>or <font size=3><B>fsbno</B> <font size=3>(filesystem block, see the</p>
</td>
</tr>
</table>
<br>
<!-- Page: 3  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<p><span style=" text-indent: 0.6000in;"></span><font size=3><B>fsblock</B> <font size=3>command), <font size=3><B>ino</B> <font size=3>or <font size=3><B>inode</B> <font size=3>(inode number), <font size=3><B>inoidx</B> <font size=3>or <font size=3><B>offset</B> <font size=3>(index of inode in filesystem block),<br>
<span style=" text-indent: 0.6000in;"></span>and <font size=3><B>inooff</B> <font size=3>or <font size=3><B>inodeoff</B> <font size=3>(byte offset in inode). Only conversions that ``make sense'' are allowed. The<br>
<span style=" text-indent: 0.6000in;"></span>compound form (with more than three arguments) is useful for conversions such as <font size=3><B>convert agno</B> <font size=3><I>ag<br>
<span style=" text-indent: 0.6000in;"></span></I><B>agbno</B> <font size=3><I>agb</I> <font size=3><B>fsblock</B><font size=3>.</p>
<p><font size=3><B>daddr</B> <font size=3>[ <font size=3><I>d</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set current address to the daddr (512 byte block) given by <font size=3><I>d</I><font size=3>. If no value for <font size=3><I>d</I> <font size=3>is given the current<br>
address is printed, expressed as a daddr. The type is set to <font size=3><B>data</B> <font size=3>(uninterpreted).</p>
</td>
</tr>
</table>
<p><font size=3><B>dblock</B> <font size=3><I>filoff<br>
<span style=" text-indent: 0.6000in;"></span></I>Set current address to the offset <font size=3><I>filoff</I> <font size=3>(a filesystem block number) in the data area of the current inode. <font size=3><B>debug</B> <font size=3>[ <font size=3><I>flagbits</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set debug option bits. These are used for debugging <font size=3><I>xfs_db</I><font size=3>. If no value is given for <font size=3><I>flagbits</I><font size=3>, print the<br>
current debug option bits. These are for the use of the implementor.</p>
</td>
</tr>
</table>
<p><font size=3><B>dquot</B> <font size=3>[ <font size=3><I>projectid_or_userid</I> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Set current address to a project or user quota block.</p>
<p><font size=3><B>echo</B> <font size=3>[ <font size=3><I>arg</I> <font size=3>] ...<br>
<span style=" text-indent: 0.6000in;"></span>Echo the arguments to the output.</p>
<p><font size=3><B>f</B> <font size=3>See the <font size=3><B>forward</B> <font size=3>command.</p>
<p><font size=3><B>forward</B> <font size=3>Move forward to the next entry in the position ring.</p>
<p><font size=3><B>frag</B> <font size=3>[ <font size=3><B>-adflqRrv</B> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Get file fragmentation data. This prints information about fragmentation of file data in the filesystem (as<br>
<span style=" text-indent: 0.6000in;"></span>opposed to fragmentation of freespace, for which see the <font size=3><B>freesp</B> <font size=3>command). Every file in the filesystem<br>
<span style=" text-indent: 0.6000in;"></span>is examined to see how far from ideal its extent mappings are. A summary is printed giving the totals.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-v</B> <font size=3>option sets verbosity, every inode has information printed for it. The remaining options select<br>
<span style=" text-indent: 0.6000in;"></span>which inodes and extents are examined. If no options are given then all are assumed set, otherwise just<br>
<span style=" text-indent: 0.6000in;"></span>those given are enabled.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-a</B> <font size=3>option enables processing of attribute data.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-d</B> <font size=3>option enables processing of directory data.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-f</B> <font size=3>option enables processing of regular file data.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-l</B> <font size=3>option enables processing of symbolic link data.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-q</B> <font size=3>option enables processing of quota file data.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-R</B> <font size=3>option enables processing of realtime control file data.<br>
<span style=" text-indent: 0.6000in;"></span>The <font size=3><B>-r</B> <font size=3>option enables processing of realtime file data.</p>
<p><font size=3><B>freesp</B> <font size=3>[ <font size=3><B>-bcds</B> <font size=3>] [ <font size=3><B>-a</B> <font size=3><I>a</I> <font size=3>] ... [ <font size=3><B>-e</B> <font size=3><I>i</I> <font size=3>] [ <font size=3><B>-h</B> <font size=3><I>h1</I> <font size=3>] ... [ <font size=3><B>-m</B> <font size=3><I>m</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Summarize free space for the filesystem. The free blocks are examined and totalled, and displayed in the form of a histogram, with a count of extents in each range of free extent sizes.<br>
The <font size=3><B>-a</B> <font size=3><I>a</I> <font size=3>option adds <font size=3><I>a</I> <font size=3>to the list of allocation groups to be processed. If no <font size=3><B>-a</B> <font size=3>options are given then all allocation groups are processed.<br>
The <font size=3><B>-b</B> <font size=3>option specifies that the histogram buckets are binary-sized, with the starting sizes being the powers of 2.<br>
The <font size=3><B>-c</B> <font size=3>option specifies that <font size=3><B>freesp</B> <font size=3>will search the by-size (cnt) space Btree instead of the default by- block (bno) space Btree.<br>
The <font size=3><B>-d</B> <font size=3>option specifies that every free extent will be displayed.<br>
The <font size=3><B>-e</B> <font size=3><I>i</I> <font size=3>option specifies that the histogram buckets are equal-sized, with the size specified as <font size=3><I>i</I><font size=3>.<br>
The <font size=3><B>-h</B> <font size=3><I>h1</I> <font size=3>option specifies a starting block number for a histogram bucket as <font size=3><I>h1</I><font size=3>. Multiple <font size=3><B>-h</B> <font size=3>options are given to specify the complete set of buckets.<br>
The <font size=3><B>-m</B> <font size=3><I>m</I> <font size=3>option specifies that the histogram starting block numbers are powers of <font size=3><I>m</I><font size=3>. This is the gen- eral case of <font size=3><B>-b</B><font size=3>.<br>
The <font size=3><B>-s</B> <font size=3>option specifies that a final summary of total free extents, free blocks, and the average free extent size is printed.</p>
</td>
</tr>
</table>
<p><font size=3><B>fsb</B> <font size=3>See the <font size=3><B>fsblock</B> <font size=3>command.</p>
<p><font size=3><B>fsblock</B> <font size=3>[ <font size=3><I>fsb</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set current address to the fsblock value given by <font size=3><I>fsb</I><font size=3>. If no value for <font size=3><I>fsb</I> <font size=3>is given the current address is printed, expressed as an fsb. The type is set to <font size=3><B>data</B> <font size=3>(uninterpreted). XFS filesystem block numbers are computed ((<font size=3><I>agno</I> <font size=3>&lt;&lt; <font size=3><I>agshift</I><font size=3>) | <font size=3><I>agblock</I><font size=3>) where <font size=3><I>agshift</I> <font size=3>depends on the size of an allocation group. Use the <font size=3><B>convert</B> <font size=3>command to convert to and from this form. Block numbers given for file blocks (for instance from the <font size=3><B>bmap</B> <font size=3>command) are in this form.</p>
</td>
</tr>
</table>
<br>
<!-- Page: 4  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<p><font size=3><B>hash</B> <font size=3><I>string<br>
<span style=" text-indent: 0.6000in;"></span></I>Prints the hash value of <font size=3><I>string</I> <font size=3>using the hash function of the XFS directory and attribute implementation. <font size=3><B>help</B> <font size=3>[ <font size=3><I>command</I> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Print help for one or all commands.</p>
<p><font size=3><B>inode</B> <font size=3>[ <font size=3><I>inode#</I> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Set the current inode number. If no <font size=3><I>inode#</I> <font size=3>is given, print the current inode number.</p>
<p><font size=3><B>log</B> <font size=3>[ <font size=3><B>stop</B> <font size=3>| <font size=3><B>start</B> <font size=3><I>filename</I> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Start logging output to <font size=3><I>filename</I><font size=3>, stop logging, or print the current logging status.</p>
<p><font size=3><B>ncheck</B> <font size=3>[ <font size=3><B>-s</B> <font size=3>] [ <font size=3><B>-i</B> <font size=3><I>ino</I> <font size=3>] ...</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Print name-inode pairs. A <font size=3><B>blockget -n</B> <font size=3>command must be run first to gather the information.<br>
The <font size=3><B>-i</B> <font size=3>option specifies an inode number to be printed. If no <font size=3><B>-i</B> <font size=3>options are given then all inodes are<br>
printed.<br>
The <font size=3><B>-s</B> <font size=3>option specifies that only setuid and setgid files are printed.</p>
</td>
</tr>
</table>
<p><font size=3><B>p</B> <font size=3>See the <font size=3><B>print</B> <font size=3>command.</p>
<p><font size=3><B>pop</B> <font size=3>Pop location from the stack.</p>
<p><font size=3><B>print</B> <font size=3>[ <font size=3><I>field-expression</I> <font size=3>] ...<br>
<span style=" text-indent: 0.6000in;"></span>Print field values. If no argument is given, print all fields in the current structure.</p>
<p><font size=3><B>push</B> <font size=3>[ <font size=3><I>command</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Push location to the stack. If <font size=3><I>command</I> <font size=3>is supplied, set the current location to the results of <font size=3><I>command<br>
</I>after pushing the old location.</p>
</td>
</tr>
</table>
<p><font size=3><B>q</B> <font size=3>See the <font size=3><B>quit</B> <font size=3>command.</p>
<p><font size=3><B>quit</B> <font size=3>Exit <font size=3><I>xfs_db</I><font size=3>.</p>
<p><font size=3><B>ring</B> <font size=3>[ <font size=3><I>index</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Show position ring (if no <font size=3><I>index</I> <font size=3>argument is given), or move to a specific entry in the position ring given<br>
by <font size=3><I>index</I><font size=3>.</p>
</td>
</tr>
</table>
<p><font size=3><B>sb</B> <font size=3>[ <font size=3><I>agno</I> <font size=3>]</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Set current address to SB header in allocation group <font size=3><I>agno</I><font size=3>. If no <font size=3><I>agno</I> <font size=3>is given use the current allocation<br>
group number.</p>
</td>
</tr>
</table>
<p><font size=3><B>source</B> <font size=3><I>source-file<br>
<span style=" text-indent: 0.6000in;"></span></I>Process commands from <font size=3><I>source-file</I><font size=3>. <font size=3><B>source</B> <font size=3>commands can be nested.</p>
<p><font size=3><B>stack</B> <font size=3>View the location stack.</p>
<p><font size=3><B>type</B> <font size=3>[ <font size=3><I>type</I> <font size=3>]<br>
<span style=" text-indent: 0.6000in;"></span>Set the current data type to <font size=3><I>type</I><font size=3>. If no argument is given, show the current data type. The possible<br>
<span style=" text-indent: 0.6000in;"></span>data types are: <font size=3><B>agf</B><font size=3>, <font size=3><B>agfl</B><font size=3>, <font size=3><B>agi</B><font size=3>, <font size=3><B>attr</B><font size=3>, <font size=3><B>bmapbta</B><font size=3>, <font size=3><B>bmapbtd</B><font size=3>, <font size=3><B>bnobt</B><font size=3>, <font size=3><B>cntbt</B><font size=3>, <font size=3><B>data</B><font size=3>, <font size=3><B>dir</B><font size=3>, <font size=3><B>dir2</B><font size=3>, <font size=3><B>dqblk</B><font size=3>, <font size=3><B>inobt</B><font size=3>,<br>
<span style=" text-indent: 0.6000in;"></span><B>inode</B><font size=3>, <font size=3><B>log</B><font size=3>, <font size=3><B>rtbitmap</B><font size=3>, <font size=3><B>rtsummary</B><font size=3>, <font size=3><B>sb</B><font size=3>, and <font size=3><B>symlink</B><font size=3>. See the TYPES section below for more informa-<br>
<span style=" text-indent: 0.6000in;"></span>tion on these data types.</p>
<p><font size=3><B>write</B> <font size=3>[ <font size=3><I>field or value</I> <font size=3>] ...</p>

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Write a value to disk. Specific fields can be set in structures (struct mode), or a block can be set to data values (data mode), or a block can be set to string values (string mode, for symlink blocks). The opera- tion happens immediately: there is no buffering.<br>
Struct mode is in effect when the current type is structural, i.e. not data. For struct mode, the syntax is ``<font size=3><B>write</B> <font size=3><I>field value</I><font size=3>''.<br>
Data mode is in effect when the current type is data. In this case the contents of the block can be shifted or rotated left or right, or filled with a sequence, a constant value, or a random value. In this mode <font size=3><B>write</B> <font size=3>with no arguments gives more information on the allowed commands.</p>
</td>
</tr>
</table>
<br>
<a name="TYPES"></a><h2>TYPES</h2><p><font size=3>This section gives the fields in each structure type and their meanings. Note that some types of block cover multi- ple actual structures, for instance directory blocks.</p>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.9231%">
<p><font size=3><B>agf</p>
</B></td>
<td valign="top" align="left"  width="6.3077%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>The AGF block is the header for block allocation information; it is in the second 512-byte block of each allocation group. The following fields are defined:<br>
<B>magicnum</B><font size=3>: AGF block magic number, 0x58414746 ('XAGF')<br>
<B>versionnum</B><font size=3>: version number, currently 1<br>
<B>seqno</B><font size=3>: sequence number starting from 0<br>
<B>length</B><font size=3>: size in filesystem blocks of the allocation group. All allocation groups except the last one of the filesystem have the superblock's <font size=3><B>agblocks</B> <font size=3>value here</p>
</td>
</tr>
</table>
<br>
<!-- Page: 5  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.3846%">
</td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3><B>bnoroot</B><font size=3>: block number of the root of the Btree holding free space information sorted by block number<br>
<B>cntroot</B><font size=3>: block number of the root of the Btree holding free space information sorted by block count<br>
<B>bnolevel</B><font size=3>: number of levels in the by-block-number Btree<br>
<B>cntlevel</B><font size=3>: number of levels in the by-block-count Btree<br>
<B>flfirst</B><font size=3>: index into the AGFL block of the first active entry<br>
<B>fllast</B><font size=3>: index into the AGFL block of the last active entry<br>
<B>flcount</B><font size=3>: count of active entries in the AGFL block<br>
<B>freeblks</B><font size=3>: count of blocks represented in the freespace Btrees<br>
<B>longest</B><font size=3>: longest free space represented in the freespace Btrees</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.3846%">
<p><font size=3><B>agfl</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>The AGFL block contains block numbers for use of the block allocator; it is in the fourth 512-byte block of each allocation group. Each entry in the active list is a block number within the allocation group that can be used for any purpose if space runs low. The AGF block fields <font size=3><B>flfirst</B><font size=3>, <font size=3><B>fllast</B><font size=3>, and <font size=3><B>flcount</B> <font size=3>desig- nate which entries are currently active. Entry space is allocated in a circular manner within the AGFL block. Fields defined:<br>
<B>bno</B><font size=3>: array of all block numbers. Even those which are not active are printed</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.3846%">
<p><font size=3><B>agi</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>The AGI block is the header for inode allocation information; it is in the third 512-byte block of each allo- cation group. Fields defined:<br>
<B>magicnum</B><font size=3>: AGI block magic number, 0x58414749 ('XAGI')<br>
<B>versionnum</B><font size=3>: version number, currently 1<br>
<B>seqno</B><font size=3>: sequence number starting from 0<br>
<B>length</B><font size=3>: size in filesystem blocks of the allocation group<br>
<B>count</B><font size=3>: count of inodes allocated<br>
<B>root</B><font size=3>: block number of the root of the Btree holding inode allocation information<br>
<B>level</B><font size=3>: number of levels in the inode allocation Btree<br>
<B>freecount</B><font size=3>: count of allocated inodes that are not in use<br>
<B>newino</B><font size=3>: last inode number allocated<br>
<B>dirino</B><font size=3>: unused<br>
<B>unlinked</B><font size=3>: an array of inode numbers within the allocation group. The entries in the AGI block are the heads of lists which run through the inode <font size=3><B>next_unlinked</B> <font size=3>field. These inodes are to be unlinked the next time the filesystem is mounted</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.3846%">
<p><font size=3><B>attr</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>An attribute fork is organized as a Btree with the actual data embedded in the leaf blocks. The root of the Btree is found in block 0 of the fork. The index (sort order) of the Btree is the hash value of the attribute name. All the blocks contain a <font size=3><B>blkinfo</B> <font size=3>structure at the beginning, see type <font size=3><B>dir</B> <font size=3>for a descrip- tion. Nonleaf blocks are identical in format to those for version 1 and version 2 directories, see type <font size=3><B>dir</B> <font size=3>for a description. Leaf blocks can refer to ``local'' or ``remote'' attribute values. Local values are stored directly in the leaf block. Remote values are stored in an independent block in the attribute fork (with no structure). Leaf blocks contain the following fields:<br>
<B>hdr</B><font size=3>: header containing a <font size=3><B>blkinfo</B> <font size=3>structure <font size=3><B>info</B> <font size=3>(magic number 0xfbee), a <font size=3><B>count</B> <font size=3>of active entries, <font size=3><B>used- bytes</B> <font size=3>total bytes of names and values, the <font size=3><B>firstused</B> <font size=3>byte in the name area, <font size=3><B>holes</B> <font size=3>set if the block needs compaction, and array <font size=3><B>freemap</B> <font size=3>as for <font size=3><B>dir</B> <font size=3>leaf blocks<br>
<B>entries</B><font size=3>: array of structures containing a <font size=3><B>hashval</B><font size=3>, <font size=3><B>nameidx</B> <font size=3>(index into the block of the name), and flags <font size=3><B>incomplete</B><font size=3>, <font size=3><B>root</B><font size=3>, and <font size=3><B>local<br>
nvlist</B><font size=3>: array of structures describing the attribute names and values. Fields always present: <font size=3><B>valuelen</B> <font size=3>(length of value in bytes), <font size=3><B>namelen</B><font size=3>, and <font size=3><B>name</B><font size=3>. Fields present for local values: <font size=3><B>value</B> <font size=3>(value string). Fields present for remote values: <font size=3><B>valueblk</B> <font size=3>(fork block number of containing the value).</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.3846%">
<p><font size=3><B>bmapbt</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Files with many extents in their data or attribute fork will have the extents described by the contents of a Btree for that fork, instead of being stored directly in the inode. Each bmap Btree starts with a root block contained within the inode. The other levels of the Btree are stored in filesystem blocks. The blocks are linked to sibling left and right blocks at each level, as well as by pointers from parent to child blocks. Each block contains the following fields:<br>
<B>magic</B><font size=3>: bmap Btree block magic number, 0x424d4150 ('BMAP')<br>
<B>level</B><font size=3>: level of this block above the leaf level<br>
<B>numrecs</B><font size=3>: number of records or keys in the block<br>
<B>leftsib</B><font size=3>: left (logically lower) sibling block, 0 if none<br>
<B>rightsib</B><font size=3>: right (logically higher) sibling block, 0 if none<br>
<B>recs</B><font size=3>: [leaf blocks only] array of extent records. Each record contains <font size=3><B>startoff</B><font size=3>, <font size=3><B>startblock</B><font size=3>, <font size=3><B>blockcount</B><font size=3>, and <font size=3><B>extentflag</B> <font size=3>(1 if the extent is unwritten)<br>
<B>keys</B><font size=3>: [nonleaf blocks only] array of key records. These are the first key value of each block in the level below this one. Each record contains <font size=3><B>startoff<br>
ptrs</B><font size=3>: [nonleaf blocks only] array of child block pointers. Each pointer is a filesystem block number to</p>
</td>
</tr>
</table>
<br>
<!-- Page: 6  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="5.5385%">
<p><font size=3><B>bnobt</p>
</B></td>
<td valign="top" align="left"  width="3.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>the next level in the Btree</p>
<p><font size=3>There is one set of filesystem blocks forming the by-block-number allocation Btree for each allocation group. The root block of this Btree is designated by the <font size=3><B>bnoroot</B> <font size=3>field in the coresponding AGF block. The blocks are linked to sibling left and right blocks at each level, as well as by pointers from parent to child blocks. Each block has the following fields:<br>
<B>magic</B><font size=3>: BNOBT block magic number, 0x41425442 ('ABTB')<br>
<B>level</B><font size=3>: level number of this block, 0 is a leaf<br>
<B>numrecs</B><font size=3>: number of data entries in the block<br>
<B>leftsib</B><font size=3>: left (logically lower) sibling block, 0 if none<br>
<B>rightsib</B><font size=3>: right (logically higher) sibling block, 0 if none<br>
<B>recs</B><font size=3>: [leaf blocks only] array of freespace records. Each record contains <font size=3><B>startblock</B> <font size=3>and <font size=3><B>blockcount<br>
keys</B><font size=3>: [nonleaf blocks only] array of key records. These are the first value of each block in the level below this one. Each record contains <font size=3><B>startblock</B> <font size=3>and <font size=3><B>blockcount<br>
ptrs</B><font size=3>: [nonleaf blocks only] array of child block pointers. Each pointer is a block number within the allo- cation group to the next level in the Btree</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="5.5385%">
<p><font size=3><B>cntbt</p>
</B></td>
<td valign="top" align="left"  width="3.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>There is one set of filesystem blocks forming the by-block-count allocation Btree for each allocation group. The root block of this Btree is designated by the coresponding AGF block. The blocks are linked to sibling left and right blocks at each level, as well as by pointers from parent to child blocks. Each block has the following fields:<br>
<B>magic</B><font size=3>: CNTBT block magic number, 0x41425443 ('ABTC')<br>
<B>level</B><font size=3>: level number of this block, 0 is a leaf<br>
<B>numrecs</B><font size=3>: number of data entries in the block<br>
<B>leftsib</B><font size=3>: left (logically lower) sibling block, 0 if none<br>
<B>rightsib</B><font size=3>: right (logically higher) sibling block, 0 if none<br>
<B>recs</B><font size=3>: [leaf blocks only] array of freespace records. Each record contains <font size=3><B>startblock</B> <font size=3>and <font size=3><B>blockcount<br>
keys</B><font size=3>: [nonleaf blocks only] array of key records. These are the first value of each block in the level below this one. Each record contains <font size=3><B>blockcount</B> <font size=3>and <font size=3><B>startblock<br>
ptrs</B><font size=3>: [nonleaf blocks only] array of child block pointers. Each pointer is a block number within the allo- cation group to the next level in the Btree</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="5.5385%">
<p><font size=3><B>data</p>
</B></td>
<td valign="top" align="left"  width="3.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>User file blocks, and other blocks whose type is unknown, have this type for display purposes in <font size=3><I>xfs_db</I><font size=3>. The block data is displayed in hexadecimal format.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="5.5385%">
<p><font size=3><B>dir</p>
</B></td>
<td valign="top" align="left"  width="3.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>A version 1 directory is organized as a Btree with the directory data embedded in the leaf blocks. The root of the Btree is found in block 0 of the file. The index (sort order) of the Btree is the hash value of the entry name. All the blocks contain a <font size=3><B>blkinfo</B> <font size=3>structure at the beginning with the following fields:<br>
<B>forw</B><font size=3>: next sibling block<br>
<B>back</B><font size=3>: previous sibling block<br>
<B>magic</B><font size=3>: magic number for this block type</p>
<p><font size=3>The nonleaf (node) blocks have the following fields:<br>
<B>hdr</B><font size=3>: header containing a <font size=3><B>blkinfo</B> <font size=3>structure <font size=3><B>info</B> <font size=3>(magic number 0xfebe), the <font size=3><B>count</B> <font size=3>of active entries, and the <font size=3><B>level</B> <font size=3>of this block above the leaves<br>
<B>btree</B><font size=3>: array of entries containing <font size=3><B>hashval</B> <font size=3>and <font size=3><B>before</B> <font size=3>fields. The <font size=3><B>before</B> <font size=3>value is a block number within the directory file to the child block, the <font size=3><B>hashval</B> <font size=3>is the last hash value in that block</p>
<p><font size=3>The leaf blocks have the following fields:<br>
<B>hdr</B><font size=3>: header containing a <font size=3><B>blkinfo</B> <font size=3>structure <font size=3><B>info</B> <font size=3>(magic number 0xfeeb), the <font size=3><B>count</B> <font size=3>of active entries, <font size=3><B>namebytes</B> <font size=3>(total name string bytes), <font size=3><B>holes</B> <font size=3>flag (block needs compaction), and <font size=3><B>freemap</B> <font size=3>(array of <font size=3><B>base</B><font size=3>, <font size=3><B>size</B> <font size=3>entries for free regions)<br>
<B>entries</B><font size=3>: array of structures containing <font size=3><B>hashval</B><font size=3>, <font size=3><B>nameidx</B> <font size=3>(byte index into the block of the name string), and <font size=3><B>namelen<br>
namelist</B><font size=3>: array of structures containing <font size=3><B>inumber</B> <font size=3>and <font size=3><B>name</p>
</B></td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="5.5385%">
<p><font size=3><B>dir2</p>
</B></td>
<td valign="top" align="left"  width="3.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>A version 2 directory has four kinds of blocks. Data blocks start at offset 0 in the file. There are two kinds of data blocks: single-block directories have the leaf information embedded at the end of the block, data blocks in multi-block directories do not. Node and leaf blocks start at offset 32GB (with either a single leaf block or the root node block). Freespace blocks start at offset 64GB. The node and leaf blocks form a Btree, with references to the data in the data blocks. The freespace blocks form an index of longest free spaces within the data blocks.</p>
<p><font size=3>A single-block directory block contains the following fields:<br>
<B>bhdr</B><font size=3>: header containing <font size=3><B>magic</B> <font size=3>number 0x58443242 ('XD2B') and an array <font size=3><B>bestfree</B> <font size=3>of the longest 3</p>
</td>
</tr>
</table>
<br>
<!-- Page: 7  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>free spaces in the block (<font size=3><B>offset</B><font size=3>, <font size=3><B>length</B><font size=3>)<br>
<B>bu</B><font size=3>: array of union structures. Each element is either an entry or a freespace. For entries, there are the following fields: <font size=3><B>inumber</B><font size=3>, <font size=3><B>namelen</B><font size=3>, <font size=3><B>name</B><font size=3>, and <font size=3><B>tag</B><font size=3>. For freespace, there are the following fields: <font size=3><B>free- tag</B> <font size=3>(0xffff), <font size=3><B>length</B><font size=3>, and <font size=3><B>tag</B><font size=3>. The <font size=3><B>tag</B> <font size=3>value is the byte offset in the block of the start of the entry it is contained in<br>
<B>bleaf</B><font size=3>: array of leaf entries containing <font size=3><B>hashval</B> <font size=3>and <font size=3><B>address</B><font size=3>. The <font size=3><B>address</B> <font size=3>is a 64-bit word offset into the file<br>
<B>btail</B><font size=3>: tail structure containing the total <font size=3><B>count</B> <font size=3>of leaf entries and <font size=3><B>stale</B> <font size=3>count of unused leaf entries</p>
<p><font size=3>A data block contains the following fields:<br>
<B>dhdr</B><font size=3>: header containing <font size=3><B>magic</B> <font size=3>number 0x58443244 ('XD2D') and an array <font size=3><B>bestfree</B> <font size=3>of the longest 3 free spaces in the block (<font size=3><B>offset</B><font size=3>, <font size=3><B>length</B><font size=3>)<br>
<B>du</B><font size=3>: array of union structures as for <font size=3><B>bu</p>
</B><p><font size=3>Leaf blocks have two possible forms. If the Btree consists of a single leaf then the freespace informa- tion is in the leaf block, otherwise it is in separate blocks and the root of the Btree is a node block. A leaf block contains the following fields:<br>
<B>lhdr</B><font size=3>: header containing a <font size=3><B>blkinfo</B> <font size=3>structure <font size=3><B>info</B> <font size=3>(magic number 0xd2f1 for the single leaf case, 0xd2ff for the true Btree case), the total <font size=3><B>count</B> <font size=3>of leaf entries, and <font size=3><B>stale</B> <font size=3>count of unused leaf entries<br>
<B>lents</B><font size=3>: leaf entries, as for <font size=3><B>bleaf<br>
lbests</B><font size=3>: [single leaf only] array of values which represent the longest freespace in each data block in the directory<br>
<B>ltail</B><font size=3>: [single leaf only] tail structure containing <font size=3><B>bestcount</B> <font size=3>count of <font size=3><B>lbests</p>
</B><p><font size=3>A node block is identical to that for types <font size=3><B>attr</B> <font size=3>and <font size=3><B>dir</B><font size=3>.</p>
<p><font size=3>A freespace block contains the following fields:<br>
<B>fhdr</B><font size=3>: header containing <font size=3><B>magic</B> <font size=3>number 0x58443246 ('XD2F'), <font size=3><B>firstdb</B> <font size=3>first data block number covered by this freespace block, <font size=3><B>nvalid</B> <font size=3>number of valid entries, and <font size=3><B>nused</B> <font size=3>number of entries representing real data blocks<br>
<B>fbests</B><font size=3>: array of values as for <font size=3><B>lbests</p>
</B></td>
</tr>
</table>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="5.2308%">
<p><font size=3><B>dqblk</p>
</B></td>
<td valign="top" align="left"  width="4.0000%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>The quota information is stored in files referred to by the superblock <font size=3><B>uquotino</B> <font size=3>and <font size=3><B>pquotino</B> <font size=3>fields. Each filesystem block in a quota file contains a constant number of quota entries. The quota entry size is currently 136 bytes, so with a 4KB filesystem block size there are 30 quota entries per block. The <font size=3><B>dquot</B> <font size=3>command is used to locate these entries in the filesystem. The file entries are indexed by the user or project identifier to determine the block and offset. Each quota entry has the following fields:<br>
<B>magic</B><font size=3>: magic number, 0x4451 ('DQ')<br>
<B>version</B><font size=3>: version number, currently 1<br>
<B>flags</B><font size=3>: flags, values include 0x01 for user quota, 0x02 for project quota<br>
<B>id</B><font size=3>: user or project identifier<br>
<B>blk_hardlimit</B><font size=3>: absolute limit on blocks in use<br>
<B>blk_softlimit</B><font size=3>: preferred limit on blocks in use<br>
<B>ino_hardlimit</B><font size=3>: absolute limit on inodes in use<br>
<B>ino_softlimit</B><font size=3>: preferred limit on inodes in use<br>
<B>bcount</B><font size=3>: blocks actually in use<br>
<B>icount</B><font size=3>: inodes actually in use<br>
<B>itimer</B><font size=3>: time when service will be refused if soft limit is violated for inodes<br>
<B>btimer</B><font size=3>: time when service will be refused if soft limit is violated for blocks<br>
<B>iwarns</B><font size=3>: number of warnings issued about inode limit violations<br>
<B>bwarns</B><font size=3>: number of warnings issued about block limit violations<br>
<B>rtb_hardlimit</B><font size=3>: absolute limit on realtime blocks in use<br>
<B>rtb_softlimit</B><font size=3>: preferred limit on realtime blocks in use<br>
<B>rtbcount</B><font size=3>: realtime blocks actually in use<br>
<B>rtbtimer</B><font size=3>: time when service will be refused if soft limit is violated for realtime blocks<br>
<B>rtbwarns</B><font size=3>: number of warnings issued about realtime block limit violations</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="5.2308%">
<p><font size=3><B>inobt</p>
</B></td>
<td valign="top" align="left"  width="4.0000%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>There is one set of filesystem blocks forming the inode allocation Btree for each allocation group. The root block of this Btree is designated by the <font size=3><B>root</B> <font size=3>field in the coresponding AGI block. The blocks are linked to sibling left and right blocks at each level, as well as by pointers from parent to child blocks. Each block has the following fields:<br>
<B>magic</B><font size=3>: INOBT block magic number, 0x49414254 ('IABT')<br>
<B>level</B><font size=3>: level number of this block, 0 is a leaf</p>
</td>
</tr>
</table>
<br>
<!-- Page: 8  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3><B>numrecs</B><font size=3>: number of data entries in the block<br>
<B>leftsib</B><font size=3>: left (logically lower) sibling block, 0 if none<br>
<B>rightsib</B><font size=3>: right (logically higher) sibling block, 0 if none<br>
<B>recs</B><font size=3>: [leaf blocks only] array of inode records. Each record contains <font size=3><B>startino</B> <font size=3>allocation-group relative inode number, <font size=3><B>freecount</B> <font size=3>count of free inodes in this chunk, and <font size=3><B>free</B> <font size=3>bitmap, LSB corresponds to inode 0<br>
<B>keys</B><font size=3>: [nonleaf blocks only] array of key records. These are the first value of each block in the level below this one. Each record contains <font size=3><B>startino<br>
ptrs</B><font size=3>: [nonleaf blocks only] array of child block pointers. Each pointer is a block number within the allo- cation group to the next level in the Btree</p>
</td>
</tr>
</table>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="4.9231%">
<p><font size=3><B>inode</p>
</B></td>
<td valign="top" align="left"  width="4.3077%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Inodes are allocated in ``chunks'' of 64 inodes each. Usually a chunk is multiple filesystem blocks, although there are cases with large filesystem blocks where a chunk is less than one block. The inode Btree (see <font size=3><B>inobt</B> <font size=3>above) refers to the inode numbers per allocation group. The inode numbers directly reflect the location of the inode block on disk. Use the <font size=3><B>inode</B> <font size=3>command to point <font size=3><I>xfs_db</I> <font size=3>to a specific inode. Each inode contains four regions: <font size=3><B>core</B><font size=3>, <font size=3><B>next_unlinked</B><font size=3>, <font size=3><B>u</B><font size=3>, and <font size=3><B>a</B><font size=3>. <font size=3><B>core</B> <font size=3>contains the fixed infor- mation. <font size=3><B>next_unlinked</B> <font size=3>is separated from the core due to journalling considerations, see type <font size=3><B>agi</B> <font size=3>field <font size=3><B>unlinked</B><font size=3>. <font size=3><B>u</B> <font size=3>is a union structure that is different in size and format depending on the type and represen- tation of the file data (``data fork''). <font size=3><B>a</B> <font size=3>is an optional union structure to describe attribute data, that is dif- ferent in size, format, and location depending on the presence and representation of attribute data, and the size of the <font size=3><B>u</B> <font size=3>data (``attribute fork''). <font size=3><I>xfs_db</I> <font size=3>automatically selects the proper union members based on information in the inode.<br>
The following are fields in the inode core:<br>
<B>magic</B><font size=3>: inode magic number, 0x494e ('IN')<br>
<B>mode</B><font size=3>: mode and type of file, as described in <font size=3><B>chmod</B><font size=3>(2), <font size=3><B>mknod</B><font size=3>(2), and <font size=3><B>stat</B><font size=3>(2)<br>
<B>version</B><font size=3>: inode version, 1 or 2<br>
<B>format</B><font size=3>: format of <font size=3><B>u</B> <font size=3>union data (0: dev_t, 1: local file - in-inode directory or symlink, 2: extent list, 3: Btree root, 4: unique id [unused])<br>
<B>nlinkv1</B><font size=3>: number of links to the file in a version 1 inode<br>
<B>nlinkv2</B><font size=3>: number of links to the file in a version 2 inode<br>
<B>projid</B><font size=3>: owner's project id (version 2 inode only)<br>
<B>uid</B><font size=3>: owner's user id<br>
<B>gid</B><font size=3>: owner's group id<br>
<B>atime</B><font size=3>: time last accessed (seconds and nanoseconds)<br>
<B>mtime</B><font size=3>: time last modified<br>
<B>ctime</B><font size=3>: time created or inode last modified<br>
<B>size</B><font size=3>: number of bytes in the file<br>
<B>nblocks</B><font size=3>: total number of blocks in the file including indirect and attribute<br>
<B>extsize</B><font size=3>: basic/minimum extent size for the file, used only for realtime<br>
<B>nextents</B><font size=3>: number of extents in the data fork<br>
<B>naextents</B><font size=3>: number of extents in the attribute fork<br>
<B>forkoff</B><font size=3>: attribute fork offset in the inode, in 64-bit words from the start of <font size=3><B>u<br>
aformat</B><font size=3>: format of <font size=3><B>a</B> <font size=3>data (1: local attribute data, 2: extent list, 3: Btree root)<br>
<B>dmevmask</B><font size=3>: DMAPI event mask<br>
<B>dmstate</B><font size=3>: DMAPI state information<br>
<B>newrtbm</B><font size=3>: file is the realtime bitmap and is ``new'' format<br>
<B>prealloc</B><font size=3>: file has preallocated data space after EOF<br>
<B>realtime</B><font size=3>: file data is in the realtime subvolume<br>
<B>gen</B><font size=3>: inode generation number</p>
<p><font size=3>The following fields are in the <font size=3><B>u</B> <font size=3>data fork union:<br>
<B>bmbt</B><font size=3>: bmap Btree root. This looks like a <font size=3><B>bmapbtd</B> <font size=3>block with redundant information removed<br>
<B>bmx</B><font size=3>: array of extent descriptors<br>
<B>dev</B><font size=3>: dev_t for the block or character device<br>
<B>sfdir</B><font size=3>: shortform (in-inode) version 1 directory. This consists of a <font size=3><B>hdr</B> <font size=3>containing the <font size=3><B>parent</B> <font size=3>inode num- ber and a <font size=3><B>count</B> <font size=3>of active entries in the directory, followed by an array <font size=3><B>list</B> <font size=3>of <font size=3><B>hdr</B><font size=3>.<font size=3><B>count</B> <font size=3>entries. Each such entry contains <font size=3><B>inumber</B><font size=3>, <font size=3><B>namelen</B><font size=3>, and <font size=3><B>name</B> <font size=3>string<br>
<B>sfdir2</B><font size=3>: shortform (in-inode) version 2 directory. This consists of a <font size=3><B>hdr</B> <font size=3>containing a <font size=3><B>count</B> <font size=3>of active entries in the directory, an <font size=3><B>i8count</B> <font size=3>of entries with inumbers that don't fit in a 32-bit value, and the <font size=3><B>par- ent</B> <font size=3>inode number, followed by an array <font size=3><B>list</B> <font size=3>of <font size=3><B>hdr</B><font size=3>.<font size=3><B>count</B> <font size=3>entries. Each such entry contains <font size=3><B>namelen</B><font size=3>, a saved <font size=3><B>offset</B> <font size=3>used when the directory is converted to a larger form, a <font size=3><B>name</B> <font size=3>string, and the <font size=3><B>inumber<br>
symlink</B><font size=3>: symbolic link string value</p>
</td>
</tr>
</table>
<br>
<!-- Page: 9  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>The following fields are in the <font size=3><B>a</B> <font size=3>attribute fork union if it exists:<br>
<B>bmbt</B><font size=3>: bmap Btree root, as above<br>
<B>bmx</B><font size=3>: array of extent descriptors<br>
<B>sfattr</B><font size=3>: shortform (in-inode) attribute values. This consists of a <font size=3><B>hdr</B> <font size=3>containing a <font size=3><B>totsize</B> <font size=3>(total size in bytes) and a <font size=3><B>count</B> <font size=3>of active entries, followed by an array <font size=3><B>list</B> <font size=3>of <font size=3><B>hdr</B><font size=3>.<font size=3><B>count</B> <font size=3>entries. Each such entry contains <font size=3><B>namelen</B><font size=3>, <font size=3><B>valuelen</B><font size=3>, <font size=3><B>root</B> <font size=3>flag, <font size=3><B>name</B><font size=3>, and <font size=3><B>value</p>
</B></td>
</tr>
</table>
<p><font size=3><B>log</B> <font size=3>Log blocks contain the journal entries for XFS. It's not useful to examine these with <font size=3><I>xfs_db</I><font size=3>, use<br>
<span style=" text-indent: 0.6000in;"></span><I>xfs_logprint</I><font size=3>(1M) instead.</p>
<a name="rtbitmap"></a><h2>rtbitmap</h2>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>If the filesystem has a realtime subvolume, then the <font size=3><B>rbmino</B> <font size=3>field in the superblock refers to a file that contains the realtime bitmap. Each bit in the bitmap file controls the allocation of a single realtime extent (set == free). The bitmap is processed in 32-bit words, the LSB of a word is used for the first extent controlled by that bitmap word. The <font size=3><B>atime</B> <font size=3>field of the realtime bitmap inode contains a counter that is used to control where the next new realtime file will start.</p>
</td>
</tr>
</table>
<p><font size=3><B>rtsummary</p>
</B>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>If the filesystem has a realtime subvolume, then the <font size=3><B>rsumino</B> <font size=3>field in the superblock refers to a file that contains the realtime summary data. The summary file contains a two-dimensional array of 16-bit val- ues. Each value counts the number of free extent runs (consecutive free realtime extents) of a given range of sizes that starts in a given bitmap block. The size ranges are binary buckets (low size in the bucket is a power of 2). There are as many size ranges as are necessary given the size of the realtime subvolume. The first dimension is the size range, the second dimension is the starting bitmap block number (adjacent entries are for the same size, adjacent bitmap blocks).</p>
</td>
</tr>
</table>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.1538%">
<p><font size=3><B>sb</p>
</B></td>
<td valign="top" align="left"  width="7.0769%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>There is one sb (superblock) structure per allocation group. It is the first disk block in the allocation group. Only the first one (block 0 of the filesystem) is actually used; the other blocks are redundant information for <font size=3><I>xfs_repair</I><font size=3>(1M) to use if the first superblock is damaged. Fields defined:<br>
<B>magicnum</B><font size=3>: superblock magic number, 0x58465342 ('XFSB')<br>
<B>blocksize</B><font size=3>: filesystem block size in bytes<br>
<B>dblocks</B><font size=3>: number of filesystem blocks present in the data subvolume<br>
<B>rblocks</B><font size=3>: number of filesystem blocks present in the realtime subvolume<br>
<B>rextents</B><font size=3>: number of realtime extents that <font size=3><B>rblocks</B> <font size=3>contain<br>
<B>uuid</B><font size=3>: unique identifier of the filesystem<br>
<B>logstart</B><font size=3>: starting filesystem block number of the log (journal). If this value is 0 the log is ``external''<br>
<B>rootino</B><font size=3>: root inode number<br>
<B>rbmino</B><font size=3>: realtime bitmap inode number<br>
<B>rsumino</B><font size=3>: realtime summary data inode number<br>
<B>rextsize</B><font size=3>: realtime extent size in filesystem blocks<br>
<B>agblocks</B><font size=3>: size of an allocation group in filesystem blocks<br>
<B>agcount</B><font size=3>: number of allocation groups<br>
<B>rbmblocks</B><font size=3>: number of realtime bitmap blocks<br>
<B>logblocks</B><font size=3>: number of log blocks (filesystem blocks)<br>
<B>versionnum</B><font size=3>: filesystem version information. This value is currently 1, 2, 3, or 4 in the low 4 bits. If the low bits are 4 then the other bits have additional meanings. 1 is the original value. 2 means that attributes were used. 3 means that version 2 inodes (large link counts) were used. 4 is the bitmask ver- sion of the version number. In this case, the other bits are used as flags (0x0010: attributes were used, 0x0020: version 2 inodes were used, 0x0040: quotas were used, 0x0080: inode cluster alignment is in force, 0x0100: data stripe alignment is in force, 0x0200: the <font size=3><B>shared_vn</B> <font size=3>field is used, 0x1000: unwritten extent tracking is on, 0x2000: version 2 directories are in use)<br>
<B>sectsize</B><font size=3>: sector size in bytes, currently always 512. This is the size of the superblock and the other header blocks<br>
<B>inodesize</B><font size=3>: inode size in bytes<br>
<B>inopblock</B><font size=3>: number of inodes per filesystem block<br>
<B>fname</B><font size=3>: obsolete, filesystem name<br>
<B>fpack</B><font size=3>: obsolete, filesystem pack name<br>
<B>blocklog</B><font size=3>: log2 of <font size=3><B>blocksize<br>
sectlog</B><font size=3>: log2 of <font size=3><B>sectsize<br>
inodelog</B><font size=3>: log2 of <font size=3><B>inodesize<br>
inopblog</B><font size=3>: log2 of <font size=3><B>inopblock<br>
agblklog</B><font size=3>: log2 of <font size=3><B>agblocks</B> <font size=3>(rounded up)<br>
<B>rextslog</B><font size=3>: log2 of <font size=3><B>rextents<br>
inprogress</B><font size=3>: <font size=3><I>mkfs_xfs</I><font size=3>(1M) aborted before completing this filesystem</p>
</td>
</tr>
</table>
<br>
<!-- Page: 10  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->

<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="9.2308%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3><B>imax_pct</B><font size=3>: maximum percentage of filesystem space used for inode blocks<br>
<B>icount</B><font size=3>: number of allocated inodes<br>
<B>ifree</B><font size=3>: number of allocated inodes that are not in use<br>
<B>fdblocks</B><font size=3>: number of free data blocks<br>
<B>frextents</B><font size=3>: number of free realtime extents<br>
<B>uquotino</B><font size=3>: user quota inode number<br>
<B>pquotino</B><font size=3>: project quota inode number; this is currently unused<br>
<B>qflags</B><font size=3>: quota status flags (0x01: user quota accounting is on, 0x02: user quota limits are enforced, 0x04: quotacheck has been run on user quotas, 0x08: project quota accounting is on, 0x10: project quota lim- its are enforced, 0x20: quotacheck has been run on project quotas)<br>
<B>flags</B><font size=3>: random flags. 0x01: only read-only mounts are allowed<br>
<B>shared_vn</B><font size=3>: shared version number (shared readonly filesystems)<br>
<B>inoalignmt</B><font size=3>: inode chunk alignment in filesystem blocks<br>
<B>unit</B><font size=3>: stripe or RAID unit<br>
<B>width</B><font size=3>: stripe or RAID width<br>
<B>dirblklog</B><font size=3>: log2 of directory block size (filesystem blocks)</p>
</td>
</tr>
</table>
<p><font size=3><B>symlink</B> <font size=3>Symbolic link blocks are used only when the symbolic link value does not fit inside the inode. The block<br>
<span style=" text-indent: 0.6000in;"></span>content is just the string value. Bytes past the logical end of the symbolic link value have arbitrary val-<br>
<span style=" text-indent: 0.6000in;"></span>ues.</p>
<a name="DIAGNOSTICS"></a><h2>DIAGNOSTICS</h2><p><font size=3>Many messages can come from the <font size=3><B>check</B> <font size=3>(<font size=3><B>blockget</B><font size=3>) command; these are documented in <font size=3><I>xfs_check</I><font size=3>(1M).</p>
<a name="SEE ALSO"></a><h2>SEE ALSO</h2><p><font size=3>mkfs_xfs(1M), xfs_check(1M), xfs_copy(1M), xfs_logprint(1M), xfs_ncheck(1M), xfs_repair(1M), chmod(2), mknod(2), stat(2), xfs(4).<br>
</p>
</body>
</html>