Patch Name: PHKL_18913 Patch Description: s700 10.20 Correct VxFS fsadm resize problems Creation Date: 99/06/18 Post Date: 99/06/22 Hardware Platforms - OS Releases: s700: 10.20 Products: N/A Filesets: JournalFS.VXFS-BASE-KRN Automatic Reboot?: Yes Status: General Release Critical: Yes PHKL_18913: PANIC PHKL_9940: CORRUPTION Path Name: /hp-ux_patches/s700/10.X/PHKL_18913 Symptoms: PHKL_18913: ( SR: 1653304642 CR: JAGab17264 ) When trying to use the OnLine JFS fsadm resize capability to resize a Vxfs Version 2 file system, the system may panic with a data page fault in function vx_resize_mapupd(). PHKL_9940: When trying to use the OnLine JFS fsadm resize capability to grow a file system greater than 2Gb, the fsadm command will fail with an errno of 28, and the file system will report I/O errors on any attempted access. The file system becomes unusable at this point. Defect Description: PHKL_18913: ( SR: 1653304642 CR: JAGab17264 ) When trying to resize a VxFS Version 2 file system, the new number of allocation units needed by the file system was calculated incorrectly for VxFS version 2 file systems. Resolution: The calculation for the number of allocation units needed when resizing a VxFS file system was corrected to apply to both Version 2 and Version 3 file systems. PHKL_9940: The problem can be reproduced by executing the following: - create a 4Gb volume, and newfs a VxFS file system on it - mount this file system - run lvextend to extend the volume to 6Gb - run VxFS fsadm command to try to grow the fs to 6Gb This fsadm command will fail. Two resize bugs were uncovered with this problem. The first was in vx_resize_sumcalc() which calculates the new values for the fs_efree array; the code was only copying VX_SNEFREE entries (16) so higher entries from the multiple allocation unit summaries were not getting copied into the file system summary. The other was that two emap inodes wound up with different layouts caused by an extending allocation; the code in vx_resize_icopy() failed to take the extent offset (returned from the bmap call) into account. SR: 1653304642 5003352096 Patch Files: /usr/conf/lib/libvxfs_base.a(vx_resize.o) what(1) Output: /usr/conf/lib/libvxfs_base.a(vx_resize.o): vx_resize.c $Date: 99/06/18 08:13:10 $ $Revision: 1. 5.98.10 $ PATCH_10.20 (PHKL_18913) cksum(1) Output: 1193412150 16240 /usr/conf/lib/libvxfs_base.a(vx_resize.o) Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_9940 Equivalent Patches: PHKL_18914: s800: 10.20 Patch Package Size: 80 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 PHKL_18913 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_18913.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/PHKL_18913.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/PHKL_18913. 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 PHKL_18913.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/PHKL_18913.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None