<!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="vx_vxhelp_2005c">
<meta name="LASTUPDATED" content="06/13/05 10:02:06">
<meta name="PRODUCTNAME" content="VERITAS Software Documentation">
<meta name="FILENAME" content="02.performance.fm">
     
<title>Choosing mount Command Options</title>

</HEAD>

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

<a name="198326"></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="02_performance_vxfs30_119883.html" title="Previous - Choosing mkfs Command Options">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="02_performance_vxfs32_120095.html" title="Next - Kernel Tunables">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_splashpage_docCD_vxfs1_103036.vxhd" title="File System Guides title page ">File System Guides</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="vxfs_admin_titlepage_docCD_vxfs2_73700.vxhd" title="File System 4.1 Administrator's Guide title page ">File System 4.1 Administrator's Guide</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>
	
<h1><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="+1" color="#000000"><a name="198326"></a> Choosing mount Command Options</font>
</h1>
         
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119913"></a>In addition to the standard mount mode (<font face="Courier New, Courier, sansserif, sans serif" size="2">delaylog</font> mode), VxFS provides <font face="Courier New, Courier, sansserif, sans serif" size="2">blkclear</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">log</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">tmplog</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">nodatainlog</font> modes of operation. Caching behavior can be altered with the <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache</font> option, and the behavior of <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">D_SYNC</font> (see the <font face="Courier New, Courier, sansserif, sans serif" size="2">fcntl</font>(2) manual page) writes can be altered with the <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync</font> option.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119920"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">delaylog</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">tmplog</font> modes can significantly improve performance. The improvement over <font face="Courier New, Courier, sansserif, sans serif" size="2">log</font> mode is typically about 15 to 20 percent with <font face="Courier New, Courier, sansserif, sans serif" size="2">delaylog</font>; with <font face="Courier New, Courier, sansserif, sans serif" size="2">tmplog</font>, the improvement is even higher. Performance improvement varies, depending on the operations being performed and the workload. Read/write intensive loads should show less improvement, while file system structure intensive loads (such as <font face="Courier New, Courier, sansserif, sans serif" size="2">mkdir</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">create</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">rename</font>) may show over 100 percent improvement. The best way to select a mode is to test representative system loads against the logging modes and compare the performance results.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119921"></a>Most of the modes can be used in combination. For example, a desktop machine might use both the <font face="Courier New, Courier, sansserif, sans serif" size="2">blkclear</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=closesync</font> modes.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119922"></a>Additional information on <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> options can be found in the <font face="Courier New, Courier, sansserif, sans serif" size="2">mount_vxfs</font>(1M) manual page.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="172135"></a>In the following descriptions, the term &quot;effects of system calls&quot; refers to changes to file system data and metadata caused by the system call, excluding changes to st_atime (see the <font face="Courier New, Courier, sansserif, sans serif" size="2">stat</font>(2) manual page).</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="119926"></a>log</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="172502"></a>In <font face="Courier New, Courier, sansserif, sans serif" size="2">log</font> mode, all system calls other than <font face="Courier New, Courier, sansserif, sans serif" size="2">write</font>(2), <font face="Courier New, Courier, sansserif, sans serif" size="2">writev</font>(2), and <font face="Courier New, Courier, sansserif, sans serif" size="2">pwrite</font>(2) are guaranteed to be persistent once the system call returns to the application.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="172858"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">rename</font>(2) system call flushes the source file to disk to guarantee the persistence of  the file data before renaming it. In both modes, the rename is also guaranteed to be persistent when the system call returns. This benefits shell scripts and programs that try to update a file atomically by writing the new file contents to a temporary file and then  renaming it on top of the target file.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="119931"></a>delaylog</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119932"></a>The default logging mode is <font face="Courier New, Courier, sansserif, sans serif" size="2">delaylog</font>. In delaylog mode, the effects of most system calls other than <font face="Courier New, Courier, sansserif, sans serif" size="2">write</font>(2), <font face="Courier New, Courier, sansserif, sans serif" size="2">writev</font>(2), and <font face="Courier New, Courier, sansserif, sans serif" size="2">pwrite</font>(2) are guaranteed to be persistent approximately 3 seconds after the system call returns to the  application. Contrast this with the behavior of most other file systems in which most system calls are not persistent until approximately 30 seconds or more after the call has returned. Fast file system recovery works with this mode.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="173102"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">rename</font>(2) system call flushes the source file to disk to guarantee the persistence of  the file data before renaming it. In both modes, the rename is also guaranteed to be persistent when the system call returns. This benefits shell scripts and programs that try to update a file atomically by writing the new file contents to a temporary file and then  renaming it on top of the target file.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="153081"></a>tmplog</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="172623"></a>In tmplog mode, the effects of system calls have persistence guarantees that are similar to those in delaylog mode. In addition, enhanced flushing of delayed extending writes is disabled, which results in better performance but increases the chances of data being lost or unitialized data appearing in a file that was being actively written at the time of a system failure. This mode is only recommended for temporary file systems. Fast file system recovery works with this mode.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="173641"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">In all logging modes, VxFS is fully POSIX compliant. The effects of the <font face="Courier New, Courier, sansserif, sans serif" size="2">fsync</font>(2) and <font face="Courier New, Courier, sansserif, sans serif" size="2">fdatasync</font>(2) system calls are guaranteed to be persistent once the calls return. The persistence guarantees for data or metadata modified by <font face="Courier New, Courier, sansserif, sans serif" size="2">write</font>(2), <font face="Courier New, Courier, sansserif, sans serif" size="2">writev</font>(2), or <font face="Courier New, Courier, sansserif, sans serif" size="2">pwrite</font>(2) are not affected by the logging mount options. The effects of these system calls are guaranteed to be persistent only if the <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">O_DSYNC</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_DSYNC</font>, or <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_DIRECT</font> flag, as modified by the <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=&nbsp;</font><font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> option, has been specified for the file descriptor.<br><br>The behavior of NFS servers on a VxFS file system is unaffected by the log and tmplog mount options, but not delaylog. In all cases except with delaylog, VxFS complies with the persistency requirements of the NFS v2 and NFS v3 standard.<br><br>Unless a UNIX application has been developed specifically for the VxFS file system in <font face="Courier New, Courier, sansserif, sans serif" size="2">log</font> mode, it will expect the persistence guarantees offered by most other file systems and will experience improved robustness when used with a VxFS file system mounted in <font face="Courier New, Courier, sansserif, sans serif" size="2">delaylog</font> mode. Applications that expect better persistence guarantees than that offered by most other file systems can benefit from the <font face="Courier New, Courier, sansserif, sans serif" size="2">log</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">closesync</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> options. However, most commercially available applications will work well with the default VxFS <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> options, including the <font face="Courier New, Courier, sansserif, sans serif" size="2">delaylog</font> mode.
</font>
<hr noshade size="2" width="100%" color="#000000">



<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="153146"></a>logiosize</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="133573"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">logiosize</font>=<font face="Courier New, Courier, sansserif, sans serif" size="2"><em>size</em></font> option is provided to enhance the performance of storage devices that employ a <em>read-modify-write</em> feature. If you specify <font face="Courier New, Courier, sansserif, sans serif" size="2">logiosize</font> when you mount a file system, VxFS writes the intent log in at least <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>size</em></font> bytes to obtain the maximum performance from such devices. The values for <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>size</em></font> can be 1024, 2048, or 4096.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="133579"></a>nodatainlog</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119946"></a>Use the <font face="Courier New, Courier, sansserif, sans serif" size="2">nodatainlog</font> mode on systems with disks that do not support bad block revectoring. Usually, a VxFS file system uses the intent log for synchronous writes. The inode update and the data are both logged in the transaction, so a synchronous write only requires one disk write instead of two. When the synchronous write returns to the application, the file system has told the application that the data is already written. If a disk error causes the metadata update to fail, then the file must be marked bad and the entire file is lost.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119949"></a>If a disk supports bad block revectoring, then a failure on the data update is unlikely, so logging synchronous writes should be allowed. If the disk does not support bad block revectoring, then a failure is more likely, so the <font face="Courier New, Courier, sansserif, sans serif" size="2">nodatainlog</font> mode should be used.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119950"></a>A <font face="Courier New, Courier, sansserif, sans serif" size="2">nodatainlog</font> mode file system is approximately 50 percent slower than a standard mode VxFS file system for synchronous writes. Other operations are not affected. </font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="119953"></a>blkclear</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119954"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">blkclear</font> mode is used in increased data security environments. The <font face="Courier New, Courier, sansserif, sans serif" size="2">blkclear</font> mode guarantees that uninitialized storage never appears in files. The increased integrity is provided by clearing extents on disk when they are allocated within a file. Extending writes are not affected by this mode. A <font face="Courier New, Courier, sansserif, sans serif" size="2">blkclear</font> mode file system is approximately 10 percent slower than a standard mode VxFS file system, depending on the workload.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="119959"></a>mincache</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119960"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache</font> mode has five suboptions: </font>
</p>

<p>
<ul type="disc"><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119961"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=closesync</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119962"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=direct</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119963"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=dsync</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119964"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=unbuffered</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119965"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=tmpcache</font></font>
</li>
</ul>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119966"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=closesync</font> mode is useful in desktop environments where users are likely to shut off the power on the machine without halting it first. In this mode, any changes to the file are flushed to disk when the file is closed.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119968"></a>To improve performance, most file systems do not synchronously update data and inode changes to disk. If the system crashes, files that have been updated within the past minute are in danger of losing data. With the <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=closesync</font> mode, if the system crashes or is switched off, only files that are currently open can lose data. A <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=closesync</font> mode file system should be approximately 15 percent slower than a standard mode VxFS file system, depending on the workload.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119969"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=direct</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=unbuffered</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=dsync</font> modes are used in environments where applications are experiencing reliability problems caused by the kernel buffering of I/O and delayed flushing of non-synchronous I/O. The <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=direct</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=unbuffered</font> modes guarantee that all non-synchronous I/O requests to files will be handled as if the <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_DIRECT</font> or <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_UNBUFFERED</font> caching advisories had been specified. The <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=dsync</font> mode guarantees that all non-synchronous I/O requests to files will be handled as if the <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_DSYNC</font> caching advisory had been specified. Refer to the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxfsio</font>(7) manual page for explanations of <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_DIRECT</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_UNBUFFERED</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_DSYNC</font>, as well as for the requirements for direct I/O. The <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=direct</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=unbuffered</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=dsync</font> modes also flush file data on <font face="Courier New, Courier, sansserif, sans serif" size="2">close</font> as <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=closesync</font> does.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119973"></a>Because the <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=direct</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=unbuffered</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=dsync</font> modes change non-synchronous I/O to synchronous I/O, there can be a substantial degradation in throughput for small to medium size files for most applications. Since the <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_DIRECT</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">VX_UNBUFFERED</font> advisories do not allow any caching of data, applications that would normally benefit from caching for reads will usually experience less degradation with the <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=dsync</font> mode. <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=direct</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=unbuffered</font> require significantly less CPU time than buffered I/O.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119974"></a>If performance is more important than data integrity, you can use the <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=tmpcache</font> mode. The <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=tmpcache</font> mode disables special delayed extending write handling, trading off less integrity for better performance. Unlike the other <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache</font> modes, <font face="Courier New, Courier, sansserif, sans serif" size="2">tmpcache</font> does not flush the file to disk when it is closed. When the <font face="Courier New, Courier, sansserif, sans serif" size="2">mincache=tmpcache</font> option is used, bad data can appear in a file that was being extended when a crash occurred.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="119978"></a>convosync</font>
</h2>
 
<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="119979"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">Use of the <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=dsync</font> option violates POSIX guarantees for synchronous I/O.
</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119980"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync</font> (convert osync) mode has five suboptions:</font>
</p>

<p>
<ul type="disc"><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119981"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=closesync</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119982"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=delay</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119983"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=direct</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119984"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=dsync</font></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119985"></a><font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=unbuffered</font></font>
</li>
</ul>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119986"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=closesync</font> mode converts synchronous and data synchronous writes to non-synchronous writes and flushes the changes to the file to disk when the file is closed.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119987"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=delay</font> mode causes synchronous and data synchronous writes to be delayed rather than to take effect immediately. No special action is performed when closing a file. This option effectively cancels any data integrity guarantees normally provided by opening a file with <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC</font>. See the <font face="Courier New, Courier, sansserif, sans serif" size="2">open</font>(2), <font face="Courier New, Courier, sansserif, sans serif" size="2">fcntl</font>(2), and <font face="Courier New, Courier, sansserif, sans serif" size="2">vxfsio</font>(7) manual pages for more information on <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC</font>.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/caution.gif" alt="Caution " height="16" width="16">&nbsp;<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="119988"></a><b>Caution  &nbsp;&nbsp;</b></font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000"> Be very careful when using the <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=closesync</font> or <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=delay</font> mode because they actually change synchronous I/O into non-synchronous I/O. This may cause applications that use synchronous I/O for data reliability to fail if the system crashes and synchronously written data is lost.</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119989"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=direct</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=unbuffered</font> mode convert synchronous and data synchronous reads and writes to direct reads and writes.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119990"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=dsync</font> mode converts synchronous writes to data synchronous writes.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119991"></a>As with <font face="Courier New, Courier, sansserif, sans serif" size="2">closesync</font>, the <font face="Courier New, Courier, sansserif, sans serif" size="2">direct</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">unbuffered</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">dsync</font> modes flush changes to the file to disk when it is closed. These modes can be used to speed up applications that use synchronous I/O. Many applications that are concerned with data integrity specify the <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC&nbsp;fcntl</font> in order to write the file data synchronously. However, this has the undesirable side effect of updating inode times and therefore slowing down performance. The <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=dsync</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=unbuffered</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=direct</font> modes alleviate this problem by allowing applications to take advantage of synchronous writes without modifying inode times as well.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/caution.gif" alt="Caution " height="16" width="16">&nbsp;<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="140347"></a><b>Caution  &nbsp;&nbsp;</b></font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000"> Before using <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=dsync</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=unbuffered</font>, or <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=direct</font>, make sure that all applications that use the file system do not require synchronous inode time updates for <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC</font> writes.</font>
<hr noshade size="2" width="100%" color="#000000">



<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="140350"></a>ioerror</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119997"></a>Sets the policy for handling I/O errors on a mounted file system. I/O errors can occur while reading or writing file data, or while reading or writing metadata. The file system can respond to these I/O errors either by halting or by gradually degrading. The ioerror option provides four policies that determine how the file system responds to the various errors. All four policies limit data corruption, either by stopping the file system or by marking a corrupted inode as bad. The four policies are <font face="Courier New, Courier, sansserif, sans serif" size="2">disable</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">nodisable</font>, <font face="Courier New, Courier, sansserif, sans serif" size="2">wdisable</font>, and <font face="Courier New, Courier, sansserif, sans serif" size="2">mwdisable</font>.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119998"></a>If <font face="Courier New, Courier, sansserif, sans serif" size="2">disable</font> is selected, VxFS disables the file system after detecting any I/O error. You must then unmount the file system and correct the condition causing the I/O error. After the problem is repaired, run <font face="Courier New, Courier, sansserif, sans serif" size="2">fsck</font> and mount the file system again. In most cases, replaying <font face="Courier New, Courier, sansserif, sans serif" size="2">fsck</font> is sufficient to repair the file system. A full <font face="Courier New, Courier, sansserif, sans serif" size="2">fsck</font> is required only in cases of structural damage to the file system's metadata. Select <font face="Courier New, Courier, sansserif, sans serif" size="2">disable</font> in environments where the underlying storage is redundant, such as RAID-5 or mirrored disks. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="119999"></a>If <font face="Courier New, Courier, sansserif, sans serif" size="2">nodisable</font> is selected, when VxFS detects an I/O error, it sets the appropriate error flags to contain the error, but continues running. Note that the &quot;degraded&quot; condition indicates possible data or metadata corruption, not the overall performance of the file system.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120000"></a>For file data read and write errors, VxFS sets the VX_DATAIOERR flag in the super-block. For metadata read errors, VxFS sets the VX_FULLFSCK flag in the super-block. For metadata write errors, VxFS sets the VX_FULLFSCK and VX_METAIOERR flags in the super-block and may mark associated metadata as bad on disk. VxFS then prints the appropriate error messages to the console (see <a href="B_err_msgs_vxfs104_80880.html#80880">Kernel Messages</a> for information on actions to take for specific errors).</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120004"></a>You should stop the file system as soon as possible and repair the condition causing the I/O error. After the problem is repaired, run <font face="Courier New, Courier, sansserif, sans serif" size="2">fsck</font> and mount the file system again. Select <font face="Courier New, Courier, sansserif, sans serif" size="2">nodisable</font> if you want to implement the policy that most closely resembles the error handling policy of the previous VxFS release.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="142718"></a>If <font face="Courier New, Courier, sansserif, sans serif" size="2">wdisable</font> (write disable) or <font face="Courier New, Courier, sansserif, sans serif" size="2">mwdisable</font> (metadata-write disable) is selected, the file system is disabled or degraded, depending on the type of error encountered. Select <font face="Courier New, Courier, sansserif, sans serif" size="2">wdisable</font> or <font face="Courier New, Courier, sansserif, sans serif" size="2">mwdisable</font> for environments where read errors are more likely to persist than write errors, such as when using non-redundant storage. <font face="Courier New, Courier, sansserif, sans serif" size="2">mwdisable</font> is the default ioerror mount option for local mounts. See the <font face="Courier New, Courier, sansserif, sans serif" size="2">mount_vxfs</font>(1M) manual page for more information.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="142721"></a>largefiles | nolargefiles</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="251062"></a>VxFS supports files larger than 2 gigabytes. The maximum file size that can be created is 2 terabytes.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="155724"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">Applications and utilities such as backup may experience problems if they are not aware of large files. In such a case, create your file system without large file capability.
</font>
<hr noshade size="2" width="100%" color="#000000">



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="120013"></a>Creating a File System with Large Files</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120014"></a>You can create a file system with large file capability by entering the following command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251098"></a>&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>mkfs&nbsp;-F&nbsp;vxfs&nbsp;-o&nbsp;largefiles</b></font>&nbsp;<em>special_device&nbsp;size</em>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="137429"></a>Specifying <font face="Courier New, Courier, sansserif, sans serif" size="2">largefiles</font> sets the <font face="Courier New, Courier, sansserif, sans serif" size="2">largefiles</font> flag, which allows the file system to hold files that are two terabytes or larger in size. The default option is <font face="Courier New, Courier, sansserif, sans serif" size="2">largefiles</font>. Conversely, the <font face="Courier New, Courier, sansserif, sans serif" size="2">nolargefiles</font> option clears the flag and prevents large files from being created:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251165"></a>&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>mkfs&nbsp;-F&nbsp;vxfs&nbsp;-o&nbsp;nolargefiles</b></font>&nbsp;<em>special_device&nbsp;size</em>
</font>
<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="120024"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">The <font face="Courier New, Courier, sansserif, sans serif" size="2">largefiles</font> flag is persistent and stored on disk. 
</font>
<hr noshade size="2" width="100%" color="#000000">



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="120035"></a>Mounting a File System with Large Files</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120036"></a>If a mount succeeds and <font face="Courier New, Courier, sansserif, sans serif" size="2">nolargefiles</font> is specified, the file system cannot contain or create any large files. If a mount succeeds and <font face="Courier New, Courier, sansserif, sans serif" size="2">largefiles</font> is specified, the file system may contain and create large files. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120038"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> command fails if the specified <font face="Courier New, Courier, sansserif, sans serif" size="2">largefiles|nolargefiles</font> option does not match the on-disk flag. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120039"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> command defaults to match the current setting of the on-disk flag if specified without the <font face="Courier New, Courier, sansserif, sans serif" size="2">largefiles</font> or <font face="Courier New, Courier, sansserif, sans serif" size="2">nolargefiles</font> option, so it's best not to specify either option. After a file system is mounted, you can use the <font face="Courier New, Courier, sansserif, sans serif" size="2">fsadm</font> utility to change the large files option. </font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="120040"></a>Managing a File System with Large Files</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120041"></a>You can determine the current status of the largefiles flag using the <font face="Courier New, Courier, sansserif, sans serif" size="2">fsadm </font> or <font face="Courier New, Courier, sansserif, sans serif" size="2">mkfs</font> command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251238"></a>&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>mkfs&nbsp;-F&nbsp;vxfs&nbsp;-m&nbsp;</b></font><em>special_device</em>
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251239"></a>&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>fsadm&nbsp;-F&nbsp;vxfs&nbsp;</b></font><em>mount_point&nbsp;|&nbsp;special_device</em>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120049"></a>You can switch capabilities on a mounted file system using the <font face="Courier New, Courier, sansserif, sans serif" size="2">fsadm</font> command:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251279"></a>&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>fsadm&nbsp;-F&nbsp;vxfs&nbsp;-o&nbsp;</b></font>[<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>no</b></font>]<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>largefiles</b></font>&nbsp;<em>mount_point</em>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120054"></a>You can also switch capabilities on an unmounted file system:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251315"></a>&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>fsadm&nbsp;-F&nbsp;vxfs&nbsp;-o&nbsp;</b></font>[<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>no</b></font>]<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>largefiles</b></font>&nbsp;<em>special_device</em>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120059"></a>You cannot change a file system to <font face="Courier New, Courier, sansserif, sans serif" size="2">nolargefiles</font> if it holds large files.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120063"></a>See&nbsp;the <font face="Courier New, Courier, sansserif, sans serif" size="2">mount_vxfs</font>(1M), <font face="Courier New, Courier, sansserif, sans serif" size="2">fsadm_vxfs</font>(1M), and <font face="Courier New, Courier, sansserif, sans serif" size="2">mkfs_vxfs</font>(1M) manual pages.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="120067"></a>Combining mount Command Options </font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120069"></a>Although <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> options can be combined arbitrarily, some combinations do not make sense. The following examples provide some common and reasonable <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> option combinations.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="120070"></a>Example 1 - Desktop File System</font>
</h3>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251370"></a><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;</b></font>#<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;mount&nbsp;-F&nbsp;vxfs&nbsp;-o&nbsp;log,mincache=closesync&nbsp;/dev/dsk/c1t3d0&nbsp;/mnt</b></font>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120076"></a>This guarantees that when a file is closed, its data is synchronized to disk and cannot be lost. Thus, once an application is exited and its files are closed, no data will be lost even if the system is immediately turned off.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="120077"></a>Example 2 - Temporary File System or Restoring from Backup</font>
</h3>
<a name="251408"></a><br><font face="Courier New, Courier, sansserif, sans serif" size="2"><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>	</b></font># <font face="Courier New, Courier, sansserif, sans serif" size="2"><b>mount -F vxfs -o tmplog,convosync=delay,mincache=tmpcache </b></font>\<br><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>		/dev/dsk/c1t3d0 /mnt</b></font></font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120084"></a>This combination might be used for a temporary file system where performance is more important than absolute data integrity. Any <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC</font> writes are performed as delayed writes and delayed extending writes are not handled specially (which could result in a file that contains garbage if the system crashes at the wrong time). Any file written 30 seconds or so before a crash may contain garbage or be missing if this <font face="Courier New, Courier, sansserif, sans serif" size="2">mount</font> combination is in effect. However, such a file system will do significantly less disk writes than a log file system, and should have significantly better performance, depending on the application.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="120085"></a>Example 3 - Data Synchronous Writes</font>
</h3>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="251447"></a><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;</b></font>#<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;mount&nbsp;-F&nbsp;vxfs&nbsp;-o&nbsp;log,convosync=dsync&nbsp;/dev/dsk/c1t3d0&nbsp;/mnt</b></font>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="120091"></a>This combination would be used to improve the performance of applications that perform <font face="Courier New, Courier, sansserif, sans serif" size="2">O_SYNC</font> writes, but only require data synchronous write semantics. Their performance can be significantly improved if the file system is mounted using <font face="Courier New, Courier, sansserif, sans serif" size="2">convosync=dsync</font> without any loss of data integrity. </font>
</p>


<!-- 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="02_performance_vxfs31_198326.html" title="Choosing mount Command Options">Return to Top</a></font>

  </td>
  <td align="right"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&lt;&nbsp;<a href="02_performance_vxfs30_119883.html" title="Previous - Choosing mkfs Command Options">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="02_performance_vxfs32_120095.html" title="Next - Kernel Tunables">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_splashpage_docCD_vxfs1_103036.vxhd" title="File System Guides title page ">File System Guides</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="vxfs_admin_titlepage_docCD_vxfs2_73700.vxhd" title="File System 4.1 Administrator's Guide title page ">File System 4.1 Administrator's Guide</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>
