<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="#PRACTICAL USE">PRACTICAL USE</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<!-- Creator : groff version 1.15 -->
<!-- CreationDate: Mon Apr 24 10:40:32 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_growfs - expand an XFS filesystem</p>
<a name="SYNOPSIS"></a><h2>SYNOPSIS</h2><p><font size=3><B>xfs_growfs</B> <font size=3>[ <font size=3><B>-D</B> <font size=3>size ] [ <font size=3><B>-d</B> <font size=3>] [ <font size=3><B>-e</B> <font size=3>rtextsize ] [ <font size=3><B>-i</B> <font size=3>] [ <font size=3><B>-L</B> <font size=3>size ]<br>
<span style=" text-indent: 0.5000in;"></span>[ <font size=3><B>-l</B> <font size=3>] [ <font size=3><B>-m</B> <font size=3>maxpct ] [ <font size=3><B>-n</B> <font size=3>] [ <font size=3><B>-R</B> <font size=3>size ] [ <font size=3><B>-r</B> <font size=3>] [ <font size=3><B>-x</B> <font size=3>] mount-point</p>
<a name="DESCRIPTION"></a><h2>DESCRIPTION</h2><p><font size=3><I>xfs_growfs</I> <font size=3>expands an existing XFS filesystem (see <font size=3><I>xfs</I><font size=3>(4)). The <font size=3><I>mount-point</I> <font size=3>argument is the pathname of the directory where the filesystem is mounted. The filesystem must be mounted to be grown (see <font size=3><I>mount</I><font size=3>(1M)). The existing contents of the filesystem are undisturbed, and the added space becomes available for additional file stor- age.</p>
<p><font size=3>The options to <font size=3><I>xfs_growfs</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="10.4615%">
<p><font size=3><B>-d</B><font size=3>, <font size=3><B>-D</B> <font size=3><I>size</p>
</I></td>
<td valign="top" align="left" width="9.5385%">
</td>
<td valign="top" align="left" width="80.0000%">
<p><font size=3>Specifies that the data section of the filesystem should be grown. If the <font size=3><B>-D</B> <font size=3><I>size</I> <font size=3>option is given, the data section is grown to that size, otherwise the data section is grown to the largest size possible. The size is expressed in filesystem blocks.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="10.4615%">
<p><font size=3><B>-e</p>
</B></td>
<td valign="top" align="left" width="9.5385%">
</td>
<td valign="top" align="left" width="80.0000%">
<p><font size=3>Allows the real-time extent size to be specified. In <font size=3><I>mkfs_xfs</I><font size=3>(1M) this is specified with <font size=3><B>-r extsize=</B><font size=3><I>nnnn.</p>
</I></td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="10.4615%">
<p><font size=3><B>-i</p>
</B><p><font size=3><B>-l</B><font size=3>, <font size=3><B>-L</B> <font size=3><I>size</p>
</I></td>
<td valign="top" align="left" width="9.5385%">
</td>
<td valign="top" align="left" width="80.0000%">
<p><font size=3>The new log is an internal log (inside the data section).</p>
<p><font size=3>Specifies that the log section of the filesystem should be grown, shrunk, or moved. If the <font size=3><B>-L</B> <font size=3><I>size</I> <font size=3>option is given, the log section is changed to be that size, if possible. The size is expressed in filesystem blocks. The size of an internal log must be smaller than the size of an allocation group (this value is printed at <font size=3><I>mkfs</I><font size=3>(1M) time). If neither <font size=3><B>-i</B> <font size=3>nor <font size=3><B>-x</B> <font size=3>is given with <font size=3><B>-l</B><font size=3>, the log continues to be internal or external as it was before.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="10.4615%">
<p><font size=3><B>-m</p>
</B></td>
<td valign="top" align="left" width="9.5385%">
</td>
<td valign="top" align="left" width="80.0000%">
<p><font size=3>Specify a new value for the maximum percentage of space in the filesystem that can be allocated as inodes. In <font size=3><I>mkfs_xfs</I> <font size=3>this is specified with <font size=3><B>-i maxpct=</B><font size=3><I>nn.</p>
</I></td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="10.4615%">
<p><font size=3><B>-n</p>
</B></td>
<td valign="top" align="left" width="9.5385%">
</td>
<td valign="top" align="left" width="80.0000%">
<p><font size=3>Specifies that no change to the filesystem is to be made. The filesystem geometry is printed, and argument checking is performed, but no growth occurs.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="10.4615%">
<p><font size=3><B>-r</B><font size=3>, <font size=3><B>-R</B> <font size=3><I>size</p>
</I></td>
<td valign="top" align="left" width="9.5385%">
</td>
<td valign="top" align="left" width="80.0000%">
<p><font size=3>Specifies that the real-time section of the filesystem should be grown. If the <font size=3><B>-R</B> <font size=3><I>size</I> <font size=3>option is given, the real-time section is grown to that size, otherwise the real-time section is grown to the largest size possible. The size is expressed in filesystem blocks. The filesystem does not need to have contained a real-time section before the <font size=3><I>xfs_growfs</I> <font size=3>operation.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left" width="10.4615%">
<p><font size=3><B>-x</p>
</B></td>
<td valign="top" align="left" width="9.5385%">
</td>
<td valign="top" align="left" width="80.0000%">
<p><font size=3>The new log is an external log (in an XLV log subvolume).</p>
</td>
</tr>
</table>
<p><font size=3><I>xfs_growfs</I> <font size=3>is most often used in conjunction with logical volumes (see <font size=3><I>xlv</I><font size=3>(7M) or <font size=3><I>lv</I><font size=3>(7M)). However, it can also be used on a regular disk partition, for example if a partition has been enlarged while retaining the same starting block.</p>
<a name="PRACTICAL USE"></a><h2>PRACTICAL USE</h2><p><font size=3>Filesystems normally occupy all of the space on the device where they reside. In order to grow a filesystem, it is necessary to provide added space for it to occupy. Therefore there must be at least one spare new disk partition available. Adding the space is done through the mechanism of logical volumes. If the filesystem already resides on a logical volume, the volume is simply extended using <font size=3><I>mklv</I><font size=3>(1M) or <font size=3><I>xlv_mgr</I><font size=3>(1M). If the filesystem is currently on a regular partition, it is necessary to create a new logical volume whose first member is the existing partition, with subsequent members being the new partition(s) to be added. Again, <font size=3><I>mklv</I> <font size=3>or <font size=3><I>xlv_mgr</I> <font size=3>is used for this. In either case <font size=3><I>xfs_growfs</I> <font size=3>is run on the mounted filesystem, and the expanded filesystem is then available for use.</p>
<a name="SEE ALSO"></a><h2>SEE ALSO</h2><p><font size=3>mkfs_xfs(1M), mklv(1M), mount(1M), xlv_make(1M), lv(7M), xlv(7M).<br>
</p>
</body>
</html>