========================================================================== The checksum's (found through sum -r) of the files that you have received (other than this README) are as follows: 02515 11 patchSG0003270.idb 49734 2420 patchSG0003270.onc3_eoe_sw 50748 19 patchSG0003270.onc3_eoe_man 08987 6 patchSG0003270 ========================================================================== - 1 - 1. Patch_SG0003270_Release_Note This release note describes patch SG0003270 to IRIX 6.2. 1.1 Supported_Hardware_Platforms This patch contains bug fixes for all platforms. 1.2 Supported_Software_Platforms This patch contains bug fixes for ONC3 (version 1232792120) on a system running IRIX 6.2. The software cannot be installed on other configurations. This patch replaces patches SG0001230, SG0001310, SG0001435, SG0001473, SG0001577, SG0001692, SG0001893, SG0002150, SG0002431 and SG0003045. It also requires Patch SG0001499 or its successor. 1.3 Bugs_Fixed_by_Patch_SG0003270 This patch contains fixes for the following bugs in IRIX 6.2. Bug numbers from Silicon Graphics bug tracking system are included for reference. o Excessive zone memory allocation when using cachefs. (Bug #586219) o CacheFS panics in fscache_sync. (Bug #525703) o Processes accessing CacheFS files will sometimes hang for long periods of time. (Bug #517771) o Cachefs replacement is too slow due to excessive overhead. (Bug #512140) o Hard links are not properly cached. (Bug #511130) o CacheFS hangs when moving a directory to itself. (Bug #505199) o Writes with a file lock held can cause a loss of data. (Bug #505335) o CacheFS can hang when creating a file. (Bug #503478) o The mv(1) command sometimes fails on cachefs file systems. (Bug #496419) - 2 - o With patch SG0001893 installed, CacheFS will sometimes panic when a file or directory is being removed. (Bug #495034) o Cachefs sometimes hangs. (Bug #495034) o The cachefs replacement daemon sometimes exits unexpectedly. (Bug #495034) o It can appear that disconnected operation does not work. Also, there is a performance problem with file lookup. (Bug #489877) o Sometimes ".." disappears. (Bug #500863) o The CacheFS replacement daemon (cachefs_replacement) performs very poorly. (Bug #345665) o The default attribute timeouts used by CacheFS are too long. This can result in certain types of file corruption due to stale attributes being used. (Bug #471294) o CacheFS attempts updates for uncached directories. (Bugs #467109 and 468008) o CacheFS attempts invalidation for uncached files. (Bugs #467110 and 468008) o CacheFS does not destroy one of its synchronization variables. (Bug #469487) o CacheFS fails to remove stale front directories. (Bug #436525) o CacheFS will deadlock when a stale front directory is found during mkdir. (Bug #437118) o CacheFS causes the vnode free list to fill up with vnodes, thus causing exhaustion of kernel memory. (Bug #437490) o The cfsadmin(1M) documentation is confusing. (Bug #447170) o The daemon cachefs_replacement is not stopped when CacheFS is. (Bug #448837) o Parallel CacheFS mounts can fail for a clean cache directory. (Bug #448838) - 3 - o The CacheFS mount command mount_cachefs dumps core when the disconnect option is used. (Bug #438864) o Executing them command "find . -print" on a cachefs file system whose back file system is sufficiently large, can lead to the exhaustion of system memory. (Bug #433924) o CacheFS will leak memory on certain read errors. (Bug #433400) o Any access to a FIFO file on a CacheFS file system will cause the process to hang. (Bug #432075) o CacheFS mounts can run out of swap space when a sufficient number of cachefs entries exist in /etc/fstab. In order to correct this, mount(1M) must be instructed to limit the number of parallel mounts. This is to be done with the "-m" option provided in Patch SG0001499. Refer to cachefs(4) for information about using this option for cachefs mounts. (Bug #405727) o CacheFS sometimes returns ESTALE when the front file is stale. (Bug #418543) o CacheFS always tries to write the file header after file removal. (bug #402194) o CacheFS sometimes updates attributes but not file contents. (bug #429619) o In its strict consistency mode, the initialization of cached objects will always block when getting the attributes from the back file system even when the disconnect mount option has been specified. (Bug #429630) o CacheFS will cause a panic when the cache label file has been corrupted or is from an older version of CacheFS. (Bug #424985) o Applications will sometimes dump core when running on CacheFS due to file renames on the server or another client. (Bug #426367) o CacheFS will occasionally truncate files when they are written. (Bug #428212) o In disconnected mode, close(2) on a file on cachefs will sometimes return ETIMEDOUT. (Bug #428213) - 4 - o CacheFS will sometimes corrupt a file when it is written. (Bug #429372) o The open/creat semantics are violated by cachefs. (Bug #402185) o The df command reports incorrect or peculiar values for CacheFS file systems. (Bug #390567) o Autofs is unable to unmount CacheFS file systems once it has mounted them. (Bug #390675) o The cfsadmin "-d" option should remove only the cacheid directory (or directories). (Bug #314902) o The cfsadmin options "-d" and "-l" do not function properly. (Bug #384554) o df(1) does not function properly when its argument is a file or directory on a CacheFS file system and that file or directory is not the mount point. (Bug #384664) o The device number reported by stat(2) for files and directories on CacheFS file systems can change without the file system having been unmounted and remounted. Also, the device number may not be correct. (Bug #385264) o Cachefs misses some types of attribute changes. It will miss those changes which do not result in the modification time being changed such as permission and ownership changes. (Bug #385290) o If CacheFS is used with a NFS back-end filesystem and quotas are in use on the NFS filesystem the IRIX 6.2 CacheFS client doesn't always understand how to handle "quotas exceeded" situations. This is because CacheFS ignores write errors from the back file system. (Bug #375237) o System shutdown is unclean since CacheFS_async is holding filesystems open. This is because CacheFS_async sometimes does not exit when the file system it serves is unmounted. (bug #375241) o ls hangs when accessing a directory for which the user does not have the appropriate permission. (Bug #374667) - 5 - o CacheFS performs very poorly for commands such as find which do nothing more than lookups. The reason for this is that the file headers for the cached files are bing read and written synchronously during lookup. (Bug #367153). o When a link is made to a file on a CacheFS file system, the link count is not updated. (Bug #352995) o When a disconnected mode CacheFS mount is performed for a server which is down, the kernel will panic. (Bug #358274) o Cachefs uses the default NFS timeout for disconnected mounts. This is too long. The timeout should be set to the minimum allowed value. (Bug #360624) o It is possible for some CacheFS operations on disconnected mounts to succeed but still return ETIMEDOUT. This is because the error number is not cleared in some cases for network errors from back file system operations. (Bug #360625) o CacheFS was not holding the back vnode if VOP_REALVP was successful. This could result in any of a number of vnode related panics. (Bug #618247) o CacheFS always invalidates cached data when loading a file for execution. (Bug #638384) o Kernel panic in traverse for CacheFS mount point. (Bug #639016) o Kernel panic with negative vnode reference count. (Bug #637070) 1.4 Subsystems_Included_in_Patch_SG0003270 This patch release includes these subsystems: o patchSG0003270.onc3_eoe_sw.cachefs o patchSG0003270.onc3_eoe_man.cachefs 1.5 Installation_Instructions Because you want to install only the patches for problems you have encountered, patch software is not installed by default. After reading the descriptions of the bugs fixed in this patch (see Section 1.3), determine the patches that - 6 - meet your specific needs. If, after reading Sections 1.1 and 1.2 of these release notes, you are unsure whether your hardware and software meet the requirements for installing a particular patch, run inst. The inst program does not allow you to install patches that are incompatible with your hardware or software. Patch software is installed like any other Silicon Graphics software product. Follow the instructions in your Software Installation Administrator's Guide to bring up the miniroot form of the software installation tools. Follow these steps to select a patch for installation: 1. At the Inst> prompt, type install patchSGxxxxxxx where xxxxxxx is the patch number. 2. Initiate the installation sequence. Type Inst> go 3. You may find that two patches have been marked as incompatible. (The installation tools reject an installation request if an incompatibility is detected.) If this occurs, you must deselect one of the patches. Inst> keep patchSGxxxxxxx where xxxxxxx is the patch number. 4. After completing the installation process, exit the inst program by typing Inst> quit 1.6 Patch_Removal_Instructions To remove a patch, use the versions remove command as you would for any other software subsystem. The removal process reinstates the original version of software unless you have specifically removed the patch history from your system. versions remove patchSGxxxxxxx - 7 - where xxxxxxx is the patch number. To keep a patch but increase your disk space, use the versions removehist command to remove the patch history. versions removehist patchSGxxxxxxx where xxxxxxx is the patch number. 1.7 Known_Problems