Patch Name: PHKL_17518 Patch Description: s700 10.20 JFS Corruption stack overflow panic: dirty inval Creation Date: 99/01/29 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 Superseded Critical: Yes PHKL_17518: PANIC PHKL_16918: CORRUPTION PHKL_12951: PANIC Path Name: /hp-ux_patches/s700/10.X/PHKL_17518 Symptoms: PHKL_17518: SR: 4701413864 CR: JAGaa52714 The system panics with a 'Dirty Inval' panic message when unmounting a large (greater than 128 Gigabyte) filesystem. PHKL_16918: SR: 1653265041 DTS: JAGaa42790 The following error may appear in syslog: vxfs: mesg 048: vx_mapbad - file system extent allocation unit state bitmap number 0 marked bad After the error, filesystem prematurely fills up, causing the filesystem to be unmounted and a full fsck run against it. PHKL_12951: A kernel stack overflow panic occurs when the stack is valid and all the 3 pages allocated for kernel stack are consumed. The defect is seen when a combination of NFS,LVM,JFS related functions are used. Defect Description: PHKL_17518: SR: 4701413864 CR: JAGaa52714 vx_smap_flush() calls vx_getsmap() passing the map number as the second parameter while vx_getsmap() expects the allocation unit (AU) number. This causes vx_smap_flush() to NOT wait on the B_DELWRI buffer for this map which will later cause the panic. Resolution: Pass in an Allocation Unit number rather than a map number to vx_getsmap() from vx_smap_flush(). PHKL_16918: In vx_clonemap() we copied the extent map (or smap) bitmaps before the vx_tranflush() that would cause delayed extent frees to be processed. Once the log was flushed, the extents were marked as free and then the clone was written. When the clone write completed, the transaction could be logged as done. If logged as done, and a subsequent system crash occurred before the map with the extents actually marked as free was flushed to disk, then replay would not replay the extent (or AU) free operation the vx_tranflush() that would cause delayed extent frees to be frees to be processed. Once the log was flushed, the extents were marked as free and then the clone was written. When the clone write completed, the transaction could be logged as done. If logged as done, and a subsequent system crash occurred before the map with the extents actually marked as free was flushed to disk, then the replay would not replay the exten (or AU) free operation. PHKL_12951: The defect is due to allocation of large data structures (local variables) on stack when a function is called. The fix was to re-compile the object modules(JFS)with a compiler option (+ESssf - small stack frame) to align the stack pointer to 32-byte boundary instead of 64-byte boundary. This prevents the kernel stack overflow panic. SR: 1653265041 4701413864 5003387019 Patch Files: /usr/conf/lib/libvxfs_base.a(vx_ausum.o) /usr/conf/lib/libvxfs_base.a(vx_bitmaps.o) /usr/conf/lib/libvxfs_base.a(vx_bmap.o) /usr/conf/lib/libvxfs_base.a(vx_tran.o) what(1) Output: /usr/conf/lib/libvxfs_base.a(vx_ausum.o): vx_ausum.c $Date: 97/10/20 14:48:37 $ $Revision: 1.2 .98.10 $ PATCH_10.20 (PHKL_12951) /usr/conf/lib/libvxfs_base.a(vx_bitmaps.o): vx_bitmaps.c $Date: 99/01/29 11:27:17 $ $Revision: 1 .7.98.9 $ PATCH_10.20 (PHKL_17518) /usr/conf/lib/libvxfs_base.a(vx_bmap.o): vx_bmap.c $Date: 97/10/20 14:53:57 $ $Revision: 1.5. 98.13 $ PATCH_10.20 (PHKL_12951) /usr/conf/lib/libvxfs_base.a(vx_tran.o): vx_tran.c $Date: 97/10/20 14:54:49 $ $Revision: 1.7. 98.11 $ PATCH_10.20 (PHKL_12951) cksum(1) Output: 1581942250 10312 /usr/conf/lib/libvxfs_base.a(vx_ausum.o) 2773443982 12408 /usr/conf/lib/libvxfs_base.a(vx_bitmaps.o) 439837300 5232 /usr/conf/lib/libvxfs_base.a(vx_bmap.o) 3781156841 20292 /usr/conf/lib/libvxfs_base.a(vx_tran.o) Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_12951 PHKL_16918 Equivalent Patches: PHKL_17519: s800: 10.20 Patch Package Size: 110 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_17518 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_17518.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_17518.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_17518. 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_17518.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_17518.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None