<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Transitional//EN">
<HTML>
<HEAD>
  <!--
    *************************************************************************************
    * Copyright (c) 2005 VERITAS Software Corporation. All rights reserved. *

      For third-party license citations, please see the bottom of this file.
    *************************************************************************************
  -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="TEMPLATEBASE" content="DocCD Manual Pages 1.4">
<meta name="LASTUPDATED" content="06/13/05 11:54:57">
<meta name="PRODUCTNAME" content="VERITAS Software Documentation">
<meta name="FILENAME" content="vxtunefs.fm">
     
<title>vxtunefs</title>

</HEAD>

<BODY bgcolor="#FFFFFF" link="#000066" vlink="#0000ff" marginheight="0" topmargin="0">
<basefont=1>

<a name="435201"></a>

<div align="left">
<table border="0" cellspacing="0" cellpadding="0" width="100%">
 <tr>
   <td height="2" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#000000">
   </td>
 </tr>
 <tr>
   <td height="15" width="50%" border="0" cellspacing="0" cellpadding="0" bgcolor="#cccccc">
    <img src="images/vxsymbol.gif" height="20" width="31" border="0" cellspacing="0" cellpadding="0" align="left">
     
     
   </td>
   <td align="right" width="50%" bgcolor="#cccccc">

<!-- Header Breadcrumbs -->
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&lt;&nbsp;<a href="vxrestore_vxfs_manpages37_435936.html" title="Previous - vxrestore">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="vxupgrade_vxfs_manpages39_428773.html" title="Next - vxupgrade">Next</a>
&nbsp;&gt;&nbsp;&nbsp;</font>
   </td>
 </tr>

 <tr>
  <td bgcolor="#CCCCCC" colspan="2" height="15" align="right">
  <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Product:  
<a href="vxfs_manpages_splashpage_docCD_vxfs_manpages1_103036.vxhd" title="File System Manual Pages for Storage Foundation title page ">File System Manual Pages for Storage Foundation</a>
  &nbsp;&nbsp;
  </font>
  </td>
 </tr>
 <tr>
  <td bgcolor="#CCCCCC" colspan="2" height="15" align="right">
  <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Manual:  
<a href="man1m_titlepage_docCD_vxfs_manpages8_73700.vxhd" title="Maintenance Commands (1m) title page ">Maintenance Commands (1m)</a>
  &nbsp;&nbsp;
  </font>
  </td>
 </tr>


</table>
</div>

<div align="left">
 <table border="0" width="100%" bgcolor="#FFFFFF">
  <tr>
   <td width="100%" valign="top" bgcolor="#FFFFFF">

<!-- Start Main Topic Content -->
        <a name="startcontent"></a>
	
<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="430432"></a>vxtunefs</font>
</h2>

        

<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="430462"></a> NAME</font>
</h3>
<p>
<a name="430467"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">vxtunefs - tune a VxFS file system </font>
</p>

<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="430470"></a> SYNOPSIS</font>
</h3>
<br>
<font face="Courier, Courier New, sansserif, sans serif" size="2"><a name="430475"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs </b></font>{<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-p</b></font> | <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-s </b></font>[<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-f </b></font><em>tunefstab</em> | <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-o </b></font><em>parameter=value</em>]} {<em>mount_point</em> | <em>special</em>} ... 
</font>

<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="430505"></a> AVAILABILITY</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430510"></a>VRTSvxfs </font>
</p>


<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="430513"></a> DESCRIPTION</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430518"></a>The <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs </b></font>command sets or prints tunable I/O parameters of mounted file systems. The <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs </b></font>command can set parameters describing the I/O properties of the underlying device, parameters to indicate when to treat an I/O as direct I/O, or parameters to control the extent allocation policy for the specified file system. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430585"></a>With no options specified, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs</b></font> prints the existing VxFS parameters for the specified file systems. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430626"></a>The <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs </b></font>command works on a list of mount points specified on the command line, or all the mounted file systems listed in the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>tunefstab</b></font> file. The default <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>tunefstab</b></font> file is <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>/etc/vx/tunefstab </b></font>. You can change the default using the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-f</b></font> option. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430763"></a>The <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs </b></font>command can be run at any time on a mounted file system, and all parameter changes take immediate effect.  Parameters specified on the command line override parameters listed in the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>tunefstab</b></font> file. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430831"></a>If <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>/etc/vx/tunefstab</b></font> exists, the VxFS-specific <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>mount</b></font> command invokes <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs </b></font>to set device parameters from <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>/etc/vx/tunefstab </b></font>. If the file system is built on a VERITAS Volume Manager (VxVM) volume, the VxFS-specific <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>mount</b></font> command interacts with VxVM to obtain default values for the tunables, so you need to specify tunables for VxVM devices only to change the defaults. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430967"></a>Only a privileged user can run <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs</b></font>. </font>
</p>


<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="430970"></a> NOTES</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="430975"></a>The <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxtunefs </b></font>command works with Storage Checkpoints; however, VxFS tunables apply to an entire file system. Therefore tunables affect not only the primary fileset, but also any Storage Checkpoint filesets within that file system. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431032"></a>The tunable <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>qio_cache_enable </b></font>is not supported on HP-UX. </font>
</p>


<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="431053"></a> CLUSTER FILE SYSTEM ISSUES</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431058"></a>Whether specified by the command line or the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>tunefstab </b></font>file, tunable parameters are propagated to all nodes in the cluster. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431088"></a>CFS requires more memory to manage distributed operations, so you may want to adjust related tunables for a cluster mounted file system. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431109"></a>The <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_seqio_extent_size </b></font>and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>initial_extent_size </b></font>parameters are in-memory values that take effect only when the invoking node is the primary, or later becomes the primary, node in the cluster. </font>
</p>


<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="431166"></a> OPTIONS</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431172"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-f </b></font><em>filename</em></font>
</p>
<p>
<a name="435413"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Use <em>filename</em> instead of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>/etc/vx/tunefstab</b></font> as the file containing tuning parameters. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431215"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-o </b></font><em>parameter=value</em></font>
</p>
<p>
<a name="435436"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Specifies parameters for the file systems listed on the command line. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431238"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-p</b></font></font>
</p>
<p>
<a name="435455"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Prints the tuning parameters for all the file systems specified on the command line. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431260"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>-s</b></font></font>
</p>
<p>
<a name="435478"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Sets the new tuning parameters for the VxFS file systems specified on the command line or in the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>tunefstab</b></font> file. </font>
</p>

<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="431281"></a> VXFS TUNING PARAMETERS AND GUIDELINES</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431286"></a>The values for all the following parameters except <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime</b></font>, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_winterval</b></font>, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream</b></font>, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream</b></font>, and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>qio_cache_enable </b></font>can be specified in bytes, kilobytes, megabytes, gigabytes, terabytes, or sectors (1024 bytes) by appending k, K, m, M, g, G, t, T, s, or S. There is no need for a suffix for the value in bytes. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431379"></a>If the file system is being used with VxVM, it is advisable to let the parameters use the default values based on the volume geometry. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431400"></a>If the file system is being used with a hardware disk array or another volume manager, align the parameters to match the geometry of the logical disk. For disk striping and RAID-5 configurations, set <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_pref_io </b></font>to the stripe unit size or interleave factor and set <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream </b></font>to be the number of columns. For disk striping configurations, set <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_pref_io </b></font>and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream </b></font>to the same values as <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_pref_io </b></font>and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream</b></font>, but for RAID-5 configurations, set <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_pref_io</b></font>, to the full stripe size and set <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream </b></font>to 1. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431610"></a>For an application to do efficient direct I/O or discovered direct I/O, it should issue read requests that are equal to the product of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream </b></font>and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_pref_io</b></font>. In general, any multiple or factor of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream </b></font>multiplied by <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_pref_io </b></font>is a good size for performance. For writing, the same general rule applies to the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_pref_io </b></font>and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream </b></font>parameters. When tuning a file system, the best thing to do is use the tuning parameters under a real workload. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431806"></a>If an application is doing sequential I/O to large files, the application should issue requests larger than the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>discovered_direct_iosz</b></font>. This performs the I/O requests as discovered direct I/O requests which are unbuffered like direct I/O, but which do not require synchronous inode updates when extending the file. If the file is too large to fit in the cache, using unbuffered I/O avoids losing useful data out of the cache and lowers CPU overhead. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="431891"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>discovered_direct_iosz</b></font></font>
</p>
<p>
<a name="435581"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Any file I/O requests larger than the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>discovered_direct_iosz</b></font> are handled as discovered direct I/O. A discovered direct I/O is unbuffered like direct I/O, but it does not require a synchronous commit of the inode when the file is extended or blocks are allocated. For larger I/O requests, the CPU time for copying the data into the buffer cache and the cost of using memory to buffer the I/O becomes more expensive than the cost of doing the disk I/O.  For these I/O requests, using discovered direct I/O is more efficient than regular I/O. The default value of this parameter is 256K. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="432014"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime</b></font></font>
</p>
<p>
<a name="435604"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Specifies the minimum amount of time, in seconds, that the VxFS File Change Log (FCL) keeps records in the log. When the oldest 8K block of FCL records have been kept longer than the value of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime</b></font>, they are purged from the FCL and the extents nearest to the beginning of the FCL file are freed. This process is referred to as &quot;punching a hole.&quot; Holes are punched in the FCL file in 8K chunks. </font>
</p>
<p>
<a name="425194"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">If the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc </b></font>parameter is set, records are purged from the FCL if the amount of space allocated to the FCL exceeds <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc</b></font>, even if the elapsed time the records have been in the log is less than the value of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime</b></font>. If the file system runs out of space before <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime </b></font>is reached, the FCL is deactivated. </font>
</p>
<p>
<a name="425208"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Either or both of the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime </b></font>or <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc </b></font>parameters must be set before the File Change Log can be activated. <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime </b></font>operates only on Version 6 or higher disk layout file systems. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="432311"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc</b></font></font>
</p>
<p>
<a name="435665"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Specifies the maximum amount of space that can be allocated to the VxFS File Change Log. The FCL file is a sparse file that grows as changes occur in the file system. When the space allocated to the FCL file reaches the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc </b></font>value, the oldest FCL records are purged from the FCL and the extents nearest to the beginning of the FCL file are freed. This process is referred to as &quot;punching a hole.&quot; Holes are punched in the FCL file in 8K chunks. If the file system runs out of space before <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc </b></font>is reached, the FCL is deactivated. </font>
</p>
<p>
<a name="425234"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Either or both of the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc </b></font>or <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_keeptime </b></font>parameters must be set before the File Change Log can be activated. <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_maxalloc </b></font>operates only on Version 6 or higher disk layout file systems. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="432529"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_winterval</b></font></font>
</p>
<p>
<a name="435703"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Specifies the time, in seconds, that must elapse before the VxFS File Change Log records a data overwrite, data extending write, or data truncate for a file. The ability to limit the number of repetitive FCL records for continuous writes to the same file is important for file system performance and for applications processing the FCL. <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_winterval </b></font>is best set to an interval less than the shortest interval between reads of the FCL by any application. This way all applications using the FCL can be assured of finding at least one FCL record for any file experiencing continuous data changes. </font>
</p>
<p>
<a name="425261"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_winterval </b></font>is enforced for all files in the file system. Each file maintains its own time stamps, and the elapsed time between FCL records is per file. This elapsed time can be overridden using the VxFS FCL sync public API (see the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxfs_fcl_sync</b></font>(3) manual page). </font>
</p>
<p>
<a name="425271"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fcl_winterval </b></font>operates only on Version 6 or higher disk layout file systems. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="432799"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>hsm_write_prealloc</b></font></font>
</p>
<p>
<a name="435752"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">For a file managed by a hierarchical storage management (HSM) application, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>hsm_write_prealloc </b></font>preallocates disk blocks before data is migrated back into the file system. An HSM application usually migrates the data back through a series of writes to the file, each of which allocates a few blocks. By setting <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>hsm_write_prealloc </b></font>(<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>hsm_write_prealloc=1</b></font>), a sufficient number of disk blocks will be allocated on the first write to the empty file so that no disk block allocation is required for subsequent writes, which improves the write performance during migration. </font>
</p>
<p>
<a name="425293"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">The <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>hsm_write_prealloc </b></font>parameter is implemented outside of the DMAPI specification, and its usage has limitations depending on how the space within an HSM controlled file is managed. It is advisable to use <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>hsm_write_prealloc </b></font>only when recommended by the HSM application controlling the file system. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433044"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>initial_extent_size</b></font></font>
</p>
<p>
<a name="435782"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Changes the default size of the initial extent. </font>
</p>
<p>
<a name="425306"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">VxFS determines, based on the first write to a new file, the size of the first extent to allocate to the file. Typically the first extent is the smallest power of 2 that is larger than the size of the first write. If that power of 2 is less than 8K, the first extent allocated is 8K. After the initial extent, the file system increases the size of subsequent extents (see <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_seqio_extent_size</b></font>) with each allocation. </font>
</p>
<p>
<a name="425313"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Because most applications write to files using a buffer size of 8K or less, the increasing extents start doubling from a small initial extent. <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>initial_extent_size</b></font> changes the default initial extent size to a larger value, so the doubling policy starts from a much larger initial size, and the file system won't allocate a set of small extents at the start of file. </font>
</p>
<p>
<a name="425320"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Use this parameter only on file systems that have a very large average file size. On such file systems, there are fewer extents per file and less fragmentation. </font>
</p>
<p>
<a name="425324"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>initial_extent_size</b></font> is measured in file system blocks. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433229"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>inode_aging_count</b></font></font>
</p>
<p>
<a name="435829"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Specifies the maximum number of inodes to place on an inode aging list. Inode aging is used in conjunction with file system Storage Checkpoints to allow quick restoration of large, recently deleted files. The aging list is maintained in first-in-first-out (fifo) order up to maximum number of inodes specified by <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>inode_aging_count</b></font>. As newer inodes are placed on the list, older inodes are removed to complete their aging process. For best performance, it is advisable to age only a limited number of larger files before completion of the removal process. The default maximum number of inodes to age is 2048. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433368"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>inode_aging_size</b></font></font>
</p>
<p>
<a name="435848"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Specifies the minimum size to qualify a deleted inode for inode aging. Inode aging is used in conjunction with file system Storage Checkpoints to allow quick restoration of large, recently deleted files. For best performance, it is advisable to age only a limited number of larger files before completion of the removal process. Setting the size too low can push larger file inodes out of the aging queue to make room for newly removed smaller file inodes. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433462"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_buf_data_size</b></font></font>
</p>
<p>
<a name="435867"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Determines the maximum buffer size allocated for file data. The two accepted values are 8K bytes and 64K bytes. The larger value can be beneficial for workloads where large reads/writes are performed sequentially. The smaller value is preferable on workloads where the I/O is random or is done in small chunks. The default value is 8K bytes. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433539"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_direct_iosz</b></font></font>
</p>
<p>
<a name="435890"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Maximum size of a direct I/O request issued by the file system.  If there is a larger I/O request, it is broken up into <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_direct_iosz</b></font> chunks.  This parameter defines how much memory an I/O request can lock at once; do not set it to more than 20% of memory. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433597"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_diskq</b></font></font>
</p>
<p>
<a name="435909"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Specifies the maximum disk queue generated by a single file. If the number of dirty buffers in the disk queue exceeds this limit, the file system prevents writing more data to disk until the amount of data decreases. The default value is 1 megabyte. </font>
</p>
<p>
<a name="425382"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Although it does not limit the actual disk queue, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_diskq </b></font>prevents processes that flush data to disk, such as <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fsync</b></font>, from making the system unresponsive. </font>
</p>
<p>
<a name="425390"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">See the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>description for more information on pages and system memory. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433769"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_seqio_extent_size</b></font></font>
</p>
<p>
<a name="435946"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Increases or decreases the maximum size of an extent. When the file system is following its default allocation policy for sequential writes to a file, it allocates an initial extent that is large enough for the first write to the file. When additional extents are allocated, they are progressively larger (the algorithm tries to double the size of the file with each new extent), so each extent can hold several writes worth of data. This reduces the total number of extents in anticipation of continued sequential writes. When there are no more writes to the file, unused space is freed for other files to use. </font>
</p>
<p>
<a name="425406"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">In general, this allocation stops increasing the size of extents at 2048 blocks, which prevents one file from holding too much unused space. </font>
</p>
<p>
<a name="425409"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_seqio_extent_size</b></font> is measured in file system blocks. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="433905"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>qio_cache_enable</b></font></font>
</p>
<p>
<a name="435979"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Enables or disables caching on Quick I/O for Databases files. The default behavior is to disable caching. To enable caching, set <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>qio_cache_enable </b></font>to 1. </font>
</p>
<p>
<a name="425419"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">On systems with large amounts of memory, the database cannot always use all of the memory as a cache. By enabling file system caching as a second level cache, performance can improve. </font>
</p>
<p>
<a name="425424"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">If the database is performing sequential scans of tables, the scans can run faster by enabling file system caching so the file system performs aggressive read aheads on the files. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434041"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_ahead</b></font></font>
</p>
<p>
<a name="436008"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">In the absence of a specific caching advisory, the default for all VxFS read operations is to perform sequential read ahead. The enhanced read ahead functionality implements an algorithm that allows read aheads to detect more elaborate patterns (such as increasing or decreasing read offsets, or multithreaded file accesses) in addition to simple sequential reads. You can specify the following values for <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_ahead</b></font>: </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434144"></a>0</font>
</p>
<p>
<a name="436023"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Disables read ahead functionality </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434157"></a>1</font>
</p>
<p>
<a name="436038"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Retains traditional sequential read ahead behavior </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434170"></a>2</font>
</p>
<p>
<a name="436053"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Enables enhanced read ahead for all reads </font>
</p>
<p>
<a name="425452"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">By default, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_ahead </b></font>is set to 1, that is, VxFS detects only sequential patterns. </font>
</p>
<p>
<a name="425458"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_ahead </b></font>detects patterns on a per-thread basis, up to a maximum of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vx_era_nthreads</b></font>. The default number of threads is 5, however, you can change the default value by setting the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vx_era_nthreads </b></font>parameter in the system configuration file, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>/etc/system</b></font>. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434341"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream</b></font></font>
</p>
<p>
<a name="436108"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">The number of parallel read requests of size <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_pref_io</b></font> to have outstanding at one time.  The file system uses the product of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream</b></font> and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_pref_io</b></font> to determine its read ahead size.  The default value for <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream</b></font> is 1. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434399"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_pref_io</b></font></font>
</p>
<p>
<a name="436131"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">The preferred read request size.  The file system uses this in conjunction with the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>read_nstream </b></font>value to determine how much data to read ahead.  The default value is 64K. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434439"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream</b></font></font>
</p>
<p>
<a name="436166"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">The number of parallel write requests of size <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_pref_io</b></font> to have outstanding at one time.  The file system uses the product of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream</b></font> and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_pref_io</b></font> to determine when to do flush behind on writes.  The default value for <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream</b></font> is 1. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434497"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_pref_io</b></font></font>
</p>
<p>
<a name="436189"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">The preferred write request size. The file system uses this in conjunction with the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_nstream </b></font>value to determine how to do flush behind on writes. The default value is 64K. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="434546"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle</b></font></font>
</p>
<p>
<a name="436216"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">When data is written to a file through buffered writes, the file system updates only the in-memory image of the file, creating what are referred to as <em>dirty buffers</em>. Dirty buffers are <em>cleaned </em>when the the file system later writes the data in these buffers to disk. (Note that data can be lost if the system crashes before dirty buffers are written to disk.) </font>
</p>
<p>
<a name="425512"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">Newer model computer systems typically have more memory. The more physical memory a system has, the more dirty buffers the file system can generate before having to write the buffers to disk to free up memory. So more dirty buffers can potentially lead to longer return times for operations that write dirty buffers to disk such as <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>sync </b></font>and <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fsync</b></font>. If your system has a combination of a slow storage device and a large amount of memory, the sync operations may take long enough to complete that it gives the appearance of a hung system. </font>
</p>
<p>
<a name="425527"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">If your system is exhibiting this behavior, you can change the value of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle</b></font>. <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>lets you lower the number of dirty buffers per file that the file system will generate before writing them to disk. After the number of dirty buffers for a file reaches the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>threshold, the file system starts flushing buffers to disk even if free memory is still available. Depending on the speed of the storage device, user write performance may suffer, but the number of dirty buffers is limited, so sync operations will complete much faster. </font>
</p>
<p>
<a name="425543"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">The default value of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>is zero. The default value places no limit on the number of dirty buffers per file. This typically generates a large number of dirty buffers, but maintains fast writes. If <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>is non-zero, VxFS limits the number of dirty buffers per file to <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>buffers In some cases, <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>may delay write requests. For example, lowering the value of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle </b></font>may increase the file disk queue to the <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>max_diskq </b></font>value, delaying user writes until the disk queue decreases. So unless the system has a combination of large physical memory and slow storage devices, it is advisable not to change the value of <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>write_throttle</b></font>. </font>
</p>

<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="435183"></a> FILES</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="435189"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>/etc/vx/tunefstab</b></font></font>
</p>
<p>
<a name="436292"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2">VxFS tuning parameters table. </font>
</p>

<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="435201"></a> SEE ALSO</font>
</h3>
<blockquote>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="435206"></a><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>mount</b></font>(1), <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>mkfs</b></font>(1M), <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>sync</b></font>(2), <a href="vxfs_fcl_sync_vxfs_manpages77_427385.html#426729"><font color="#0000ff"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxfs_fcl_sync </b></font></font></a>(3), <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>fsync</b></font>(3C), <a href="tunefstab_vxfs_manpages96_427503.html#426792"><font color="#0000ff"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>tunefstab </b></font></font></a>(4), <a href="vxfsio_vxfs_manpages98_436668.html#430964"><font color="#0000ff"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><b>vxfsio </b></font></font></a>(7) </font>
</blockquote>
<blockquote>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="435288"></a><em>VERITAS File System Administrator's Guide</em>, <br><em>VERITAS Volume Manager Administrator's Guide </em></font>
</blockquote>

<!-- End Main Topic Content -->

   </td>
  </tr>
 </table>
</div>

<div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
 <tr>
  <td height="18" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#FFFFFF">
  </td>
 </tr>
  <td align="left"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&nbsp;&#94;&nbsp;<a href="vxtunefs_vxfs_manpages38_435201.html" title="vxtunefs">Return to Top</a></font>

  </td>
  <td align="right"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&lt;&nbsp;<a href="vxrestore_vxfs_manpages37_435936.html" title="Previous - vxrestore">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="vxupgrade_vxfs_manpages39_428773.html" title="Next - vxupgrade">Next</a>
&nbsp;&gt;&nbsp;&nbsp;</font>
  </td>
 <tr>
   <td height="9" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#FFFFFF">
   </td>
 </tr>

<!-- Footer Breadcrumbs -->
<tr>
<td bgcolor="#FFFFFF" colspan="2" height="15" align="right">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Product:  
<a href="vxfs_manpages_splashpage_docCD_vxfs_manpages1_103036.vxhd" title="File System Manual Pages for Storage Foundation title page ">File System Manual Pages for Storage Foundation</a>&nbsp;&nbsp;</font></td>
</tr>

<tr>
<td bgcolor="#FFFFFF" colspan="2" height="15" align="right">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Manual:  
<a href="man1m_titlepage_docCD_vxfs_manpages8_73700.vxhd" title="Maintenance Commands (1m) title page ">Maintenance Commands (1m)</a>&nbsp;&nbsp;</font></td>
</tr>


 <tr>
  <td colspan="2" align="left"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" color="#000000" align="right" size="-2">
<em>VERITAS Software Corporation
</em></font><br>

<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">www.veritas.com</font><br>
  </td>
 </tr>
</table>
</div>

</BODY>
  <!--
    *************************************************************************************
    * Copyright (c) 2005 VERITAS Software Corporation. All rights reserved. *

    VERITAS, VERITAS SOFTWARE, the VERITAS Logo, and VERITAS Software Documentation 
    are trademarks or registered trademarks of VERITAS Software Corporation 
    or its affiliates in the U.S. and other countries. Other names may be 
    trademarks of their respective owners. 

    Apache Jakarta Lucene:
    Apache Software License
    Version 1.1

    Copyright (c) 2000 The Apache Software Foundation. All rights reserved.

    Redistribution and use in source and binary forms, with or without modification, 
    are permitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice, this 
    list of conditions and the following disclaimer.

    2. Redistributions in binary form must reproduce the above copyright notice, this 
    list of conditions and the following disclaimer in the documentation and/or other 
    materials provided with the distribution.

    3. The end-user documentation included with the redistribution, if any, must include 
    the following acknowledgment: "This product includes software developed by the Apache 
    Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may 
    appear in the software itself, if and wherever such third-party acknowledgments 
    normally appear.

    4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or 
    promote products derived from this software without prior written permission. For 
    written permission, please contact apache@apache.org.

    5. Products derived from this software may not be called "Apache", nor may "Apache" 
    appear in their name, without prior written permission of the Apache Software Foundation.

    THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, 
    BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A 
    PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 
    OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, 
    OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 
    OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND 
    ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
    NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 
    ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    This software consists of voluntary contributions made by many individuals on behalf 
    of the Apache Software Foundation. For more information on the Apache Software Foundation, 
    please see <http://www.apache.org/>. Portions of this software are based upon public domain 
    software originally written at the National Center for Supercomputing Applications, University 
    of Illinois, Urbana-Champaign.
    
    This product includes WebWindow Software developed by Horst Heistermann.
    *************************************************************************************
  -->
</HTML>
