Patch Name: PHKL_26476

Patch Description: s700_800 11.00 Panic extending JFS3.1 filesystem past 128GB

Creation Date: 02/03/18

Post Date:  02/03/19

Hardware Platforms - OS Releases:
	s700: 11.00
	s800: 11.00

Products: N/A

Filesets:
	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP

Automatic Reboot?: Yes

Status: General Release

Critical:
	Yes
	PHKL_26476: PANIC

Category Tags:
	defect_repair general_release critical panic

Path Name: /hp-ux_patches/s700_800/11.X/PHKL_26476

Symptoms:
	PHKL_26476:
	( SR:8606233690 CR:JAGae02914 )
	System panics with 'dirty inval' when trying to extend a
	JFS filesystem beyond 128GB.  The panic stack trace will
	be similar to:

	panic: dirty inval

	panic+0x14
	brelse+0x284
	vx_brelse_bp+0x38
	vx_brelse_noflush+0x3c
	vx_brelse+0x2c
	vx_brelse_stale+0x2c
	vx_resize_sumcalc+0x5c4
	vx_resize_buildout+0xc0
	vx_resize+0x4f0
	vx_aioctl_fullfs+0x128
	vx_aioctl_common+0x518
	vx_aioctl+0x80
	vx_ioctl+0xf8
	vno_ioctl+0x90
	ioctl+0x1f4
	syscall+0x6f8
	$syscallrtn+0x0

Defect Description:
	PHKL_26476:
	( SR:8606233690 CR:JAGae02914 )
	When trying to extend a vxfs filesystem beyond 128GB
	using fsadm(1M), the system will panic with a 'dirty
	inval' panic due to a failure to flush dirty smaps
	after updating the extent maps for the resize.

	Resolution:
	We now ensure that any dirty smaps are flushed after
	the extent maps are updated for resize.

SR:
	8606233690

Patch Files:
	
	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
	/usr/conf/lib/libvxfs_base.a(vx_resize.o)

	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
	/usr/conf/lib/libvxfs_base.a(vx_resize.o)

what(1) Output:
	
	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
	/usr/conf/lib/libvxfs_base.a(vx_resize.o):
		vx_resize.c $Date: 2002/02/28 09:40:57 $Revision: r1
			1ros/1 PATCH_11.00 (PHKL_26476)

	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
	/usr/conf/lib/libvxfs_base.a(vx_resize.o):
		vx_resize.c $Date: 2002/02/28 09:40:57 $Revision: r1
			1ros/1 PATCH_11.00 (PHKL_26476)

cksum(1) Output:
	
	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
	2543258694 20180 /usr/conf/lib/libvxfs_base.a(vx_resize.o)

	JournalFS.VXFS-BASE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
	1501958892 35888 /usr/conf/lib/libvxfs_base.a(vx_resize.o)

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes: None

Equivalent Patches: None

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_26476

	5. Run swinstall to install the patch:

		swinstall -x autoreboot=true -x patch_match_target=true \
			  -s /tmp/PHKL_26476.depot

	By default swinstall will archive the original software in 
	/var/adm/sw/save/PHKL_26476.  If you do not wish to retain a
	copy of the original software, include the patch_save_files
	option in the swinstall command above:

		-x patch_save_files=false

	WARNING: If patch_save_files is false when a patch is installed,
		 the patch cannot be deinstalled.  Please be careful
		 when using this feature.

	For future reference, the contents of the PHKL_26476.text file is 
	available in the product readme:

		swlist -l product -a readme -d @ /tmp/PHKL_26476.depot

	To put this patch on a magnetic tape and install from the
	tape drive, use the command:

		dd if=/tmp/PHKL_26476.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions: None