Patch Name: PHKL_17520 Patch Description: s700 10.20 JFS fsadm ENOSPC, performance improvement patch Creation Date: 99/02/01 Post Date: 99/02/02 Hardware Platforms - OS Releases: s700: 10.20 Products: N/A Filesets: JournalFS.VXFS-BASE-KRN Automatic Reboot?: Yes Status: General Release Critical: No Path Name: /hp-ux_patches/s700/10.X/PHKL_17520 Symptoms: PHKL_17520: SR: 4701406454 DTS: JAGaa42801 JFS file systems with large amounts of free space can get 'vx_nospace' (ENOSPC) errors while 'fsadm' is running a defragmentation (-e option). SR:1653244277 DTS: JAGaa01284 System becomes unresponsive while running a defragmentation of a JFS file system using the 'fsadm' command (-e option). When in this state the 'fsadm' process consumes more than 99 percent of the CPU. Performance returns when the Defect Description: PHKL_17520: SR: 4701406454 DTS: JAGaa42801 In some cases we try to allocate more space than is left in a given bitmap in 'vx_extsearchodd()'. This causes a false ENOSPC return. SR:1653244277 DTS: JAGaa01284 The arguments to the functions 'vx_extsearchodd()' and 'vx_extsearchanyodd()' were not searching the correct range in a bitmap in some cases. This would cause useless work to be done for each REORG ioctl, and would cause the ioctl system call to monopolize the CPU. SR: 4701406454 1653244277 Patch Files: /usr/conf/lib/libvxfs_base.a(vx_alloc.o) what(1) Output: /usr/conf/lib/libvxfs_base.a(vx_alloc.o): vx_alloc.c $Date: 99/01/29 13:14:09 $ $Revision: 1.5 .98.16 $ PATCH_10.20 (PHKL_17520) cksum(1) Output: 1141528285 28260 /usr/conf/lib/libvxfs_base.a(vx_alloc.o) Patch Conflicts: None Patch Dependencies: s700: 10.20: PHKL_16750 Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: PHKL_17521: s800: 10.20 Patch Package Size: 90 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_17520 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_17520.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_17520.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_17520. 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_17520.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_17520.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: This patch depends on base patch PHKL_16750 . For successful installation please insure that PHKL_16750 is in the same depot with PHKL_17520, or PHKL_16750 is already installed.