Patch Name: PHCO_11908 Patch Description: s700_800 10.20 fsck_vxfs(1M) cumulative patch Creation Date: 97/07/25 Post Date: 97/08/11 Warning: 97/09/23 - This Critical Warning has been issued by HP. -Systems having installed PHCO_11908 may experience problems resulting in messages similar to: vx_mapbad - /var file system free inode bitmap in au 0 marked bad -Afterwards it will be impossible to create new files on the filesystem. Messages similar to the below example will show up. vx_iget - /var file system invalid inode number XXXXXX -A full fsck (fsck -F vxfs -o full ) will mark the filesystem as clean, but the problem persists. The filesystem is mostly useless since no files can be added to it. -The filesystem can be recovered by installing PHCO_11909 and re-running a full fsck on it. -Systems having PHCO_11908 installed should immediately update to PHCO_11909. -PHCO_11909 is available since 97/08/15. Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: N/A Filesets: JournalFS.VXFS-BASE-RUN Automatic Reboot?: No Status: General Superseded With Warnings Critical: Yes PHCO_11908: CORRUPTION Path Name: /hp-ux_patches/s700_800/10.X/PHCO_11908 Symptoms: PHCO_11908: The fsck command was unable to handle iau data that was spread across multiple extents. This resulted in a file system that could not be repaired. PHCO_11223: VxFs fsck sometimes fails with -y with the message "no valid ILISTS for fileset 999". PHCO_10965: After a hard failure, running a full fsck on a vxfs file system that contains directories larger than approximately 200 Kbytes may result in an unrecoverable file system. The exact size is fuzzy, depending on a number of factors including the geometry of other files in the file system. The problem can also occur for large sparse files. A sparse file with more than 256 Gbytes of data blocks, written using small writes might experience the same problem. PHCO_9396: If a customer upgrades from 10.01 or 10.10 to 10.20, and tries to increase their VxFS file systems via SAM, the file system will not mount after completion of extending the volume and file system. The typical approach for SAM is: 1) unmount the file system 2) lvextend the volume 3) extendfs the file system 4) mount the file system The mount will always fail in this case. Defect Description: PHCO_11908: The fsck command was unable to handle iau data that was spread across multiple extents. This resulted in a file system that could not be repaired. PHCO_11223: VxFs fsck sometimes fails with -y with the message "no valid ILISTS for fileset 999". PHCO_10965: After a hard failure, running a full fsck on a vxfs file system that contains directories larger than approximately 200 Kbytes may result in an unrecoverable file system. The exact size is fuzzy, depending on a number of factors including the geometry of other files in the file system. The problem can also occur for large sparse files. A sparse file with more than 256 Gbytes of data blocks, written using small writes might experience the same problem. PHCO_9396: If a customer upgrades from 10.01 or 10.10 to 10.20, and tries to increase their VxFS file systems via SAM, the file system will not mount after completion of extending the volume and file system. The typical approach for SAM is: 1) unmount the file system 2) lvextend the volume 3) extendfs the file system 4) mount the file system The mount will always fail in this case. SR: 4701361758 Patch Files: /sbin/fs/vxfs/fsck what(1) Output: /sbin/fs/vxfs/fsck: PATCH_10_20:PHCO_11223 /opt/langtools/lib/crt0.o agg r.o attr.o bmap.o dir.o extent.o extern.o fe xtop.o fset.o inode.o links.o lwrite.o machd ep.o main.o olt.o readi.o replay.o subr.o su breplay.o super.o May 30 1997 PATCH/10.20:PHCO_8764 libc.a_ID@@/main/r10dav/libc_d av/libc_dav_cpe/2 /ux/libc/libs/libc/archive_pa1/libc.a_ID Oct 2 1996 10:35:25 cksum(1) Output: 3703301933 352256 /sbin/fs/vxfs/fsck Patch Conflicts: None Patch Dependencies: s700: 10.20: PHKL_9370 PHKL_12007 s800: 10.20: PHKL_9371 PHKL_12008 Hardware Dependencies: None Other Dependencies: None Supersedes: PHCO_9396 PHCO_10965 PHCO_11223 Equivalent Patches: None Patch Package Size: 400 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHCO_11908 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_11908.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHCO_11908.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHCO_11908. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHCO_11908.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHCO_11908.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None