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

Revision 1.1, Wed Sep 27 05:01:47 2000 UTC (17 years, 1 month ago) by xfs
Branch: MAIN
CVS Tags: HEAD 

Update manpages.
These changes from Martin Peterson.

<html>
<head>
<meta name="Content-Style" content="text/css">
</head>
<body>
<a href="#NAME">NAME</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#qnoenforce">qnoenforce</a><br>
<a href="#pqnoenforce">pqnoenforce</a><br>
<a href="#FILES">FILES</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<!-- Creator     : groff version 1.15  -->
<!-- CreationDate: Tue Sep 26 23:59:40 2000
 -->
<!-- Total number of pages: 2 -->
<!-- Page: 1 -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<a name="NAME"></a><h2>NAME</h2><p><font size=3>xfs_fstab - static information about filesystems (XFS extensions)</p>
<a name="DESCRIPTION"></a><h2>DESCRIPTION</h2><p><font size=3>The file <font size=3><I>/etc/fstab</I> <font size=3>describes the filesystems and swapping partitions used by the local machine. The system administrator can modify it with a text editor. It is read by commands that mount, unmount, and check the consis- tency of filesystems. The file consists of a number of lines of the form:</p>
<p><span style=" text-indent: 0.2400in;"></span><font size=3><I>filesystem directory type options frequency pass</p>
</I><p><font size=3>For example:</p>
<p><span style=" text-indent: 0.2400in;"></span><font size=3>/dev/root / xfs rw 0 0</p>
<p><font size=3>Fields are separated by white space; a `#' as the first non-white space character indicates a comment.</p>
<p><font size=3>The <font size=3><I>mnt_dir</I> <font size=3>field is the full pathname of the directory to be mounted on. The <font size=3><I>mnt_type</I> <font size=3>field determines how the <font size=3><I>mnt_fsname</I> <font size=3>and <font size=3><I>mnt_opts</I> <font size=3>fields are interpreted. Here is a list of the filesystem types currently supported, and the way each of them interprets these fields:</p>
<p><font size=3><B>xfs</B> <font size=3><I>mnt_fsname</I> <font size=3>must be a block special device (for example, <font size=3><I>/dev/root</I><font size=3>) or a logical volume. <font size=3><I>mnt_freq</I> <font size=3>is<br>
<span style=" text-indent: 0.6000in;"></span>not used in current IRIX systems.</p>
<p><font size=3><I>mnt_passno</I> <font size=3>can be used to control the behavior of parallel filesystem checking on bootup, see <font size=3><I>fsck</I><font size=3>(1M).</p>
<p><font size=3>The <font size=3><I>mnt_opts</I> <font size=3>field contains a list of comma-separated option words. Some <font size=3><I>mnt_opts</I> <font size=3>are valid for all filesystem types, while others apply to a specific type only.</p>
<p><font size=3>Options specific to <font size=3><B>xfs</B> <font size=3>filesystems are:</p>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.5385%">
<p><font size=3><B>quota</p>
</B><p><font size=3><B>biosize</p>
</B></td>
<td valign="top" align="left"  width="1.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Disk quota accounting enabled, and limits enforced.</p>
<p><font size=3>The biosize (buffered I/O size) option can be used to set the default preferred buffered I/O size for filesystem. The default preferred I/O size is 64K. The biosize option can be used to decrease the pre- ferred I/O size. The size must be expressed as the log (base2) of the desired I/O size. Valid values for this option are 14 through 16, inclusive (e.g. 16K, 32K, and 64K bytes). On machines with 4K size pages, 13 (8 Kbytes) is also a valid size. The preferred buffered I/O size can also be altered on a per-file basis using the <font size=3><I>fcntl</I> <font size=3>system call. See <font size=3><I>fcntl</I><font size=3>(2) for further details.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.5385%">
<p><font size=3><B>dmi</p>
</B><p><font size=3><B>logbufs</p>
</B></td>
<td valign="top" align="left"  width="1.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Enable the Data Management Interface event callouts.</p>
<p><font size=3>Set the number of in memory log buffers. Valid numbers range from 2-8 inclusive. The default value is 8 buffers for filesystems with a blocksize of 64K, 4 buffers for filesystems with a blocksize of 32K, 3 buffers for filesystems with a blocksize of 16K, and 2 buffers for all other configurations. Increasing the number of buffers may increase performance on some workloads at the cost of the memory used for the extra log buffers and their associated control structures.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="7.5385%">
<p><font size=3><B>noalign</p>
</B><p><font size=3><B>noatime</p>
</B></td>
<td valign="top" align="left"  width="1.6923%">
</td>
<td valign="top" align="left"  width="90.7692%">
<p><font size=3>Data allocations will not be aligned at stripe unit boundaries.</p>
<p><font size=3>Access timestamps are not updated when a file is read.</p>
</td>
</tr>
</table>
<p><font size=3><B>norecovery</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>The filesystem will be mounted without running log recovery. If the filesystem was not cleanly unmounted, it is likely to be inconsistent when mounted in norecovery mode. Some files or directories may not be accessible because of this. Filesystems mounted norecovery must be mounted read-only or the mount will fail.</p>
</td>
</tr>
</table>
<p><font size=3><B>osyncisdsync<br>
<span style=" text-indent: 0.6000in;"></span></B>Make writes to files opened with the O_SYNC flag set behave as if the O_DSYNC flag had been used<br>
<span style=" text-indent: 0.6000in;"></span>instead. This can result in better performance without compromising data safety. However if this<br>
<span style=" text-indent: 0.6000in;"></span>option in effect, timestamp updates from O_SYNC writes can be lost if the system crashes.</p>
<a name="qnoenforce"></a><h2>qnoenforce</h2><p><span style=" text-indent: 0.6000in;"></span><font size=3>Disk quota accounting enabled, but limits are not enforced.</p>
<p><font size=3><B>pquota</B> <font size=3>Project disk quota accounting enabled and limits enforced.</p>
<a name="pqnoenforce"></a><h2>pqnoenforce</h2><p><span style=" text-indent: 0.6000in;"></span><font size=3>Project disk quota accounting enabled, but limits are not enforced.</p>
<p><font size=3><B>sunit</B><font size=3>=<font size=3><I>value</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>Used to specify the stripe unit for a RAID device or a xlv stripe volume. <font size=3><I>value</I> <font size=3>has to be specified in 512-byte block units. If this option is not specified and the filesystem was made on a stripe volume or the stripe unit was specified for the RAID device at mkfs time, then the mount system call will restore the value from the superblock. For filesystems that are made directly on RAID devices, this option can be used to override the information in the superblock if the underlying disk layout changes after the</p>
</td>
</tr>
</table>
<br>
<!-- Page: 2  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<p><span style=" text-indent: 0.6000in;"></span><font size=3>filesystem has been mkfsed. If the filesystem is made on a xlv volume, then this will be done implicitly.</p>
<p><font size=3><B>swidth</B><font size=3>=<font size=3><I>value</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>Used to specify the stripe width for a RAID device or a xlv stripe volume. <font size=3><I>value</I> <font size=3>has to be specified in 512-byte block units. If this option is not specified, and the filesystem was made on a stripe volume or the stripe width was specified for the RAID device at mkfs time, then the mount system call will restore the value from the superblock. For filesystems that are made directly on RAID devices, this option can be used to override the information in the superblock if the underlying disk layout changes after the filesystem has been mkfsed. If the filesystem is made on a xlv volume, then this will be done implicitly. This option is required if the <font size=3><B>-o sunit</B> <font size=3>option has been specified. Also it has to be a multiple of the sunit option.</p>
</td>
</tr>
</table>
<p><font size=3><B>wsync</B> <font size=3>All operations that modify the filesystem are synchronous except for writes to user files (e.g. create,<br>
<span style=" text-indent: 0.6000in;"></span>unlink, mv, truncate, etc.). This option can be used in conjunction with exporting a filesystem -wsync to<br>
<span style=" text-indent: 0.6000in;"></span>obtain NFS write-synchronous semantics, if so desired. See <font size=3><B>exports(5)</B> <font size=3>for further information.</p>
<a name="FILES"></a><h2>FILES</h2><p><font size=3>/etc/fstab</p>
<a name="SEE ALSO"></a><h2>SEE ALSO</h2><p><font size=3>xfs(5).<br>
</p>
</body>
</html>