Patch Name: PHCO_20330

Patch Description: s700_800 10.20 fsck_hfs(1M) cumulative patch

Creation Date: 99/11/19

Post Date:  99/12/02

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

Products: N/A

Filesets:
	OS-Core.UX-CORE

Automatic Reboot?: No

Status: General Release

Critical:
	No (superseded patches were critical)
	PHCO_12435: PANIC
	PHCO_12067: PANIC

Path Name: /hp-ux_patches/s700_800/10.X/PHCO_20330

Symptoms:
	PHCO_20330:
	fsck will coredump when checking some hfs
	filesystems.

	PHCO_12435:
	This fix is needed in addition to the one in PHCO_12067
	in order to fix the filesystem corruption problem.
	Fsck may corrupt a filesystem by not properly clearing
	an inode after clearing its associated continuation
	inode.  The filesystem will be marked clean.  If this
	inode is accessed once the filesystem is mounted, it
	can result in a system panic.

	PHCO_12067:
	Fsck may corrupt a filesystem containing continuation
	inodes by clearing the wrong continuation inode.  The
	filesystem will be marked clean.  If this inode is a
	continuation inode, and the base inode is accessed once
	the file system is mounted, it can result in a system
	panic.

	PHCO_7817:
	If the system is booted into LVM maintenance mode, doing an
	fsck of a device defined to have an HFS file system will
	produce the error message

	DeviceName(): Cannot determine name of device major=??,
	                                              minor=??

	where the major and minor numbers may differ, depending on
	the system.  This prevents the fsck from succeeding.

Defect Description:
	PHCO_20330:
	In cases where the size field or super block size field
	becomes invalid, it is possible for 'ndb' to become
	negative, when 'ndb' is used as a array index, a segment
	violation (core dump) is caused due to an invalid memory
	access.

	PHCO_12435:
	The problem appears when an inode with a continuation
	inode needs to be cleared.  The continuation inode
	is recursively cleared first.  The base inode should
	then be cleared, but some of the values have been
	altered by clearing the continuation inode, causing
	the base inode not to be fully cleared.  Thus it
	leaves this inode in the filesystem pointing to a
	cleared continuation inode.  Accessing this inode
	can cause a system panic.

	PHCO_12067:
	The problem appears when an inode has been corrupted that
	has a continuation inode.  If the inode's continuation
	inode information is corrupt, it is possible that a random
	inode will be cleared.  This problem can cause system
	inconsistencies, and a subsequent panic.

	The problem is caused by missing braces after an
	if-statement, causing an inode to be cleared even though
	the variable was never set to the correct inode value.

	PHCO_7817:
	The problem will only appear when the system is booted into
	LVM maintenance mode, which is usually used only for system
	repair.

	fsck tries to determine if the device that fsck was invoked
	upon is a swap device, but in this mode, the device numbers
	are not mapped where the swap device checking routine can
	determine this information.  It mistakenly exits instead
	of letting the user continue if desired.

SR:
	8606107242 4701344432 4701329011

Patch Files:
	/sbin/fs/hfs/fsck

what(1) Output:
	/sbin/fs/hfs/fsck:
		$Revision: 78.5.1.5 $
		PATCH-PHCO_18644 for 10.20; for 10.30, 11.x compatib
			ility libc.a_ID@@/main/r10dav/libc_dav/libc_
			dav_cpe/9
		/ux/core/libs/libc/archive_pa1/libc.a_ID
		Jul  8 1999 15:44:31
		PATCH_10_20: fsck.o cache.o ufs_tables.o ufs_subr.o
			hpux_rel.o 99/11/19

cksum(1) Output:
	3503658292 253952 /sbin/fs/hfs/fsck

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHCO_7817 PHCO_12067 PHCO_12435

Equivalent Patches: None

Patch Package Size: 310 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 PHCO_20330

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

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

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

Special Installation Instructions: None