Patch Name: PHCO_12187

Patch Description: s700_800 10.30 vxdump(1M): new-volume timeout; process hang

Creation Date: 97/08/20

Post Date:  97/08/26

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

Products: N/A

Filesets:
	JournalFS.VXFS-BASE-RUN

Automatic Reboot?: No

Status: General Release

Critical: No

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

Symptoms:
	PHCO_12187:
	1. vxdump aborts after one hour if it does not receive
	a response to the following query for mounting the next
	volume:  "vxdump: Is the new volume mounted and ready
	to go?: ("yes" or "no") ".  The following messages are
	displayed before aborting:
	"vxdump: excessive operator query failures"
	"vxdump: The ENTIRE dump is aborted."
	2. A vxdump session intermittently hangs forever.
	This was seen when several vxdump sessions were
	started to backup different file systems to different
	tape drives at the same time.  Sometimes one of the
	sessions does not finish and hangs.

Defect Description:
	PHCO_12187:
	1. vxdump aborts after an hour if it does not receive a
	response to the following prompt for next volume:
	"vxdump: Is the new volume mounted and ready to
	go?: ("yes" or "no") ".  The following messages are
	displayed before vxdump aborts:
	"vxdump: excessive operator query failures"
	"vxdump: The ENTIRE dump is aborted."
	The timeout works such that it queries for the next
	volume, and then sends a beep to the console every two
	minutes to alert the operator that it needs attention.
	After 30 times (every 2 minutes = 1 hour), vxdump
	aborts.
	2. A vxdump session is comprised of 5 vxdump processes.
	The parent vxdump forks a child vxdump and just waits
	for this child to finish.  This child becomes the master
	vxdump process which is responsible for selecting the files
	to backup.  It creates three child (slave) processes and
	has a separate unnamed pipe through which it communicates
	to each slave.  The slaves work in a round-robin fashion
	by reading the selected file and writing to the tape.
	The slave that has just finished using the tape notifies
	the next slave that it can use the tape by sending it a
	signal.  The problem is that this signal is not always
	caught correctly and all three slaves end up waiting,
	causing the vxdump session to hang forever.

SR:
	1653215616 1653211300

Patch Files:
	/usr/lbin/fs/vxfs/vxdump
	/usr/sbin/rvxdump
	/usr/sbin/vxdump

what(1) Output:
	/usr/lbin/fs/vxfs/vxdump:
		PATCH_10_30: itime.o main.o optr.o tape.o traverse.o
			 unctime.o dumprmt.o 97/08/20
	/usr/sbin/rvxdump:
		PATCH_10_30: itime.o main.o optr.o tape.o traverse.o
			 unctime.o dumprmt.o 97/08/20
	/usr/sbin/vxdump:
		PATCH_10_30: itime.o main.o optr.o tape.o traverse.o
			 unctime.o dumprmt.o 97/08/20

cksum(1) Output:
	517004603 102400 /usr/lbin/fs/vxfs/vxdump
	517004603 102400 /usr/sbin/rvxdump
	517004603 102400 /usr/sbin/vxdump

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes: None

Equivalent Patches: None

Patch Package Size: 150 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_12187

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

		swinstall -x autoreboot=true -x match_target=true \
			-s /tmp/PHCO_12187.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/PHCO_12187.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/PHCO_12187.  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_12187.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_12187.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions: None