Patch Name: PHCO_10965 Patch Description: s700_800 10.20 fsck_vxfs(1M) cumulative patch Creation Date: 97/05/06 Post Date: 97/05/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 Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHCO_10965 Symptoms: 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_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: 123456789012345678901234567890123456789012345678901234567890 The inode summary fields in the new allocation unit added by extendfs were not properly initialized. So whatever happened to be in the block wound up being treated as inode summary data. The vxfs fsck command never detected this, and the mount command was failing in the kernel due to a file system validation error. The problem is easily reproduced by executing the following: # lvcreate -L 40 -n testvol /dev/vg00 # mkfs -F vxfs -oversion=2 /dev/vg00/rtestvol # mount -Fvxfs /dev/vg00/tstvol /tmp_mnt # umount /tmp_mnt # lvextend -L 80 /dev/vg00/testvol # extendfs -F vxfs /dev/vg00/rtestvol # mount -F vxfs /dev/vg00/testvol /tmp_mnt SR: 4701350124 Patch Files: /sbin/fs/vxfs/fsck what(1) Output: /sbin/fs/vxfs/fsck: 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 PATCH_10_20: /opt/langtools/lib/crt0.o aggr.o attr.o bmap.o dir.o extent.o extern.o fextop.o fse t.o inode.o links.o lwrite.o machdep.o main. o olt.o readi.o replay.o subr.o subreplay.o super.o 97/05/06 cksum(1) Output: 3031146202 352256 /sbin/fs/vxfs/fsck Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHCO_9396 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_10965 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_10965.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_10965.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_10965. 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_10965.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_10965.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None