Patch Name: PHKL_18987

Patch Description: s700 10.26 VxFS (JFS) mount,fsck cumulative patch

Creation Date: 99/09/03

Post Date:  99/11/17

Hardware Platforms - OS Releases:
	s700: 10.26

Products: N/A

Filesets:
	JournalFS.VXFS-BASE-KRN

Automatic Reboot?: Yes

Status: General Superseded

Critical:
	Yes
	PHKL_18987: CORRUPTION PANIC HANG

Path Name: /hp-ux_patches/s700/10.X/PHKL_18987

Symptoms:
	PHKL_18987:
	Ported 10.20 patch PHKL_18197 to TOS.
	(PHKL_18197)
	On vxfs filesystems where a particular type of inode
	corruption occurs, all future mounts of that filesystem
	fail.  In the message buf will be the message:
	   vx_iget - [fs name] file system invalid inode number [#]
	This message will possibly be repeated many times.  Future
	attempts to mount this file system will fail with either:
	   vxfs mount: [device] is not a vxfs file system
	or vxfs mount: [device] is corrupted. needs checking
	At that point, if an fsck is performed the file system can
	be mounted, but further use of the file system may cause
	the vx_iget message to occur again, and the file system to
	again be unmountable.
	(PHKL_17716)
	SR: 4701411298 DTS: JAGaa45918
	A panic may occur in vx_spinlock() when trying to mount
	a corrupt VxFS file system.
	This patch provides a fix so that a failure is reported
	in this case, but a panic will not occur.
	(PHKL_12339)
	Mounting a VxFS Version 2 filesystem containing a large
	amount of files (in excess of 800,000) can take several
	minutes to complete. During the time it takes to mount
	the filesystem the system appears to be hung.
	This patch provides improved kernel routines which
	eliminate this performance problem.
	(PHKL_12007)
	fsck on vxfs (version 3) filesystem fails with
	the following error:
	   # fsck -o full -y /dev/vg01/lvol3
	     pass0 - checking structural files
	     pass1 - checking inode sanity and blocks
	     pass2 - checking directory linkage
	     pass3 - checking reference counts
	     pass4 - checking resource maps
	     small extent in iau inode
	This occured after a normal shutdown.  The filesystem
	is unusable and must be newfs'd.
	This patch provides the kernel half of a solution for an
	fsck defect.  The commands patch PHCO_17671 must also be
	applied to install the full solution.
	Without the command patch PHCO_17671 installed, this patch
	will have no impact.

Defect Description:
	PHKL_18987:
	The vxfs kernel was not properly handling sparse IFILT
	files.  This was due to fsh_ninode being incorrectly set in
	this case, as well as the end of the IFILT list being
	calculated incorrectly.
	Resolution:
	vx_fsetialloc() was updated to properly update fsh_ninode
	in the case of a sparse IFILT file.  vx_olt_ilistadd() was
	updated to properly find the end of the IFILT list in this
	case.  This prevents a corrupt filesystem from getting
	worse, and will not fix the inital cause of the corruption.

SR:
	1653297531 4701361758 4701411298 5003383307

Patch Files:
	/usr/conf/lib/libvxfs_base.a(vx_fsetsubr.o)
	/usr/conf/lib/libvxfs_base.a(vx_oltmount.o)

what(1) Output:
	/usr/conf/lib/libvxfs_base.a(vx_fsetsubr.o):
		99/06/22 kern/vxfs/vx_fsetsubr.c, hpux, hpux_10.26,
			ic5db Revision 1.2 PATCH_10.26 (PHKL_18987)
			UNMODIFIED
	/usr/conf/lib/libvxfs_base.a(vx_oltmount.o):
		99/06/22 kern/vxfs/vx_oltmount.c, hpux, hpux_10.26,
			ic5db Revision 1.3 PATCH_10.26 (PHKL_18987)
			UNMODIFIED

cksum(1) Output:
	1951719763 22920 /usr/conf/lib/libvxfs_base.a(vx_fsetsubr.o)
	1989997113 29744 /usr/conf/lib/libvxfs_base.a(vx_oltmount.o)

Patch Conflicts: None

Patch Dependencies:
	s700: 10.26: PHKL_17282 PHCO_17671

Hardware Dependencies: None

Other Dependencies: None

Supersedes: None

Equivalent Patches:
	PHKL_18988:
	s800: 10.26

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_18987

	5a. For a standalone system, run swinstall to install the
	    patch:

		swinstall -x autoreboot=true -x match_target=true \
			-s /tmp/PHKL_18987.depot

	By default swinstall will archive the original software in
	/var/adm/sw/patch/PHKL_18987.  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_18987.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_18987.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	This patch provides the kernel half of a solution for an
	fsck defect.  The commands patch PHCO_17671 must also be
	applied to install the full solution.  Without PHCO_17671
	installed, this patch will have no impact.