Patch Name: PHCO_24437

Patch Description: s700_800 11.00 LVM commands cumulative patch

Creation Date: 01/06/25

Post Date: 01/06/25

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

Products: N/A

Filesets:
	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
	LVM.LVM-MIRROR-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP

Automatic Reboot?: No

Status: General Release

Critical:
	Yes
	PHCO_24437: CORRUPTION
	PHCO_23791: CORRUPTION
	PHCO_23499: PANIC

Category Tags:
	defect_repair enhancement general_release critical panic
	corruption

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

Symptoms:
	PHCO_24437:
	( SR: 1653162065 CR: JAGaa10504 )
	When running lvdisplay simultaneously with the
	pvmove and the lvmerge commands, the lvdisplay command
	displays zeros extent information.

	( SR: 8606198826 CR: JAGad68015 )
	The lvlnboot -v command displays incorrect boot disk
	information when the boot disks order in the lvmtab file
	is reversed.

	( SR: 5003432500 CR: JAGaa52059 )
	The pvdisplay -v command shows incorrect information
	about physical extent(s) and logical extent(s), if
	the number of the extent(s) is more than 9999.

	( SR: 8606161148 CR: JAGad30464 )
	The vgimport command will fail with the following
	error message, if the imported volume group has a
	logical volume with the minor number of 255.

	Warning: Logical Volume number "nn" found on
	physical volume not found in "xxxxx".
	where "nn" is the logical volume number, and "xxxxx"
	is the mapfile name.

	( SR: 8606111918 CR: JAGab84052 )
	The vgscan command puts a bogus entry in the lvmtab
	file, when a special file /dev/slvmvg is present
	with the same minor number as /dev/vg00.

	( SR: 8606199183 CR: JAGad68371 )
	The lvextend command could lead to data corruption, if the
	user enters the same physical volume more than once in the
	command line.

	PHCO_23791:
	(CR: JAGad55191  SR: 8606185986)
	When the size of the file "/etc/lvmpvg" gets more
	than 8k bytes (characters), customers may encounter
	the following problems:

	   lvcreate fails with:
	   Error detected when reading from file "/etc/lvmpvg".

	   pvdisplay reports a warning:
	   Bad file "/etc/lvmpvg": Missing PVG keyword.

	(CR:JAGad50582 SR:8606181365)
	Data loss and corruption can result from attempting
	to use LVM with "Virtual Array" disk arrays.

	PHCO_23499:
	(CR: JAGad46538     SR: 8606177306)
	LVM pvol structure is not getting released which prevents
	creating/importing volume groups on the system.
	Customer may eventually come up to the situation
	when all minor numbers are exhausted and this would
	require the system reboot.
	It is not possible to modify volume group minor id and
	name in shared mode.

	(CR: JAGad05245     SR: 8606136115)
	System panic when CPU0 was doing "vgdisplay -v" on a
	cluster volume group.
	This panic occurred when user was activating and
	deactivating a cluster volume group. Data page fault
	at lv_querylvmap. The stack trace looks like:
	panic+0x14
	report_trap_or_int_and_panic+0x80
	trap+0xdb8
	nokgdb+0x8
	lv_querylvmap+0x11c
	lv_ioctl+0xff8
	spec_ioctl+0xac
	vno_ioctl+0x90
	ioctl+0x1e4
	syscall+0x200
	$syscallrtn+0x0

	PHCO_23076:
	(CR: JAGad50461     SR: 8606181244)
	New functionality in LVM to support "Virtual Array"
	disk arrays.

	PHCO_22839:
	(CR: JAGad38961     SR: 8606169686)
	Currently, LVM commands recognize XP disk
	arrays such as XP256 and XP512.  LVM commands
	do not recognize XP48 as part of the XP disk
	array family.

	PHCO_21630:
	(CR: JAGac78496     SR: 8606127694)
	When two VGs created with the same name, one
	with an extra alash ("/") at the end of the group
	file, many LVM commands will fail to recognize
	they are different VGs and get confused.  This
	situation leads to LVM command failing and
	sometimes system panics.

	(CR: JAGad06173     SR: 8606137055)
	The vgchgid command currently only changes the
	VGID on EMC and XP256 devices.  Even though the
	XP512 came from the same family as XP256, but
	they have different product-id.  In this case,
	vgchgid will not recognize XP512, and it will
	fail to modify the VGID on the split-off mirror
	copy when it is needed.

	PHCO_21269:
	Customer needs new functionality in the LVM
	command vgchgid to support XP256 disk array.

	PHCO_20870:
	(CR: JAGaa46006   SR: 1653288878)
	Various LVM commands coredump on systems where
	any PV has more than 4 PVlinks (one primary and
	3 alternates).

	(CR: JAGab83482   SR: 8606110734)
	The pvdisplay command displays "PV Status" as
	available when a disk is powerfailed.  (JAGab83482)

	(CR: JAGab83470   SR: 8606110722)
	vgimport needs a method to specify disk list in
	a file.

	(CR: JAGad02854  SR: 8606133710)
	Need method to remove an unattached path without
	using vgexport/import.

	(CR: JAGad02856   SR: 8606133712)
	Need a method to see the pvchange(1m) autoswitch
	setting.

	PHCO_20054:
	1. vgcreate with a disk having more than 64K
	   extents sets up the VG incorrectly.
	2. vgreduce deletes PV entries from /etc/lvmtab
	   for a read-only Volume Group
	3. vgreduce deletes a PV from /etc/lvmtab
	   even when the PV has some extents in use
	   under certain circumstances.
	4. When a VG has one PV and multiple links
	   vgremove still removes the VG, but doesn't
	   cleanup /etc/lvmtab.

	PHCO_19631:
	1. vgextend doesn't print a proper error
	   message when supplied with a character
	   device name rather than a block device
	   name.
	2. Enhancement to identify VxFS version 4
	   filesystem.

	PHCO_19479:
	1. vgdisplay used to show wrong number of free
	   extents, if the total number of free extents
	   exceeded 64K in number.
	2. lvcreate -I would not allow stripe sizes
	   more than 64 K.

	PHCO_19205:
	1. lvlnboot -R used to corrupt BDRA data under
	   certain circumstances.
	2. "vgchange -a r; vgchange -a y" doesn't print
	   error message.
	3. lvdisplay incorectly displays extents
	   larger than 4 digits.
	4. pvremove command is disabled.

	PHCO_18485:
	This patch does not include the pvremove(1M)
	command. PHCO_17453 introduced this new
	functionality mistakenly, and has been recalled.
	This patch fix the problem for vgcfgbackup
	and vgextend.
	vgcfgbackup - invalid lvmrecord was backup
	due to lack of sanity check in this command.
	vgextend - users are limited to create volume
	group with maximum physical extents of 65535.
	This is incorrect.

	PHCO_17453:
	The introduction of the VERITAS Volume Manager
	(VxVM) requires several enhancements for LVM
	coexistence with VxVM.

	PHCO_18292:
	This patch has the following fixes :
	1. This patch fix the data corruption problem
	   when mirrored logical volumes are created
	   on PVGs which has PVs with alternate links.
	2. LVM allows creation of stripes greater than
	   the total size of physical volumes in the
	   volume group.
	3. Limit for Stripe size is 64K currently
	   where as it can go upto 32MB.

	PHCO_16851:
	This patch has the following fixes :
	1. LVM scripts which lvextend one extent at a time
	   (where the next logical extent added is always
	   placed on a different physical volume from the
	   preceding logical extent) can take hours to run
	   for large logical volumes (i.e. 50gb). The goal
	   of this kind of configuration is to create
	   "extent-based mirrored stripes".  LVM provides
	   no alternate method for creating "extent-based
	   mirrored stripes".
	2. The SG stress suite is unable to shutdown the
	   cluster after 24 hours or so because it can't
	   shutdown the LVM daemon.
	3. lvremove occasionally fails to remove logical
	   volumes with an error message saying that it is
	   a swap device, when it is not.

	PHCO_16248:
	If any of the PVs which belong to a VG are involved
	in any LVM commands operation, is not available
	after the device is opened. The system hangs on
	subsequent read/write since it is doing a blocking
	operatin. Eg: vgcfgbackup hangs when a PV is unavailable
	after opening it.

	PHCO_16090:
	vgextend prohibits even partial use of disks
	larger than the defined Max_PE_per_PV.

	PHCO_15237:
	lvcreate was dumping core when given out-of-range
	LogicalVolumeSize with the -L option (-L 0, for e.g.).
	Man page documentation was specifying incorrect
	range for LogicalVolumeSize in lvcreate, lvextend
	and lvreduce.

	Error message on extending a volume group with a disk
	that is too large was getting mangled with normal
	informative messages. SAM was not able to interpret
	the messages properly.

	vgcreate was not recalculating max_pe properly if
	the -s option was used.

	lvreduce -k was allowing only one pvkey to be selected.

	PHCO_15087:
	lvmtab_read error message added to lvlnboot,lvrmboot,
	pvcreate, vgchgid, vgimport and vgscan commands.
	sleep() is added in vgchgid while creating new vgids ,
	Interrupts are disabled and check for valid no. of PVs
	added. Checks for SCSI disks added when verifying the disks
	in vgchgid,vgimport,vgscan and vgextend commands.

	PHCO_14562:
	The pvmove command does not support physical
	volume groups as a destination path as documented.

	PHCO_14124:
	This patch contains the following hotsite fixes:
	1. PV links don't switch in a shared cluster environment.
	2. Cannot import a cluster aware volume group after
	   migrating to 11.00.  vgimport failed.
	3. EMC provides the option to split a hardware mirror
	   without hpux knowning.  This causes the system to see
	   another set of disks with duplicate VGIDS.  LVM needs
	   to come up with a solution to allow customer import
	   the split-off disk(s) to another system for backup
	   purpose without causing problems.

Defect Description:
	PHCO_24437:
	( SR: 1653162065 CR: JAGaa10504 )
	LVM commands are not designed to have multiple
	command running at the same time.  Incorrect
	information was displayed due to the problem.

	Resolution:
	Fix the lvdisplay command to display more
	meaningful error message.

	( SR: 8606198826 CR: JAGad68015 )
	The lvlnboot command does not pick up the
	correct boot disk information when the boot
	disk order was reversed.

	Resolution:
	The lvlnboot command was modified to pick up the
	refreshed boot disk information.

	( SR: 5003432500 CR: JAGaa52059 )
	LVM only allows 4 digits for displaying the
	number of logical and physical extent(s).

	Resolution:
	Changed the LVM code to now allow 5 digits fields.

	( SR: 8606161148 CR: JAGad30464 )
	The vgimport command only checks the logical volume
	number up to 254.

	Resolution:
	The vgimport command was modified to fix the problem.

	( SR: 8606111918 CR: JAGab84052 )
	vgscan looks for all special files with major number
	0x64 under /dev and assumes that the directory in which
	it is present is a volume group name.

	Resolution:
	The vgscan command is modified to check the group file
	under each volume group directory.

	( SR: 8606199183 CR:JAGad68371 )
	A list of unique Physical Volumes is not properly
	built during lvextend, and it leads to a case where multiple
	entries of a same physical volume could be present list.

	Resolution:
	Added a new check during mapping of logical extents to
	physical extent to verify that no physical extent
	is mapped more than once.

	PHCO_23791:
	(CR: JAGad55191  SR: 8606185986)
	The LVM library code used a C library
	"ungetc" which has a 8k boundary which
	caused problem when the length of the
	ungetted strings is more than 8k.

	Resoultion:
	The LVM library code has been modified
	to fix the problem.

	(CR:JAGad50582 SR:8606181365)
	"Virtual Array" family of disks support splitting a LUN.
	Since this results in a new disk with identical data to the
	original disk, verifying the pvid and vgid information on
	disk is no longer sufficient in determining which links are
	alternate links to a LUN.  This could result in data loss or
	corruption by LVM using what it believes is an alternate
	link to the original LUN when it is actually using a link to
	the new LUN created by the split.

	Resolution:
	"Virtual Array" specific functionality to LVM was added by
	using the array specific LUN id as a unique identifier when
	we are attempting to identify alternate links and disks with
	duplicate LVM metadata.

	PHCO_23499:
	(CR: JAGad46538     SR: 8606177306)
	When a volume group is deactivated and then exported, there
	is a leftover in volgrp structure with the volume group id.
	If the volume group is imported later on with a different
	minor number, there will be two different volgrp structures
	in the array with the same vgid - one is a leftover, another
	one is created at the time of vg activation.

	Resolution:
	Vgexport will Clear the volume group id while exporting
	the volume group.

	(CR: JAGad05245     SR: 8606136115)
	The panic occurred when lv_querylvmap tried to dereference
	(vg->pvols[ext->e_pvnum])->pv_flags on a volume group
	whose vg->pvols was null.

	Resoultion:
	Add attach_pvs() inside vgchange_main() which will call
	notify_clvmd_deactivn() to fail on an exclusively
	activated volume group.

	PHCO_23076:
	(CR: JAGad50461     SR: 8606181244)
	"Virtual Array" family of disks support
	splitting a LUN. Therefore, for determining
	alternate links to a LUN it is not sufficient
	to verify the pvid and vgid information on
	disk from each link because LVM can be easily
	misled in case of split LUNs where the data
	may be same on two links but they are paths
	to two different disks after the split.

	Resoultion :
	Added "Virtual Array" specific functionality to
	LVM, where we identify alternate links and disks
	with duplicate LVM metadata by using the array
	specific unique LUN id.

	PHCO_22839:
	(CR: JAGad38961     SR: 8606169686)
	Currently, LVM commands recognize XP256 and
	XP512 by checking the unique identifier on the
	disk.  Need to modify LVM commands to recognize
	XP48 as part of the XP disk array family.

	Resolution:
	Modify LVM commands to recognize XP disk array
	family by means of product id, instead of using
	the unique identifier on the firmware.

	PHCO_21630:
	(CR: JAGac78496     SR: 8606127694)
	Several problems caused by having the same
	VG appearing in the lvmtab more than once.
	Because LVM commands failed to check if the PVs
	in those VGS are indeed valid, by comparing the
	VGID on the disk and on the lvmtab file.

	Resolution:
	Modified LVM commands to validate each PVs
	in the VG to make sure they belong.

	(CR: JAGad06173     SR: 8606137055)
	Currently, LVM commands recognize XP256
	disk array by checking the product id.  But
	XP512 have a different product id.  Need to
	modify LVM commands to recognize XP512 as well.

	Resolution:
	Modified LVM commands to recognized XP256
	as well as XP512 disk arrays.

	PHCO_21269:
	The LVM command vgchgid only modifies the VGID on EMC
	BCV or EMC RDF2 devices.  Customers need the same
	functionality to support XP256 disks, such that the
	vgchgid command would also modify the VGID on the
	XP256 devices.

	Rssolution:
	Modified the LVM command vgchgid to add new
	functionality to support XP256 disk array.  Other
	LVM commands are also modified in order to support
	both EMC and XP256 devices in the same volume group.

	PHCO_20870:
	(CR: JAGaa46006   SR: 1653288878)
	The maximum number of physical volume which LVM can
	support was used incorrectly in the code.

	(CR: JAGab83482   SR: 8606110734)
	The pvdisplay command failed to report correct
	status when a disk is powerfailed.

	(CR: JAGab83470   SR: 8606110722)
	The vgimport command and vgexport command lack
	of an option which allow users to specify
	device names in a file.

	(CR: JAGad02854  SR: 8606133710)
	The vgreduce command failed to remove any
	unattached physical volume in the lvmtab file.
	And the vgreduce command "-f" option insists that
	all physical volume in the lvmtab are attached.

	(CR: JAGad02856   SR: 8606133712)
	The "autoswitch" option was not implemented on
	the vgdisplay and the pvdisplay command.

	Resolution:
	(CR: JAGaa46006   SR: 1653288878)
	Modified LVM commands to handle maximum physical
	volume configuration.  With the fix in this patch,
	LVM can handle a volume group up to 255 physical
	volumes, and 8 paths (one primary, 7 alternate)
	to each physical volume.

	(CR: JAGab83482   SR: 8606110734)
	Modified the pvdisplay command to report correct
	status when a disk is powerfailed.

	(CR: JAGab83470   SR: 8606110722)
	Add a new option "-f" to the vgimport and vgexport
	command to allow user to specify all devices
	in a file.

	(CR: JAGad02854  SR: 8606133710)
	Add a new option "-l" to the vgreduce command, so
	that the unattached physical volume can be removed
	Modified the vgreduce command "-f" option to remove
	any unattached physical volume in the lvmtab file.

	(CR: JAGad02856   SR: 8606133712)
	Modified the vgdisplay and the pvdisplay command
	to have a display on whether the "autoswitch"
	option is on for each physical volume.

	PHCO_20054:
	1. Modified vgcreate to create VG with disks more
	   than 64K extents correctly.  Only 64K extents
	   from the PV will be used.
	2. Modified vgreduce to not delete /etc/lvmtab
	   entries for a read-only Volume Group.
	3. Modified vgreduce to not delete PV entries from
	   /etc/lvmtab if the PV has extnets in use.
	4. Modified vgremove to not delete the VG if there
	   are more than one entry (multiple links for PV)
	   in the /etc/lvmtab even though the VG contains
	   only one PV.

	PHCO_19631:
	1. Modified vgextend and vgcreate commands to
	   print proper error messages when supplied
	   with character device pathname.
	2. Multiple VxFS products are available on HPUX
	   11.00.  The VxFS product (JFS3.1) installed
	   with 11.00 does not have version 4 filesystem
	   capability. Later VxFS products (JFS3.3) include
	   a version 4 filesystem.  Therefore, libc routines
	   have been updated to identify and verify version
	   4 filesystems. The lvm commands call these
	   modified libc routines.

	   To allow for multiple VxFS versions the following
	   patches are required:
	   PHCO_19491          libc
	   PHCO_18462          diskusg_vxfs
	   PHCO_18463          fscat
	   PHCO_18464          getext
	   PHCO_18465          setext
	   PHCO_18466          vxdump
	   PHCO_18467          vxrestore
	   PHCO_18468          vxupgrade
	   PHCO_18470          df
	   PHCO_18471          fstyp
	   PHCO_18472          fs_wrapper
	   PHCO_18473          mount_wrapper
	   PHCO_19673          fsck_hfs
	   PHCO_19623          mount_hfs
	   PHCO_19624          mount_cdfs
	   PHCO_19656          mkboot

	   Please note that PHCO_19631 can be used without
	   the above patch dependencies if multiple VxFS
	   version support is not required.

	   Resolution:
	   Re-issue lvm commands to use updatad libc routines.

	PHCO_19479:
	1. In lv_queryvg structure, freepxs has been
	   defined as a short.  This caused the vgdisplay
	   command to not show the right number of free
	   extents if it exceeds the 64K (which is what
	   a short can hold).  Modified the total_px and
	   free_px from 'int' to 'ulong_t' and now using
	   free_px to print the number of free extents
	   instead of using lv_queryvg.freepxs
	2. Modified code in lvcreate to allow stripe size
	   of more than 64 K.

	PHCO_19205:
	1. In recover_boot_info() function, to search for
	   alternate paths, for boot, root & swap volumes
	   we use the total number of primary links in VG
	   instead of total number of all links.  Modified
	   the code to use the total number of all links
	   (primary + alternate) in VG to fix BDRA corruption
	2. Added a new check in  vgchange not to activate VG if
	   it is already activated in read-only mode.
	3. Modified lvdisplay to accomodate the 5 digit
	   extent numbers.
	4. Enabled the pvremove command.

	PHCO_18485:
	This patch does not include the pvremove(1M)
	command. PHCO_17453 introduced this new
	functionality mistakenly, and has been recalled.
	The pvremove(1m) command may not be included in
	subsequent patches. Also, please note that if
	pvremove(1M) is reintroduced in the future,
	it may or may not be compatible with the version
	in PHCO_17453. Therefore, HP recommends removing
	PHCO_17453.
	New checks are added to the vgcfgbackup command
	to make sure the information in the lvmrecord
	is correct before backing it up.  Corrections
	are made to the vgextend command to allow user
	create volume group with maximum physical
	extents of 255 * 65535.

	PHCO_17453:
	Enhancements to LVM commands for coexistence with
	the VERITAS Volume Manager (VxVM).  Enhancements
	include:
	1. Introduction of the pvremove command to free
	   disk media from  under the control of LVM.
	2. Enhancements to the pvcreate and vgcfgrestore
	   commands to be VxVM aware.
	Resolution:
	   This is an enhancement for LVM to coexist with VxVM.

	PHCO_18292:
	1. Add new checks in LVM library to make sure
	   all LEs are mapped to unique PEs;  Another
	   new checks are added to check for alternate
	   links in PV to make sure the same PV would
	   not be selected again.
	2. In lvcreate we were not checking for total
	   number of stripes to be less than or equal
	   to total number of PVs in the VG, hence it
	   was possible to create a VG with Stripes
	   more than the total number of PVs in the VG,
	   added a new check to dissallow this.
	3. Earlier the max StripeSize that can be
	   specified was 64 whereas it can go upto 32K
	   since that is the max power of two value that
	   can be stored in a ushort_t.

	PHCO_16851:
	1. The solution is to create a new LVM allocation
	   policy for creating "extent-based mirrored
	   stripes". By reducing the configuration sequence
	   to a single step, the time for the configuration
	   to complete has been reduced from hours to minutes
	   (i.e. for a 50gb logical volume).
	   The new policy is called the distributed allocation
	   policy and is described in the new lvcreate(1M)
	   man page provided with this patch. There are new
	   lvchange(1M) and lvdisplay(1M) man pages also.
	   There is new command line option in both lvcreate
	   and lvchange: -D y. There is a new logical volume
	   flag in the kernel (see dependent kernel patch).
	2. The SG stress suite is unable to shutdown the
	   cluster after 24 hours or so, because LVM leaves
	   clvmd and LVM kernel in an inconsistent state.
	   This patch fixes vgchange to include recovery
	   schemes if that happens and to prevent such a
	   state, in general.
	3. Lvremove fails to remove logical volumes
	   occasionally, because it thinks that the volume
	   is a swap device, when it is not. This is caused
	   by not checking error return and this patch
	   fixes it.

	PHCO_16248:
	The problem of blocking on an not available
	PV and hence causing the called process to hang is
	overcome by converting all the blocking read/write
	operations to non-blocking read/write operations
	and a wrapper is put arround the read/write operations
	to retry a definite number of times. To make
	non-blocking O_NDELAY flag is set while opening the
	raw PVs.

	PHCO_16090:
	The fix for PHCO_15237 prohibits even partial use of
	disks larger than Max_PE_per_PV. The command should
	print a warning message (on stdout) and proceed,
	instead of printing an error message and aborting.

	PHCO_15237:
	lvcreate, lvextend and lvreduce were not performing range
	check for LogicalVolumeSize with the -L option. The man
	pages for these commands were indicating wrong range
	for LogicalVolumeSize.

	The vgcreate/vgextend defect on error message was due to
	an earlier fix that changed a few stderr prints to stdouts.
	Also, on this particular case, after sending error message
	to stderr, vgcreate/vgextend commands needed to fail which
	they were not doing.

	The adjustment of max_pe was not being done by vgcreate
	even if one of -s or -e option was supplied. The correct
	fix is to report failure only if both the options are
	given and the required number of PE's exceed the
	supplied value.

	lvreduce allows reduction of missing PV by specifying the
	pvkey rather than the pvpath but it was accepting a single
	key only. The fix was made such that -k no longer accepts
	any arguments and the pvkey is now derived from the pvpath
	list.

	PHCO_15087:
	lvmtab_read() call did have any error message printed
	if the call was a failure in lvlnboot.c,lvrmboot.c
	pvcreate.c,vgchgid.c, vgimport.c and vgscan.c
	vgchgid generated same vgids if the vgchgid is called in
	a shell srcipt. So added 1 second delay and disabled
	all interrupts. Check for max. no. of Arguments added.
	Check for SCSI disk added when the devices are verified
	for vgchgid,vgscan,vgimport,vgextend commands.

	PHCO_14562:
	Modified pvmove to allow a physical volume group as a
	destination path.

	PHCO_14124:
	1. Implemented a new ioctl to fix the problem of links not
	   switching in a shared cluster environment.
	2. The vgimport failed was caused by a bad checksum on 10.20
	   disks.  Temporary turn off checksum in LVM command for
	   the same reason that kernel has turned off the checksum
	   until a proper versioning mechanism is implemented.
	3. A new command (vgchgid) is created to modify the VGIDs on
	   the split-off EMC Symmetrix disk(s).  LVM commands
	   vgscan, vgextend and vgimport are also modified to
	   support EMC Symmetrix disk(s).

SR:
	1653282301 1653292375 1653325484 5003385989 4701374967
	1653252874 1653252759 1653252734 1653199265 5003320606
	1653196428 5003325340 1653271833 1653264887 4701368670
	5003408633 1653297630 5003429829 1653282301 4701427328
	1653286518 1653288878 8606110734 8606110722 8606133710
	8606133712 8606131752 8606127694 8606137055 8606169686
	8606181244 8606177306 8606136115 8606185986 8606181365
	1653162065 8606198826 5003432500 8606161148 8606111918
	8606199183

Patch Files:
	
	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/lvchange.1m
	/usr/share/man/man1m.Z/lvcreate.1m
	/usr/share/man/man1m.Z/lvdisplay.1m
	/usr/share/man/man1m.Z/lvextend.1m
	/usr/share/man/man1m.Z/lvreduce.1m
	/usr/share/man/man1m.Z/pvcreate.1m
	/usr/share/man/man1m.Z/pvremove.1m
	/usr/share/man/man1m.Z/vgchgid.1m
	/usr/share/man/man1m.Z/vgcreate.1m
	/usr/share/man/man1m.Z/vgexport.1m
	/usr/share/man/man1m.Z/vgextend.1m
	/usr/share/man/man1m.Z/vgimport.1m
	/usr/share/man/man1m.Z/vgreduce.1m
	/usr/share/man/man1m.Z/vgscan.1m

	LVM.LVM-MIRROR-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/newconfig/sbin/lvchange.mir
	/usr/newconfig/usr/sbin/lvchange.mir

	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/lib/nls/msg/C/lvm.cat
	/sbin/lvchange
	/usr/sbin/lvchange

what(1) Output:
	
	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/lib/nls/msg/C/lvm.cat:
		None

	LVM.LVM-MIRROR-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/newconfig/sbin/lvchange.mir:
		$Revision: 80.6 $ $Date: 97/04/28 18:00:45 $
		$Revision: 82.26.1.9.1.111 $ MIRROR PRODUCT
		$ PATCH/11.00:PHCO_19491  Aug  9 1999 09:51:13 $
		PATCH_11_00: lvdisplay.o lvlnboot.o lvremove.o lvrmb
			oot.o pvck.o pvchange.o pvcreate.o pvdisplay
			.o pvmove.o pvremove.o sdstolvm.o vgchgid.o 
			vgcfgbackup.o vgcfgrestore.o vgchange.o vgcr
			eate.o vgdisplay.o vgexport.o vgextend.o vgi
			mport.o vgreduce.o vgremove.o vgscan.o lvcha
			nge_m.o lvcreate_m.o lvextend_m.o lvmerge_m.
			o lvmmain_m.o lvreduce_m.o lvsplit_m.o lvsyn
			c_m.o nomwcsyncd_m.o vgsync_m.o hpux_rel_m.o
			 01/06/25

	LVM.LVM-MIRROR-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/newconfig/usr/sbin/lvchange.mir:
		$Revision: 80.6 $ $Date: 97/04/28 18:00:45 $
		$Revision: 82.26.1.9.1.111 $ MIRROR PRODUCT
		PATCH_11_00: lvdisplay.o lvlnboot.o lvremove.o lvrmb
			oot.o pvck.o pvchange.o pvcreate.o pvdisplay
			.o pvmove.o pvremove.o sdstolvm.o vgchgid.o 
			vgcfgbackup.o vgcfgrestore.o vgchange.o vgcr
			eate.o vgdisplay.o vgexport.o vgextend.o vgi
			mport.o vgreduce.o vgremove.o vgscan.o lvcha
			nge_m.o lvcreate_m.o lvextend_m.o lvmerge_m.
			o lvmmain_m.o lvreduce_m.o lvsplit_m.o lvsyn
			c_m.o nomwcsyncd_m.o vgsync_m.o hpux_rel_m.o
			 01/06/25

	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/sbin/lvchange:
		$Revision: 80.6 $ $Date: 97/04/28 18:00:45 $
		$Revision: 82.26.1.9.1.111 $
		$ PATCH/11.00:PHCO_19491  Aug  9 1999 09:51:13 $
		PATCH_11_00: lvdisplay.o lvlnboot.o lvremove.o lvrmb
			oot.o pvck.o pvchange.o pvcreate.o pvdisplay
			.o pvmove.o pvremove.o sdstolvm.o vgchgid.o 
			vgcfgbackup.o vgcfgrestore.o vgchange.o vgcr
			eate.o vgdisplay.o vgexport.o vgextend.o vgi
			mport.o vgreduce.o vgremove.o vgscan.o lvcha
			nge.o lvcreate.o lvextend.o lvmerge.o lvmmai
			n.o lvreduce.o lvsplit.o lvsync.o nomwcsyncd
			.o vgsync.o hpux_rel.o 01/06/25

	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/sbin/lvchange:
		$Revision: 80.6 $ $Date: 97/04/28 18:00:45 $
		$Revision: 82.26.1.9.1.111 $
		PATCH_11_00: lvdisplay.o lvlnboot.o lvremove.o lvrmb
			oot.o pvck.o pvchange.o pvcreate.o pvdisplay
			.o pvmove.o pvremove.o sdstolvm.o vgchgid.o 
			vgcfgbackup.o vgcfgrestore.o vgchange.o vgcr
			eate.o vgdisplay.o vgexport.o vgextend.o vgi
			mport.o vgreduce.o vgremove.o vgscan.o lvcha
			nge.o lvcreate.o lvextend.o lvmerge.o lvmmai
			n.o lvreduce.o lvsplit.o lvsync.o nomwcsyncd
			.o vgsync.o hpux_rel.o 01/06/25

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/lvchange.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/lvcreate.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/lvdisplay.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/lvextend.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/lvreduce.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/pvcreate.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/pvremove.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/vgchgid.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/vgcreate.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/vgexport.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/vgextend.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/vgimport.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/vgreduce.1m:
		None

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	/usr/share/man/man1m.Z/vgscan.1m:
		None

cksum(1) Output:
	
	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	298175625 44255 /usr/lib/nls/msg/C/lvm.cat

	LVM.LVM-MIRROR-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	2930654971 835584 /usr/newconfig/sbin/lvchange.mir

	LVM.LVM-MIRROR-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	3332309403 561152 /usr/newconfig/usr/sbin/lvchange.mir

	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	3428915975 811008 /sbin/lvchange

	LVM.LVM-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	2921192784 544768 /usr/sbin/lvchange

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	2297888547 6048 /usr/share/man/man1m.Z/lvchange.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	2036144898 6890 /usr/share/man/man1m.Z/lvcreate.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	764326670 4196 /usr/share/man/man1m.Z/lvdisplay.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	1293134496 3400 /usr/share/man/man1m.Z/lvextend.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	1698610205 3433 /usr/share/man/man1m.Z/lvreduce.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	608064438 2713 /usr/share/man/man1m.Z/pvcreate.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	2153149383 1195 /usr/share/man/man1m.Z/pvremove.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	2623980810 2834 /usr/share/man/man1m.Z/vgchgid.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	3197649666 4291 /usr/share/man/man1m.Z/vgcreate.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	3717591610 2695 /usr/share/man/man1m.Z/vgexport.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	649400902 4273 /usr/share/man/man1m.Z/vgextend.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	3376243830 4076 /usr/share/man/man1m.Z/vgimport.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	3890431035 3284 /usr/share/man/man1m.Z/vgreduce.1m

	LVM.LVM-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
	1023382866 3400 /usr/share/man/man1m.Z/vgscan.1m

Patch Conflicts: None

Patch Dependencies:
	s700: 11.00: PHKL_20419
	s800: 11.00: PHKL_20419

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHCO_14124 PHCO_14562 PHCO_15087 PHCO_15237 PHCO_16090 PHCO_16248
	PHCO_16851 PHCO_18292 PHCO_17453 PHCO_18485 PHCO_19205 PHCO_19479
	PHCO_19631 PHCO_20054 PHCO_20870 PHCO_21269 PHCO_21630 PHCO_22839
	PHCO_23076 PHCO_23499 PHCO_23791

Equivalent Patches: None

Patch Package Size: 00 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_24437

	5. Run swinstall to install the patch:

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

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

		swinstall -x autoreboot=true -x patch_match_target=true \
			  -x patch_save_files=false -s /tmp/PHCO_24437.depot

	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 PHCO_24437.text file is 
	available in the product readme:

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

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

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

Special Installation Instructions: None

