Patch Name: PHKL_17526 Patch Description: s700 10.20 JFS sync/freeze 'dirty inval' panic 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 Superseded Critical: Yes PHKL_17526: PANIC Path Name: /hp-ux_patches/s700/10.X/PHKL_17526 Symptoms: PHKL_17526: SR: 1653285320 DTS: JAGaa44494 System panics with "panic: dirty inval" message. A stack trace might look like: panic+0x10 brelse+0x230 vx_brelse_bp+0x34 vx_brelse_noflush+0x34 vx_brelse+0x3c vx_brelse_stale+0x2c vx_blkinval+0x12c vx_freeze_level+0x114 vx_freeze+0x10 vx_vfsfreeze+0x28 freeze_and_sync_fs_dev+0x38 lv_single_freeze_fs+0xd0 lv_realloclv+0x668 lv_ioctl+0x9bc spec_ioctl+0xd4 vno_ioctl+0x98 ioctl+0x78 syscall+0x1a4 $syscallrtn+0x0 Defect Description: PHKL_17526: SR: 1653285320 DTS: JAGaa44494 A JFS file system that is in the frozen state could have activity generated by a 'sync' system call. This leaves some buffers in the 'invalid' (B_INVAL) and delayed write (B_DELWRI) state. This causes a panic. Running the 'lvmerge' command and sync at the same time on the same file system might reproduce the problem. Resolution: Protect the 'vx_delxwri_flush_inode()' call in 'vx_delxwri_flush()' with an ACTIVE1 level so that sync and freeze will coordinate. SR: 1653285320 Patch Files: /usr/conf/lib/libvxfs_base.a(vx_iflush.o) what(1) Output: /usr/conf/lib/libvxfs_base.a(vx_iflush.o): vx_iflush.c $Date: 99/02/01 09:15:59 $ $Revision: 1. 6.98.16 $ PATCH_10.20 (PHKL_17526) cksum(1) Output: 2002218658 29796 /usr/conf/lib/libvxfs_base.a(vx_iflush.o) Patch Conflicts: None Patch Dependencies: s700: 10.20: PHKL_16750 Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: PHKL_17527: 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_17526 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_17526.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_17526.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_17526. 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_17526.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_17526.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_17526, or PHKL_16750 is already installed.