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

Revision 1.1, Mon Apr 24 19:46:05 2000 UTC (17 years, 6 months ago) by cattelan
Branch: MAIN 

Added man pages

<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="#SEE ALSO">SEE ALSO</a><br>
<!-- Creator     : groff version 1.15  -->
<!-- CreationDate: Mon Apr 24 10:40:33 2000
 -->
<!-- Total number of pages: 1 -->
<!-- Page: 1 -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<a name="NAME"></a><h2>NAME</h2><p><font size=3>xfs_logprint - print the log of an XFS filesystem</p>
<a name="SYNOPSIS"></a><h2>SYNOPSIS</h2><p><font size=3><B>xfs_logprint</B> <font size=3>[ options ] device-name<br>
<B>xfs_logprint -f</B> <font size=3>[ options ] filename</p>
<a name="DESCRIPTION"></a><h2>DESCRIPTION</h2><p><font size=3><I>xfs_logprint</I> <font size=3>prints the log of an XFS filesystem (see <font size=3><I>xfs</I><font size=3>(4)). The <font size=3><I>device-name</I> <font size=3>argument is the pathname of the partition or logical volume containing the filesystem. The contents of the filesystem remain undisturbed. There are two major modes of operation in <font size=3><I>xfs_logprint</I><font size=3>.</p>
<p><font size=3>One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the <font size=3><B>-t</B> <font size=3>option. The transactional view prints only the portion of the log that pertains to recovery. In other words, it prints out complete transactions between the tail and the head. This view tries to display each transaction without regard to how they are split across log records.</p>
<p><font size=3>The second mode starts printing out information from the beginning of the log. Some error blocks might print out in the beginning because the last log record usually overlaps the oldest log record. A message is printed when the physical end of the log is reached and when the logical end of the log is reached. A log record view is displayed one record at a time. Transactions that span log records may not be decoded fully.</p>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="18.9231%">
<p><font size=3>Common options are:</p>
<p><font size=3><B>-b</p>
</B></td>
<td valign="top" align="left"  width="1.0769%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>Extract and print buffer information. Only used in transactional view.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="18.9231%">
<p><font size=3><B>-D</p>
</B><p><font size=3><B>-e</p>
</B></td>
<td valign="top" align="left"  width="1.0769%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>Don't decode anything; just print data.</p>
<p><font size=3>Exit when an error is found in the log. Normally, <font size=3><I>xfs_logprint</I> <font size=3>tries to continue and unwind from bad logs. However, sometimes it just dies in bad ways. Using this option prevents core dumps.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="18.9231%">
<p><font size=3><B>-f</p>
</B><p><font size=3><B>-i</p>
</B><p><font size=3><B>-q</p>
</B><p><font size=3><B>-n</p>
</B><p><font size=3><B>-o</p>
</B></td>
<td valign="top" align="left"  width="1.0769%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>The log is a file.</p>
<p><font size=3>Extract and print inode information. Only used in transactional view.</p>
<p><font size=3>Extract and print quota information. Only used in transactional view.</p>
<p><font size=3>Don't try and interpret log data; just interpret log header information.</p>
<p><font size=3>Also print buffer data in hex. Normally, buffer data is just decoded, so better information<br>
can be printed.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="18.9231%">
<p><font size=3><B>-s</B> <font size=3><I>start-block</p>
</I><p><font size=3><B>-t</p>
</B></td>
<td valign="top" align="left"  width="1.0769%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>Override any notion of where to start printing.</p>
<p><font size=3>Print out the transactional view.</p>
</td>
</tr>
</table>
<br>
<a name="SEE ALSO"></a><h2>SEE ALSO</h2><p><font size=3>mkfs_xfs(1M), mount(1M).<br>
</p>
</body>
</html>