PHCO_35313 s700_800 11.11 LVM関連コマンド累積パッチ

パッチ名:   PHCO_35313

パッチ摘要: s700_800 11.11 LVM関連コマンド累積パッチ

作成日:  06/09/16

公開日:  06/10/27

再発行:  07/01/04
	 "現象"/"問題点の説明"セクションでのサービス要求8606449890(JAGag07004)
	 と8606449884(JAGag07000)の参照が逆になっていました。正しいサービス要
	 求を参照するように各セクションを修正しました。

警告: 07/02/13 - これは、当社からの警告(Non-Criticalレベル)です。

	- オプションのMirrorDisk/UXソフトウェアがインストールされていないシス
	  テムにPHCO_35313をインストールすると、lvextend(1M)コマンドが異常終了
	  することがあります。この場合、次のようなエラーメッセージが表示されま
	  す。

	    Usage: lvextend
		    [-A Autobackup]
		    {-l LogicalExtentsNumber |
		      -L LogicalVolumeSize}
		    LogicalVolumePath [ PhysicalVolumePath... |
	    PhysicalVolumeGroupName... ]
	    Program error. Bad usage of options handling routines.

	- この問題の詳細は、サービス要求8606473680(JAGag28309)を参照してくださ
	  い。

	- MirrorDisk/UXソフトウェアは、スタンドアロン製品B2491BA/B5403BAだけで
	  なくHP-UX EnterpriseとHP-UX Mission Critical Operating Environments
	  にも含まれています。次のコマンドを使って、MirrorDisk/UXがシステムに
	  インストールされているか調べることができます。

	    swlist -l fileset LVM.LVM-MIRROR-RUN

	- この問題を回避するために、以下のいずれかのアクションを取るようお勧め
	  します。

	    - MirrorDisk/UXをインストールしていないシステムの場合は、
	      PHCO_35313を削除する。

	    - PHCO_35313が提供する機能が必要な場合は、MirrorDisk/UXをインスト
	      ールする。ただし、PHCO_35313のMirrorDisk/UXコンポーネントが確実
	      にインストールされるように、MirrorDisk/UXのインストール後、再度
	      PHCO_35313をインストールする必要があります。

	- 以前のパッチPHCO_34196では、この問題は起きません。したがって、
	  PHCO_35313を削除する場合は、その他の既知の問題をできるだけ多く解決す
	  るために、PHCO_35313の削除後PHCO_34196をインストールするようお勧めし
	  ます。ただし、PHCO_34196がPHCO_35313より前にインストールされている場
	  合は、PHCO_35313を削除すればPHCO_34196が自動的に復元されるので、再イ
	  ンストールする必要はありません。

ハードウェアプラットフォームおよびOSリリース:

	s700: 11.11
	s800: 11.11

現象:

	PHCO_35313:

	1. (SR:8606449884 CR:JAGag07000)
	"vgcfgrestore -n <VG> -l"コマンドがデバイス特殊ファイル名を18文字で切
	り捨てます。

	2. (SR:8606449890 CR:JAGag07004)
	"pvdisplay -b"コマンドが論理ボリューム名を18文字で切り捨てます。

	3. (SR:8606449888 CR:JAGag07002)
	表示するボリュームグループ数が調整可能なシステムパラメータ"maxfiles"の
	値を超えると、vgdisplayコマンドが次のようなエラーメッセージを表示しま
	す。

		"cannot open the control file"

	4. (SR:8606430256 CR:JAGaf89715)
	物理ボリューム上のLVMメタデータが矛盾していると、"vgreduce -f"コマンド
	でコアダンプが取られます。

	5. (SR:8606442543 CR:JAGag00293)
	/etc/lvmtabファイルの再作成時に、vgscanコマンドが、"vgreduce -f"コマン
	ドを使って縮小したボリュームグループをスキップします。

	6. (SR:8606457243 CR:JAGag13572)
	機能拡張: lvsyncコマンドが、無効な論理ボリュームの同期をシリアルに行い
	ます。そのため、全入力論理ボリュームの同期にかかる時間は、各論理ボリュ
	ームの同期にかかる時間の和(累積時間)になります。この累積時間を短縮する
	必要があります。

	7. (SR:8606430833 CR:JAGaf90290)
	pvcreate(-fオプションなし)/vgcfgrestoreコマンドが不正に、Oracle ASMデ
	ィスクグループに属している物理ボリュームをLVMメタデータ情報で上書きし
	ます。

	8. (SR:8606456785 CR:JAGag13166)
	LVM関連コマンドには、物理ボリュームがLVMの制御下にあるかどうかチェック
	するオプションがありません。

	9. (SR:8606422021 CR:JAGaf81846)
	PVG厳密(PVG-strict)および分散(distributed)割り当て方針を設定して論理ボ
	リュームを作成すると、論理ボリュームのミラーコピーが同じ物理ボリューム
	グループを共有することがあります。この問題が起きるのは、/etc/lvmpvgフ
	ァイル内に代替リンクがリストされている場合だけです。

	10.(SR:8606397355 CR:JAGaf57337)
	LVM不正ブロック再配置機能は、カーネルパッチPHKL_29979で変更されていま
	す。ところが、これらの変更がマニュアルページに反映されていません。

	11.(SR:8606444829 CR:JAGag02362)
	vgimport(1M)のマニュアルページに、「"-s"オプションは"-p"または"-v"オプ
	ションと一緒に使用する必要がある。」という記述があります。しかし、"-p"
	オプション(プレビューモード)を使用すると、vgimportコマンドはボリューム
	グループのインポート操作を行いません。

	12.(SR:8606443239 CR:JAGag00913)
	lvcreate(1M)、lvdisplay(1M)、lvchange(1M)、vgdisplay(1M)および
	vgchange(1M)のマニュアルページでの論理ボリュームの状態(特に、ミラー一
	貫性回復がオフ(NONE))の場合)に関する説明が不正確です。

問題点の説明:
 
	PHCO_35313:

	1. (SR:8606449884 CR:JAGag07000)
	デバイス特殊ファイル名を表示するためのフィールド幅を18に設定していまし
	た。

	解決方法:
	出力時にデバイス特殊ファイル名を18文字で切り捨てないようにvgcfgrestore
	コマンドを修正しました。

	2. (SR:8606449890 CR:JAGag07004)
	論理ボリューム名を表示するためのフィールド幅を8に設定していました。

	解決方法:
	出力時に論理ボリューム名を8文字で切り捨てないようにpvdisplayコマンドを
	修正しました。

	3. (SR:8606449888 CR:JAGag07002)
	vgdisplayコマンドは、ボリュームグループのファイル記述子を使用後クロー
	ズしていませんでした。そのため、表示するボリュームグループ数が調整可能
	パラメータ"maxfiles"の値を超えると、open(2)がエラーになっていました。

	解決方法:
	各ボリュームグループの表示後、そのファイル記述子をクローズするように
	vgdisplayコマンドを修正しました。これで、ファイル記述子が使い果される
	ことはありません。

	4. (SR:8606430256 CR:JAGaf89715)
	物理ボリューム上のLVMメタデータが矛盾していると、"vgreduce -f"コマンド
	は、ボリュームグループ情報の最新のコピーを特定できませんでした。その結
	果、コアダンプが取られていました。

	解決方法:
	LVMメタデータを読み取らないようにvgreduceコマンドを修正しました。これ
	で、LVMメタデータが矛盾していても、コアダンプが取られることはありませ
	ん。

	5. (SR:8606442543 CR:JAGag00293)
	vgscanコマンドは、"vgreduce -f"を使って縮小したボリュームグループに属
	する物理ボリューム数を正しく計算していませんでした。そのため、vgscanコ
	マンドはそのようなボリュームグループをスキップしていました。

	解決方法:
	"vgreduce -f"を使って縮小したボリュームグループ内の物理ボリューム数を
	正しく計算するようにvgscanコマンドを修正しました。

	6. (SR:8606457243 CR:JAGag13572)
	機能拡張: lvmerge/"lvextend -m"コマンドの結果として生じる無効なエクス
	テントの自動再同期を防ぐ方法がありませんでした。しかし、多くの同期操作
	を行う必要がある場合、これでは不都合が生じます。一方、lvsyncコマンドの
	場合、引き数として複数の論理ボリュームを指定すると、各論理ボリュームの
	同期はシリアルに行われます。そのため、全入力論理ボリュームの同期にかか
	る時間は、各論理ボリュームの同期にかかる時間の和(累積時間)になります。
	コマンド行引き数として多数の論理ボリュームを指定する場合、これは好まし
	くありません。

	解決方法:
	論理ボリュームの無効なエクステントを同期せずに処理を完了させる新たなコ
	マンド行オプション"-s"をlvmerge/lvextendコマンドに追加しました。それで
	も同期は必要ですが、lvsyncコマンドを使って手動で同期を行うことができま
	す。ボリュームグループ内の論理ボリュームの再同期をパラレルに行わせる新
	たなコマンド行オプション"-T"をlvsyncコマンドに追加しました。これで、
	ほとんどの場合、無効なエクステントの同期に必要な時間は短縮されます。

	7. (SR:8606430833 CR:JAGaf90290)
	pvcreate/vgcfgrestoreコマンドは、指定した物理ボリュームがOracle ASMの
	制御下にあるかどうかチェックしていませんでした。そのため、物理ボリュー
	ムをLVMメタデータ情報で上書きしていました。

	解決方法:
	物理ボリュームがOracle ASMの制御下にあるかどうかチェックし、Oracle ASM
	の制御下にある場合は、物理ボリュームをLVMメタデータ情報で上書きしない
	ようにpvcreate/vgcfgrestoreコマンドを修正しました。

	8. (SR:8606456785 CR:JAGag13166)
	指定した物理ボリュームがLVMの制御下にあるかどうかチェックできるLVM関連
	コマンドがありませんでした。

	解決方法:
	指定した物理ボリュームLVMの制御下にあるかどうかチェックする新たなオプ
	ション"-l"をpvdisplayコマンドに追加しました。

	9. (SR:8606422021 CR:JAGaf81846)
	論理ボリュームのミラーコピーを拡張する場合、PVG厳密(PVG-strict)割り当
	て方針のチェック時に代替リンクを考慮していませんでした。

	解決方法:
	PVG厳密割り当て方針が設定され、PVG内に代替リンクだけしか存在しない場合
	は、新たなミラーコピーを同じPVG内に割り当てないようにコードを修正しま
	した。

	10.(SR:8606397355 CR:JAGaf57337)
	PHKL_29979での変更がlvchange(1M)/lvcreate(1M)のマニュアルページに反映
	されていませんでした。

	解決方法:
	PHKL_29979での変更を反映するようにlvchange(1M)/lvcreate(1M)のマニュア
	ルページを修正しました。

	11.(SR:8606444829 CR:JAGag02362)
	vgimport(1M)のマニュアルページには、"-s"オプションに関する不正な記述が
	ありました。"-s"オプションは、必ずしも"-p"オプションや"-v"オプションと
	一緒に使用する必要はありません。正しくは、「"-s"オプションは、"-p"オプ
	ションや"-v"オプションと一緒に使用することもできます。」です。ただし、
	"-p"(プレビューモード)オプションを使用すると、vgimport操作は行われませ
	ん。

	解決方法:
	vgimport(1M)のマニュアルページでの"-s"オプションに関する記述を次のよう
	に修正しました。

	「"-s"オプションは、"-p"オプションや"-v"オプションと一緒に使用すること
	もできます。」

	12.(SR:8606443239 CR:JAGag00913)
	lvcreate(1M)、lvdisplay(1M)、lvchange(1M)、vgdisplay(1M)および
	vgchange(1M)のマニュアルページでのミラー一貫性回復がオフ(NONE)の論理ボ
	リュームに関する説明は不正確でした。

	解決方法:
	論理ボリュームの可能な状態について正しく説明するようにlvcreate(1M)、
	lvdisplay(1M)、lvchange(1M)、vgdisplay(1M)およびvgchange(1M)のマニュア
	ルページを修正しました。また、ミラー一貫性回復がオフ(NONE)の論理ボリュ
	ームを使用してはいけないケースについての説明をマニュアルページに追加し
	ました。これで、これらのマニュアルページでの論理ボリュームの可能な状態
	に関する説明は、LVMカーネルパッチPHKL_32095またはそれ以降のリビジョン
	を適用したシステムでのこれらのコマンドの実際の動作と完全に一致します。
	この結果、それより前のバージョンのLVMカーネルパッチを適用したシステム
	でのこれらのコマンドの動作は、マニュアルページでの説明とは必ずしも一致
	しませんが、従来どおり正常に動作することに変わりはありません。

-----------------------------------------------------------------------------
Patch Name: PHCO_35313

Patch Description: s700_800 11.11 LVM commands cumulative patch

Creation Date: 06/09/16

Post Date: 06/10/27

Repost: 07/01/04
	The references for Service Request 8606449890 (JAGag07004)
	and 8606449884 (JAGag07000) were inverted in the Symptoms
	and Defect Description sections.  The references have been
	inverted so they now head the correct Service Request
	sections.

Warning: 07/02/13 - This Non-Critical Warning has been issued by HP.

	- PHCO_35313 introduced behavior that can cause the
	  lvextend(1M) command to fail if the optional MirrorDisk/UX
	  software is not installed.  When this behavior occurs, the
	  lvextend(1M) command will fail with a message similar to the
	  following:

	    Usage: lvextend
		    [-A Autobackup]
		    {-l LogicalExtentsNumber |
		      -L LogicalVolumeSize}
		    LogicalVolumePath [ PhysicalVolumePath... |
	    PhysicalVolumeGroupName... ]
	    Program error. Bad usage of options handling routines.

	- Additional details on this behavior may be found in Service
	  Request 8606473680 (JAGag28309).
	- The MirrorDisk/UX software is included in the HP-UX
	  Enterprise and HP-UX Mission Critical Operating Environments,
	  as well as standalone products B2491BA and B5403BA.  The
	  following command can be used to determine if MirrorDisk/UX
	  is installed:

	    swlist -l fileset LVM.LVM-MIRROR-RUN

	- To avoid this behavior, HP recommends the either of the
	  following approaches:

	    - Remove PHCO_35313 from systems on which MirrorDisk/UX
	      is not installed.

	    - Install MirrorDisk/UX, if the functionality provided by
	      PHCO_35313 is required.  Please note, that PHCO_35313
	      will need to be installed again after MirrorDisk/UX is
	      installed to ensure the MirrorDisk/UX component of
	      PHCO_35313 is installed.

	- The previous patch, PHCO_34196, does not exhibit this same
	  behavior.  If you choose to remove PHCO_35313, HP recommends
	  that PHCO_34196 be installed after PHCO_35313 is removed to
	  ensure as many known issues as possible are addressed.  If
	  PHCO_34196 was installed prior to PHCO_35313, it will
	  automatically restored when PHCO_35313 is removed and will
	  not need to be reinstalled.

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

Products: N/A

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

Automatic Reboot?: No

Status: General Release With Warnings

Critical: 
	Yes
	PHCO_35313: ABORT
	        ( SR:8606430256 CR:JAGaf89715 )
		"vgreduce -f" command dumps core if the LVM metadata
		on the physical volumes is inconsistent.
	PHCO_30698: CORRUPTION ABORT
	PHCO_29379: ABORT PANIC CORRUPTION HANG
	PHCO_27913: ABORT PANIC
	PHCO_27408: ABORT
		This fixes a problem in the vgimport(1M) command
		which results in a core dump.
	PHCO_24809: ABORT
	PHCO_23333: CORRUPTION

Category Tags: 
	defect_repair hardware_enablement enhancement
	general_release critical panic halts_system corruption
	manual_dependencies

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

Symptoms: 
	PHCO_35313:
	( SR:8606449884 CR:JAGag07000 )
	"vgcfgrestore -n <VG> -l" command truncates the device
	special file name, if its length is more than 18 characters
	long.

	( SR:8606449890 CR:JAGag07004 )
	"pvdisplay -b" command truncates logical volume names which
	are more than 8 characters long.

	( SR:8606449888 CR:JAGag07002 )
	vgdisplay command fails with the below message, if the
	number of volume groups to display is larger than the
	system tunable "maxfiles".
		"cannot open the control file"

	( SR:8606430256 CR:JAGaf89715 )
	"vgreduce -f" command dumps core, if the LVM metadata on the
	physical volumes is inconsistent.

	( SR:8606442543 CR:JAGag00293 )
	While re-creating the /etc/lvmtab file vgscan command skips
	volume groups which have been reduced using "vgreduce -f"
	command.

	( SR:8606457243 CR:JAGag13572 )
	Enhancement: lvsync command synchronizes stale logical
	volumes serially. As a result, the time taken for lvsync
	command to perform synchronization of all the input logical
	volumes is the cumulative time for synchronizing each
	logical volume. This cumulative time taken for
	synchronization of logical volumes using lvsync command
	needs to be reduced.

	( SR:8606430833 CR:JAGaf90290 )
	Although they are not supposed to, pvcreate command
	(without -f option) and vgcfgrestore command operations
	succeed on a physical volume, which is already part of
	Oracle ASM diskgroup.

	( SR:8606456785 CR:JAGag13166 )
	LVM commands do not have an option to check whether
	a physical volume is under LVM control.

	( SR:8606422021 CR:JAGaf81846 )
	When a logical volume is created with PVG-strict and
	distributed allocation policy set, then the mirror copy of
	the logical volume may share the same physical volume group.
	This happens only when alternate links are listed in
	/etc/lvmpvg file.

	( SR:8606397355 CR:JAGaf57337 )
	Modifications to the LVM bad block relocation functionality
	were delivered with the kernel patch PHKL_29979. These
	changes in behavior must be appropriately documented.

	( SR:8606444829 CR:JAGag02362 )
	As per vgimport(1M) manual page, "-p" and "-v" options are
	must along with "-s" option. Volume group import action
	never takes place whenever vgimport command is invoked
	with "-p" option (preview mode).

	( SR:8606443239 CR:JAGag00913 )
	Inaccurate details in the lvcreate(1M), lvdisplay(1M),
	lvchange(1M), vgdisplay(1M) and vgchange(1M) manual pages
	for the states of logical volumes, particularly those that
	have mirror consistency recovery turned off (NONE).

	PHCO_34196:
	( SR:8606401135 CR:JAGaf61084 )
	If lvcreate(1M) is invoked where the size of the requested
	logical volume is smaller than the physical extent size
	then lvcreate(1M) will fail with the following error
	message.

	lvcreate: Specified LogicalVolumeSize is too large for the
	PhysicalExtentSize of the Volume Group. Resulting number
	of extents is out of the range 1 to 65535 (0).

	( SR:8606404441 CR:JAGaf64363 )
	During a normal mode boot there may be an unnecessary
	re-synchronization of the extents on a mirrored root
	logical volume only under circumstances such as, when
	the following actions have been performed:
	- the physical volume containing a mirrored root logical
	  volume is detached from the volume group
	- a vgcfgrestore(1M) is invoked on the physical volume
	- the physical volume is reattached to the volume group
	- system is rebooted

	( SR:8606426930 CR:JAGaf86411 )
	On HP-UX 11i v1, LVM commands do not support
	internationalization (I18N).  Therefore error and status
	message output from LVM commands will be in English
	only.

	( SR:8606399194 CR:JAGaf59159 )
	Logical volume timeout value is wrong when activating a
	volume group in shared mode with consistency recovery set
	to NOMWC for the volume group.

	( SR:8606383951 CR:JAGaf44142 )
	A subset of LVM commands (vgextend(1M), vgreduce(1M),
	lvremove(1M), lvextend(1M), lvreduce(1M), pvmove(1M),
	lvmerge(1M) and lvsplit(1M)) that support autobackup
	(-A option) when invoked with autobackup turned off, may
	generate the warning message as below.

	lvlnboot: Warning: couldn't query physical volume
	"/dev/dsk/c25t3d0": The specified path does not
	correspond to physical volume attached to this volume
	group

	( SR:8606430676 CR:JAGaf90134 )
	If a logical volume having the PVG-strict policy is reduced
	in size (number of extents) using lvreduce(1M), then a
	subsequent attempt to add a mirror ("lvextend -m 1") will
	fail with an error indicating that there is not enough space
	even when there are enough physical extents to create the
	mirror. The error message looks like the one below.

	lvextend: Not enough free physical extents available.
	Logical volume "/dev/vgrag/lvol1" could not be extended.
	Failure possibly caused by PVG-Strict allocation policy.

	PHCO_34061:
	( SR:8606400428 CR:JAGaf60383 )
	vgchange(1M) fails to activate the volume group in shared
	mode with an incorrect random error message. Also, vgchange
	exits with 0 instead of 1 as a result of which, user
	scripts relying on the exit value might be misled.

	( SR:8606400434 CR:JAGaf60389 )
	vgchange(1M) fails to activate the volume group in shared
	mode with an incorrect random error message. Also, vgchange
	exits with 0 instead of 1 as a result of which, user
	scripts relying on the exit value might be misled. Only
	a system reboot will be able to rectify the problem.

	( SR:8606397510 CR:JAGaf57492 )
	lvmerge(1M) fails with an error message similar to:
	"Couldn't delete logical volume "/dev/vg01/lvol6b".
	The corresponding split logical volume doesn't get removed
	from the system. In addition, lvmerge(1M) exits with 0
	instead of 1 as a result of which, user scripts relying on
	the exit value might be misled.

	( SR:8606397515 CR:JAGaf57497 )
	On systems with more than 8160 physical volumes,
	vgimport(1M) and vgscan(1M) fail with the following error
	message.
	"Unable to scan Physical Volumes on system"

	PHCO_33310:
	( SR:8606364202 CR:JAGaf24856 )
	It is not possible to make configuration changes to an
	active LVM volume group in a shared environment without
	deactivating the volume group on all Serviceguard cluster
	nodes.

	( SR:8606405595 CR:JAGaf65516 )
	Some of the error messages displayed by LVM commands are
	incorrect when NLS(Native Language Support) settings are
	used.

	( SR:8606410321 CR:JAGaf70203 )
	On a system installed with PHCO_24809 or any of its
	superseding patches, and when files with sizes larger than
	MAX_SMALL_FILE (2147483647) exist under the /dev directory,
	vgcreate(1M), vgimport(1M) and vgscan(1M) might fail with
	error messages as shown below.

	vgcreate(1M) and vgimport(1M) logs message similar to:
	"Minor number of /dev/xxx/xxx is not unique. /dev/xxx/xxx
	has the same minor number".

	and vgscan(1M) logs messages similar to:
	"Error getting path name of volume group with group file
	minor number 0x0.
	Value too large to be stored in data type".

	PHCO_30698:
	( SR:8606358733 CR:JAGaf19429 )
	Enhancement: Pre-enable LVM to replace disks containing
	mirrored logical volumes in shared volume groups on
	Serviceguard clusters without deactivating the volume group
	and without remapping the data on the disk.

	( SR:8606358753 CR:JAGaf19449 )
	Enhancement: Pre-enable LVM support for online replacement
	of disks.

	There is no way to cause LVM to stop using a disk that fails
	inconsistently (some i/o requests succeed but most do not).

	Since mirrored write requests must be issued to all the
	copies of the data, performance overall is dramatically
	affected if even one copy performs badly.

	( SR:8606358764 CR:JAGaf19460 )
	Enhancement: Pre-enable LVM support for online replacement
	of disks.

	There is no way to cause LVM to disable faulty/unstable
	paths or disks, or to stop sending i/o to the device.  This
	ability would enable support personnel to maintain peak
	system filesystem performance until such time that the
	faulty or unstable device can be replaced.

	LVM Online replacement provides a way to replace disks
	containing mirrored logical volumes in shared volume groups
	in ServiceGuard OPS clusters without deactivating the volume
	group and without remapping the data on the disk.

	( SR:8606322717 CR:JAGae85184 )
	Some disk arrays and other advanced devices may perform
	operations that may hold off i/o directed to the device for
	as much as 10 minutes.  However, the lvchange(1M) command
	will not allow setting a logical volume timeout value
	greater than 300 seconds (5 minutes).  Presently, the
	choices are either infinite (default) or a value in the
	range of 2-300 seconds.  Consequently, it is possible that
	i/o errors may result from LVM failing back i/o directed to
	these devices because they have been delayed too long.

	( SR:8606350908 CR:JAGaf11720 )
	Running any LVM configuration commands along with the
	"vgimport -s" command could leave the lvmtab corrupted.
	The corruption can have many forms, but most notably
	displaying the volume groups using vgdisplay(1M) after
	running commands with "vgimport -s" might indicate too many
	or few physical volumes (PVs) or other unexpected
	inconsistencies.

	( SR:8606350664 CR:JAGaf11476 )
	The vgchgid(1M) command core dumps if the number of PVs
	given in the command line exceeds 255.

	PHCO_29379:
	( SR:8606217852 CR:JAGad87002 )
	During system startup Volume Group activation, failure error
	messages can be seen when VGs  comprising of iSCSI  Physical
	Volumes  are  present.  System   hangs  may  also  be  seen.
	Hardware  Enablement:  This product  update is a member of a
	set needed to enable the optional iSCSI support in LVM.  The
	full list of product updates  required for this feature are:
	PHKL_30552 and PHCO_29379.

	( SR:8606279722 CR:JAGae43711 )
	In certain  cases,  installation  of an LVM  commands  patch
	could cause error  messages  similar to the following in the
	installation log files.

	ERROR:   The    swmodify    command    failed    for
	    PHCO_23333.LVM-RUN,l=/,r=1.0,a=HP-UX_B.11.11_32/64,v=HP.
	      The configuration process will proceed.
	ERROR:   Rebuilding the Installed Products Database
	      has failed.  You may  need to retry   this operation.

	( SR:8606305556 CR:JAGae68604 )
	I/O errors may be seen while executing the  vgcfgrestore(1M)
	command on a disk which is smaller than the original disk.

	( SR:8606305780 CR:JAGae68828 )
	Upon activation of a VG with several  mirrored lvols, when a
	synchronization  failure occurs on an lvol, vgsync(1M) fails
	to continue  synchronizing  the  remaining  lvols beyond the
	first failure encountered.

	( SR:8606305784 CR:JAGae68832 )
	On a  system  with  PHCO_24809  or  any  superseding  patch,
	running the lvlnboot(1M)  command with -b, -r, -s or -d on a
	bootable  volume  group on a  configuration  with  alternate
	links can cause  corruption.  This  corruption  can  cause a
	panic when  booting  from the  affected  volume  group  with
	messages similar to the following:

	  Logical volume 64, 0x3 configured as ROOT
	  LVM : Failure in attaching PV (8/8.1.0) to the root volume
	  group.
	  Cross device link.  The disk is not a LVM disk.
	  LVM : Failure in attaching PV (8/4.1.0) to the root volume
	  group.
	  Cross device link.  The disk is not a LVM disk.
	  LVM : Activation of root volume group failed
	  Either no physical volumes are attached or no valid VGDAs
	    were found on the physical volumes.
	  Quorum not present, or some physical volume(s) are missing
	  ---------------------------------------------------
	  |       SYSTEM HALTING during LVM Configuration   |
	  |                                                 |
	  |            Could not configure root VG          |
	  ---------------------------------------------------
	  panic: LVM: Configuration failure

	( SR:8606305787 CR:JAGae68835 )
	In  certain  situations,  vgimport(1M)  fails to import  the
	volume group and returns with the error  message - vgimport:
	Unable to read the physical volume.

	( SR:8606315175 CR:JAGae77907 )
	PHCO_24809  introduced behavior that can result in incorrect
	physical  volume  information  to remain in the  /etc/lvmtab
	file when  vgcreate(1M) or vgextend(1M) is invoked with more
	than one physical volume.
	For example, the following message can be displayed:

	vgextend: Physical volume "PV2" could not be deleted from
	  the "/etc/lvmtab" file.
	There is now an inconsistency between the LVM device driver
	  and the "/etc/lvmtab" file.
	vgextend: Couldn't install the physical volume "PV2".
	  Too many links

	( SR:8606315178 CR:JAGae77910 )
	If the size of a  physical  volume is less  than the size of
	one  physical   extent  (as  specified  in  a   vgcreate(1M)
	command), then LVM can exhibit incorrect behavior.  One such
	problem is that an LVM daemon will endlessly  loop, using up
	CPU.

	( SR:8606315186 CR:JAGae77918 )
	The lvlnboot(1M)  command gives a misleading message when it
	cannot get root configuration.  The message displayed is:

	"Could  find  the  root lv  related  information  to  create
	/stand/rootconf  file."
	This  message  should be "Could not find..."

	( SR:8606316260 CR:JAGae78977 )
	If any  duplicate  pv  path  entries  are  provided  to  the
	vgimport(1M) command, no errors are reported and the command
	silently fails to complete.

	( SR:8606320951 CR:JAGae83433 )
	If a Volume Group has greater than 256 Physical Volumes
	(including alternate links), then vgscan(1M) fails with
	a meaningless message. For eg. vgscan(1M) on /dev/vg01
	returns -
	vgscan: H
	Oe_
	   o
	   o has no corresponding valid raw device file under
	/dev/rdsk.
	Verification of unique LVM disk id on each disk in the
	volume group /dev/vg01 failed.

	( SR:8606344120 CR:JAGaf04972 )
	vgcfgrestore(1M) can fail on a Physical Volume which is part
	of a currently  active Volume  Group,  even when the path to
	the  Physical  Volume  and the  configuration  file used for
	restore are correct.

	( SR:8606323332 CR:JAGae85797 )
	Exporting or creating  (through the use of  vgexport(1M)  or
	vgcreate(1M) respectively) an LVM volume group can result in
	system panic at execution of  subsequent  LVM  commands  The
	stack trace is as follows -

	lock_write+0x14
	lv_close+0x78
	call_open_close+0x274
	closed+0xb0
	spec_close+0x54
	vn_close+0x48
	vno_close+0x20
	closef+0x64
	exit+0x1128
	rexit+0x28
	syscall+0x6f8
	syscallinit+0x54c

	( SR:8606352319 CR:JAGaf13124 )
	The vgcreate(1M) and vgextend (1M)commands expect properly
	formatted PVs as parameters.  PVs are formatted using
	pvcreate(1M).  If a PV which is not properly formatted is
	passed to vgcreate(1M) or vgextend(1M), then the behavior
	will vary depending on the data on the PV.

	If a PV which has not been formatted with pvcreate(1M) is
	passed to vgcreate(1M) or vgextend(1M) then the command will
	abort with an I/O error.  If a PV which has been formatted
	is unformatted with pvremove(1M) and then passed to
	vgcreate(1M) or vgextend(1M), then the PV will be skipped
	and any other PVs specified will be added to the VG.

	This behavior should not be inconsistent.  Also, an
	unformatted PV should be treated the same a an unavailable
	PV.  On finding that a PV is unformatted the command should
	abort with an appropriate error message

	PHCO_27913:
	( SR:8606255308 CR:JAGae19635 )
	When non unique minor numbers exist on the system, the
	vgimport(1M) command prints out one of the following
	messages:
	"Minor number of ___ is not unique. ___ has the same minor
	number."
	"Minor number of ___ is not unique. Conflicts with other
	volume group file."
	Instead of aborting, the vgimport(1M) command will
	incorrectly continue the import.  This will make one of the
	volume groups inaccessible, and the user may have to reboot
	and reassign a unique minor number to the volume group in
	order to access both volume groups.

	( SR:8606198887 CR:JAGad68076 )
	When the vgchange(1M) command is used to activate a non-
	shared volume group which contains a disk previously used
	in a shared volume group, the volume group activation may
	fail.  The following message may be displayed:
	vgchange: Activation mode requested for the volume group
	"/dev/vgtest" conflicts with configured mode.

	The following scenario can lead to the problem:
	        - A disk was used in a shared volume group.
	        - The same disk is reused in a non-shared volume
	group through the vgcreate(1M) command.
	        - The volume group is deactivated.
	        - The volume group is reactivated.

	( SR:8606199556 CR:JAGad68743 )
	When the lvremove(1M) command removes a logical volume in
	the root volume group, the following stack trace can result
	after a system panic:

	> panic+0x6c
	> report_trap_or_int_and_panic+0x94
	> trap+0xf48
	> nokgdb+0x8
	> lv_rw_one_mirror+0xc0
	> lv_schedule1+0x10c
	> lv_schedule+0x60
	> lv_initiate+0x158
	> lv_strategy+0x298
	> lv_syncio+0xbc
	> lif_locate+0x130
	> lv_readlabel+0xbc
	> lv_getpdisc+0xa4
	> lv_lvswapmaint+0x78
	> lv_swap_to_dump+0x60
	> swap_to_dump+0x5c
	> dumpconf+0x164
	> DoCalllist+0x3c
	> main+0x28

	( SR:8606223480 CR:JAGad92577 )
	The vgscan(1M) command will not work correctly if vg00 does
	not appear first in /etc/lvmtab.  If the user attempts to
	recreate the lvmtab with a vgscan, vg00 and all of the
	physical volumes associated with it will not be placed in
	the lvmtab.

	( SR:8606266304 CR:JAGae30553 )
	When lvlnboot(1M) is executed, the command may cause data
	corruption if a disk is missing or has failed.  The wrong
	disk may also be marked as missing.  These problems can
	only occur when one or more disks in an activated volume
	group are missing or have failed.

	( SR:8606235481 CR:JAGae04635 )
	The vgcfgbackup(1M) and pvremove(1M) commands may not
	return errors when there are partial failures of reads and
	writes.

	( SR:8606230792 CR:JAGae00030 )
	The vgchgid(1M) command can corrupt the Boot Data Reserved
	Area (BDRA), making the system unable to boot (except in
	maintenance mode).  When lvlnboot(1M) is executed from
	maintenance mode, a flag is cleared which prevents LVM from
	recognizing the previous maintenance mode boot.  This
	creates different data on mirrored copies, leading to
	silent data corruption in the root filesystem.

	( SR:8606251163 CR:JAGae17229 )
	Currently the vgremove(1M) command incorrectly allows a
	clustered volume group to be removed.  This can lead to
	problems whose symptoms may include:
	        - The inability to halt the cluster software. The
	command cmhaltcl(1M) will fail.

	        - The inability to deactivate an unrelated volume
	group which may have been created at a later time. This
	volume group may appear to be activated in exclusive mode.

	( SR:8606226992 CR:JAGad96054 )
	The lvcreate(1M) command will core dump and create an lvol
	of size 0 when too large of a size is specified with the -L
	argument.   The maximum size is determined by the extent
	size * number of extents (default 65535).

	PHCO_27408:
	( SR:8606251225 CR:JAGae17291 )
	This product update provides LVM support for the VA7405 and
	VA7410 disk arrays.  Without this product update, there is a
	potential risk of data corruption when these disk arrays are
	used with LVM.

	( SR:8606247046 CR:JAGae13486 )
	The vgimport(1M) command may core dump when the number of
	physical volumes specified on the command line is less than
	the total number of physical volumes in the volume group.
	This happens with all of the LVM commands patches between
	PHCO_24809 and PHCO_25814.

	PHCO_27099:
	( SR:8606262676 CR:JAGae27007 )
	The VERITAS Volume Manager (VxVM) is not able to create
	workable root/boot disk on a system.

	PHCO_25814:
	( SR:8606227294 CR:JAGad96355 )
	PHCO_24809 Introduced an extra 10 seconds delay during
	LVM volume group activation, when all the disks in the
	volume group are present.

	PHCO_25390:
	( SR:8606220106 CR:JAGad89247 )
	PHCO_24809 introduced behavior that will cause the
	lvlnboot(1M) command to fail when executed in recovery
	mode.  Executing 'lvlnboot -R' will fail to configure swap
	and dump volumes and messages similar to the following will
	be reported:
	lvlnboot: Unable to configure swap logical volume.
	Swap logical volume size beyond the IODC max address.
	lvlnboot: Unable to configure dump logical volume.
	Dump logical volume size beyond the IODC max address.

	PHCO_24809:
	( SR:8606196725 CR:JAGad65923 )
	A volume group (VG) which is activated shared
	(vgchange -a s), may be left with Physical volumes (PVs)
	still attached on de-activation. If the VG is then exported,
	it will not be possible to import and activate a different
	VG using the same group file minor number without rebooting.
	Typical activation error:
		vgchange: Couldn't set the unique id for volume
			  group "XXX":
		File exists

	( SR:8606204445 CR:JAGad73627 )
	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:8606195190 CR:JAGad64396 )
	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.

	( SR:8606202819 CR:JAGad71993 )
	The vgcfgbackup command gives incorrect information about
	the given file name.  User might see the following error
	message:

	  vgcfgback: Invalid filename: "XXX" specified with -f.

	( SR:8606214397 CR:JAGad83588 )
	When more than one Volume Groups in LVM uses the same minor
	number they overstep on each others data structures in the
	kernel resulting in unpredictable behavior with any of the
	operations with these volume groups. This problem will not
	go away even after removing both the volume groups. Any
	creation of a volume group with the same minor number (after
	removing all the Volume Groups using that minor number)
	would fail with the following message even though there is
	no volume group using that minor number at this time.

	vgcreate: Volume group "/dev/vgX" could not be created:
	A volume group is already using this major and minor number.
	Please check the minor number of the "group" device file.

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

	( SR:8606214419 CR:JAGad83610 )
	LVM commands coredump. Due to stack size overflow.

	( SR:8606186700 CR:JAGad55910 )
	The pvcreate manual page does not document that
	pvcreate when invoked with the -f may overwrite disks under
	the control of the Veritas volume manager.

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

	( SR:8606166168 CR:JAGad35455 )
	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:8606213740 CR:JAGad82931 )
	Very slow activation when physical volume links are
	down. If some of the links to physical volumes in a LVM
	volume group are not accessible then activation of volume
	group containing these physical links would take from
	several minutes to hours depending upon the number of
	unavailable links.

	( SR:8606204444 CR:JAGad73626 )
	When running lvdisplay simultaneously with the
	pvmove and the lvmerge commands, the lvdisplay command
	displays zeros extent information.

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

Defect Description: 
	PHCO_35313:
	( SR:8606449884 CR:JAGag07000 )
	The field width for displaying the device special filename
	was set to 18.

	Resolution:
	The vgcfgrestore command has been modified such that its
	output will not truncate the device special file name if its
	length is more than 18 characters long.

	( SR:8606449890 CR:JAGag07004 )
	The field width for displaying the logical volume name was
	set to 8.

	Resolution:
	The pvdisplay command has been modified such that its
	output will not truncate the logical volume name if its
	length is more than 8 characters long.

	( SR:8606449888 CR:JAGag07002 )
	vgdisplay command does not close the file descriptors of the
	volume groups when the descriptors are not being used.
	When the number of volume groups to be displayed by the
	command is more than "maxfiles" tunable then the open(2)
	system call fails.

	Resolution:
	vgdisplay command has been modified to close the file
	descriptor after displaying the volume group, to avoid
	running out of file descriptors.

	( SR:8606430256 CR:JAGaf89715 )
	"vgreduce -f" command was not able to determine the latest
	copy of volume group information from the physical volumes
	due to the inconsistency of LVM metadata, and this resulted
	in the core dump.

	Resolution:
	vgreduce command has been modified not to read the LVM
	metadata, thereby avoiding core dump when LVM metadata is
	inconsistent.

	( SR:8606442543 CR:JAGag00293 )
	The number of physical volumes belonging to a volume group
	that has been previously reduced using vgreduce -f was
	incorrectly calculated. This caused the vgscan command to
	skip such volume groups.

	Resolution:
	vgscan command has been modified to correctly calculate
	the number of physical volumes in a volume group that has
	been previously reduced using vgreduce -f.

	( SR:8606457243 CR:JAGag13572 )
	Enhancement: There is no method to prevent automatic
	synchronization of stale extents which are created as
	a result of the lvmerge and "lvextend -m" commands. This may
	not be desirable in situations where many such operations
	are to be performed. The lvsync command, when provided with
	multiple logical volumes as arguments, serializes the
	synchronization of each logical volume. The time taken for
	lvsync command to perform synchronization of all the
	logical volumes is the cumulative time for synchronizing
	each logical volume. This may not be desirable when
	a large number of logical volumes are provided as command
	line arguments.

	Resolution:
	A new command line option "-s" is provided with the lvmerge
	and lvextend commands, which will allow them to complete
	without synchronizing the stale extents of the
	logical volume(s). Synchronization is still necessary but
	can be done manually using the lvsync command. A new
	command line option, "-T", is provided with lvsync command,
	allowing the resynchronization of logical volumes within
	a volume group to be performed parallelly. In many cases
	this will reduce the time needed to synchronize the
	stale extents.

	( SR:8606430833 CR:JAGaf90290 )
	pvcreate and vgcfgrestore commands do not check whether the
	physical volume specified is under Oracle ASM control.
	Therefore physical volume is overwritten with LVM metadata
	information.

	Resolution:
	pvcreate and vgcfgrestore commands have been modified to
	check whether the physical volume is under Oracle ASM
	control, and not to overwrite the physical volume with any
	data if such is the case.

	( SR:8606456785 CR:JAGag13166 )
	There is no LVM command available by which the user can
	determine if a given physical volume is under LVM control.

	Resolution:
	pvdisplay command has been modified to add a new option,
	"-l", to check if the given physical volume is under
	LVM control.

	( SR:8606422021 CR:JAGaf81846 )
	While increasing a mirror copy of a logical volume,
	alternate links were not considered in PVG-strict
	allocation policy check.

	Resolution:
	The code has been modified to ensure that the new
	mirror copy would not be allocated in the same PVG when
	PVG-strict allocation policy is set and only the alternate
	links are present in the PVG.

	( SR:8606397355 CR:JAGaf57337 )
	lvchange(1M) and lvcreate(1M) manual pages were not
	updated to reflect the behavior since PHKL_29979.

	Resolution:
	lvchange(1M) and lvcreate(1M) manual pages are modified to
	reflect the behavior since PHKL_29979.

	( SR:8606444829 CR:JAGag02362 )
	vgimport(1M) manual page has incorrect description for the
	"-s" option. "-p" and/or "-v" options are not must, but
	they are optional along with "-s" option. The vgimport
	operation never takes place when the "-p" (preview mode)
	option is used.

	Resolution:
	The description of "-s" option in the vgimport(1M)
	manual page is corrected. "-p" and/or "-v" options are
	optional along with "-s".

	( SR:8606443239 CR:JAGag00913 )
	The lvcreate(1M), lvdisplay(1M), lvchange(1M),
	vgdisplay(1M) and vgchange(1M) manual pages were inaccurate
	and lacked adequate details on the correct use of logical
	volumes that have mirror consistency recovery turned
	off (NONE).

	Resolution:
	The lvcreate(1M), lvdisplay(1M), lvchange(1M),
	vgdisplay(1M) and vgchange(1M) manual pages are updated
	to correctly describe the possible states for logical
	volumes. Also details of when and when not logical volumes
	that have mirror consistency turned off (NONE) should be
	used have been added to the manual pages. The documented
	possible states for the logical volumes in these manual
	pages is correct for systems running with LVM Kernel patch
	PHKL_33390 and later revisions. Earlier versions of LVM
	Kernel will not necessarily match the behavior documented
	in these manual pages but will still function properly.

	PHCO_34196:
	( SR:8606401135 CR:JAGaf61084 )
	The code that rounds down the logical volume size to
	extent boundary fails when the number of extents
	requested is less than 1.

	Resolution:
	lvcreate(1M) is changed such that if a requested logical
	volume size is smaller than 1 physical extent, then
	lvcreate(1M) will create a logical volume that is the same
	size as 1 physical extent and allocate 1 physical extent
	to that volume.

	( SR:8606404441 CR:JAGaf64363 )
	The resync flag was wrongly set while restoring using
	vgcfgrestore(1M). This resulted in re-synchronization of
	mirrored extents again on reboot.

	Resolution:
	vgcfgrestore(1M) has been modified so that, when run on a
	physical volume containing the root logical volume in a
	normal boot, it will not set the resync flag.  However,
	for maintenance mode boot the operation of setting the
	resync flag for such physical volume will continue.

	( SR:8606426930 CR:JAGaf86411 )
	LVM commands were incorrectly handling internationalization
	enablement.

	Resolution:
	LVM commands are modified to support internationalization.

	( SR:8606399194 CR:JAGaf59159 )
	Logical volume timeout value was not initialized to a
	correct value while activating a volume group in shared
	mode with consistency recovery set to NOMWC.

	Resolution:
	vgchange(1M) has been modified to correctly initialize the
	logical volume timeout value.

	( SR:8606383951 CR:JAGaf44142 )
	A subset of LVM commands that support autobackup
	(-A option), when invoked with autobackup turned off, will
	not update the affected volume group list that is required
	for lvlnboot(1M) to run.  As a result of which lvlnboot(1M)
	scans all physical volumes, and this may lead to generate
	warning message on those physical volumes belonging to
	inactive volume group.

	Resolution:
	A subset of LVM commands that support autobackup
	(-A option) are modified to ensure that lvlnboot(1M) runs
	on only affected volume groups.

	( SR:8606430676 CR:JAGaf90134 )
	When the lvreduce(1M) is used to decrease the number
	of extents in a logical volume, LVM metadata is not
	properly updated. This causes "lvextend -m 1" invocation
	to fail even if enough free physical extents exists.

	Resolution:
	lvreduce(1M) has been changed to properly update the LVM
	metadata.

	PHCO_34061:
	( SR:8606400428 CR:JAGaf60383 )
	The variables used in the error handling were incorrectly
	initialized by vgchange(1M).

	Resolution:
	vgchange(1M) is modified to correctly initialize the
	variables used in error handling.

	( SR:8606400434 CR:JAGaf60389 )
	vgchange(1M) failed to update the Serviceguard daemon about
	the volume group status. This led to an inconsistency in
	volume group status as maintained by LVM and Serviceguard
	daemon, thus failing the vgchange(1M).  Also, the variables
	used in the error handling were incorrectly initialized by
	vgchange(1M).

	Resolution:
	vgchange(1M) is modified to correctly inform the
	Serviceguard daemon about the volume group status and
	correctly initialize the error handling related variables.

	( SR:8606397510 CR:JAGaf57492 )
	lvmerge(1M) fails when a user opens the split logical volume
	while the merge is in progress.

	Resolution:
	lvmerge(1M) is changed to disable logical volume open
	requests prior to the merge operation.

	( SR:8606397515 CR:JAGaf57497 )
	vgimport(1M) and vgscan(1M) had a hard-coded limitation of
	8160 physical volumes.

	Resolution:
	vgimport(1M) and vgscan(1M) are modified to remove the
	hard-coded limitation.

	PHCO_33310:
	( SR:8606364202 CR:JAGaf24856 )
	Currently, configuration changes to a volume group are
	allowed in exclusive mode only. A volume group activated in
	shared mode cannot be changed to exclusive mode even if the
	volume group is active only in a single node of the cluster.

	Resolution:
	Code changes were made to allow changing the activation mode
	of the volume group between shared and exclusive. This can
	now be done if the volume group is active in a single
	cluster node.

	Important:
	Note that changing the activation mode of a volume group
	from exclusive to shared is only allowed if the Mirror
	Write Cache consistency recovery (MWC) is not used by
	any of the underlying logical volumes.

	Note also that even when LVM does not support the activation
	of a volume group in shared mode with MWC set, it does not
	prevent the user from doing so, even if MWC has been
	incorrectly set. In this case, and with the patch installed,
	changing the activation mode of the volume group from
	shared to exclusive will succeed, while changing the
	activation mode from exclusive to shared will fail.

	( SR:8606405595 CR:JAGaf65516 )
	Few error messages were being incorrectly referenced from
	message catalog file, leading to incorrect messages being
	displayed.

	Resolution:
	LVM messages are now being correctly referenced from the
	message catalog file.

	( SR:8606410321 CR:JAGaf70203 )
	The code assumes that only special device files (which
	are smaller than MAX_SMALL_SIZE) can exist under the /dev
	directory. This assumption is broken if other large file
	types reside under the /dev directory.

	Resolution:
	Commands have been changed to handle files of size greater
	than MAX_SMALL_FILE under /dev directory.

	PHCO_30698:
	( SR:8606358733 CR:JAGaf19429 )
	Enhancement:  Pre-enable LVM support for online replacement
	of disks.

	Replacing a defective disk in a Shared LVM volume group
	first requires deactivating the volume group (taking it
	offline), and then activating the volume group in exclusive
	mode from a single node, followed by a series of LVM
	commands to move away the data mapped to the defective disk,
	before the disk can be replaced.  After the disk is
	replaced, the data has to be moved back.  Deactivating the
	volume group makes the user data unavailable.  The process
	of moving the data is time consuming and error prone.

	Resolution:
	Kernel and Command changes were made to provide the LVM
	online disk replacement feature.  The pvchange(1M) command
	has been modified, providing additional switches to allow
	detaching and re-attaching a physical volume or path to a
	device.  The usage of the vgcfgrestore(1M) has been modified
	to disallow restoring disks while they are attached to an
	active volume group (a potential source of problems in the
	past).  With the new command options, it is possible to
	replace a disk online without deactivating the volume group
	or changing the volume group configuration.

	( SR:8606358753 CR:JAGaf19449 )
	Enhancement: Pre-enable LVM support for online replacement
	of disks.

	There are situations where Disks that partially fail, or
	fail inconsistently, may never be taken offline.  When a
	user i/o fails, LVM makes the device unavailable, but LVM
	will make it available again if a subsequent LVM test i/o
	succeeds.

	Resolution:
	Kernel and Command changes were made to pre-enable the LVM
	online disk replacement feature.  One aspect of these
	changes is that they provide a new option to pvchange(1M) to
	allow directly detaching (disabling) a disk.

	( SR:8606358764 CR:JAGaf19460 )
	Enhancement: Pre-enable LVM support for online replacement
	of disks.

	There are situations where devices perform badly without
	ever reporting a failed i/o to LVM.  In these circumstances
	LVM is not aware that there is a problem so it continues to
	use the device.  If the device contains a mirrored LV, any
	writes to the logical volume will be directed to the bad
	device, thus limiting performance.

	LVM has no way to temporarily disable a marginal device.

	Resolution:
	Kernel and Command changes were made to provide the LVM
	online disk replacement feature.  One aspect of these
	changes is that they provide a new option to pvchange(1M) to
	allow directly detaching (disabling) a disk.

	( SR:8606322717 CR:JAGae85184 )
	The range for the LVM logical volume i/o timeout is infinite
	(default) or 2-300 seconds.  The same range applies to the
	LVM physical volume i/o timeout.  This is an unnecessary
	artificial limitation.

	Resolution:
	Added code to provide different limits for the logical
	volume i/o timeout and physical volume i/o timeout.
	Modified the logical volume i/o timeout limit to 2^32-1
	seconds.  Left the physical volume i/o timeout range as it
	was:  infinite (default) or 2-300sec.

	( SR:8606350908 CR:JAGaf11720 )
	The code to import a shared volume group via "vgimport -s"
	does not do the proper lvmtab locking.  Consequently, other
	commands can write on the lvmtab when vgimport is updating
	it, resulting in the corrupted lvmtab.

	Resolution:
	Added the proper lvmtab locking.

	( SR:8606350664 CR:JAGaf11476 )
	vgchgid(1M) allocates an array of file descriptors to hold
	the PV's provided on the command line.  It does not check
	the number of PV's provided against the size of the array,
	and it stores file descriptors beyond the end of the array,
	corrupting the command stack, and eventually resulting in
	the SIGILL abort.

	Resolution:
	Added the proper check for the number of PVs provided
	prior to opening the PVs.

	PHCO_29379:
	( SR:8606217852 CR:JAGad87002 )
	Without the changes  delivered  by this patch,  unrecognized
	errors will be returned  by iSCSI PVs which will cause these
	PVs  not  to be  attached  to  the  Volume  Group.  Mounting
	filesystems  residing on logical volumes comprising of iSCSI
	PVs will then result in error messages as the iSCSI PVs will
	not be accessible at the time filesystems are mounted during
	the boot-up sequence.
	This product update contains minor enhancements required to
	enable iSCSI support in LVM.

	Resolution:
	The code was modified to recognize the presence of iSCSI PVs
	at boot up time, and to allow the activation of these volume
	groups  to be  retried.  Error  messages  which  would  have
	normally  resulted from the failed  activation have now been
	changed to notification messages for these cases.

	( SR:8606279722 CR:JAGae43711 )
	This  error is the  result of the  configure  script  of LVM
	commands   patches   making  an   assumption   that  if  the
	LVM-MIRROR-RUN fileset of the patch is installed the LVM-RUN
	fileset of the same patch is also installed.

	Resolution:
	The patch  scripts were  modified to remove any  assumptions
	regarding the filesets installed.

	( SR:8606305556 CR:JAGae68604 )
	vgcfgrestore(1M)  does not  check  that  the new  disk is at
	least  as  large  as  the  old  disk  before  restoring  the
	configuration.

	Resolution:
	vgcfgrestore(1M)  now verifies that the new disk is at least
	as  large,  or  larger  than the old  disk.  If the new disk
	is smaller  than  the old  disk, then  it  displays an error
	message and aborts the operation.

	( SR:8606305780 CR:JAGae68828 )
	The  vgsync(1M)  command  synchronizes  the logical  volumes
	serially  inside a loop  statement.  The command  exits this
	loop  upon  encountering  the  first  error  and it does not
	attempt to synchronize the remaining logical volumes.

	Resolution:
	Now   the   vgsync(1M)    command    continues    with   the
	synchronization  of the remaining logical volumes even if it
	encounters an error with any logical volume, and it displays
	an error message, if required.

	( SR:8606305784 CR:JAGae68832 )
	The lvlnboot(1M) command will corrupt the Boot Data Reserved
	Area's  portion in an alternate  link  configuration  due to
	allocating an incorrect amount of memory.

	Resolution:
	The  lvlnboot(1M)  command has been modified to allocate the
	correct  amount of memory to match the number of entries  in
	the lvmtab file.

	( SR:8606305787 CR:JAGae68835 )
	On a physical  volume, two copies of status  information are
	maintained.  During  vgimport(1M),  the best copy  should be
	selected  from  the  available   copies.  vgimport(1M)   was
	incorrectly  checking  only  the  first  copy of the  status
	information  and would fail if it was not valid even  though
	the second copy was.

	Resolution:
	The  vgimport(1M)  code was modified to check for the second
	copy of the status area if the first copy is corrupt.

	( SR:8606315175 CR:JAGae77907 )
	When the vgextend(1M) or vgcreate(1M)  commands are supplied
	with more than one physical  volumes, and there is a failure
	in  installing  any of the PVs, then  there is an  incorrect
	initialization  of  a  pointer  in  the  code  resulting  in
	incorrect data remaining in the /etc/lvmtab file.

	Resolution:
	The code is modified to correctly initialize the pointers so
	that the /etc/lvmtab file contains correct data.

	( SR:8606315178 CR:JAGae77910 )
	If a physical  volume is smaller  than the  physical  extent
	size, then in some cases LVM will attempt to read beyond the
	end of the physical device.

	Resolution:
	The code was  modified  to  prevent  the  situation  where a
	physical volume can be smaller than the extent size.

	( SR:8606315186 CR:JAGae77918 )
	The word "not" is missing from the message.

	Resolution:
	The  lvlnboot(1M)  message has been  modified to include the
	missing word.

	( SR:8606316260 CR:JAGae78977 )
	Although the duplicate  entry is recognized by the code, the
	failure  causes the command to abort in a way that the error
	is not reported to the user.

	Resolution:
	The  code was  modified  to   check   for  the    duplicate
	physical volume and display an appropriate error message.

	( SR:8606320951 CR:JAGae83433 )
	The size allocated to the array  containing  the list of PVs
	is less that the possible number of PVs and alternate  links
	to PVs in a VG. When a larger number of PVs are encountered,
	vgscan(1M)  attempts to write  beyond the array limits, and
	fails.

	Resolution:
	The  size  of the  array  for   holding the PVs has now been
	correctly allocated.

	( SR:8606344120 CR:JAGaf04972 )
	During  restoring of  volume group configuration information
	on a  Physical Volume(PV),  the number  of PVs in the backup
	file used for restore is verified against the  number of PVs
	actually in the  currently  active VG.  If the  verification
	fails  then the  operation  is  aborted.  This  verification
	method  is  incorrect,  since  alternate  links  to a PV are
	considered  whereas  alternate  links are not present in the
	backup file.

	Resolution:
	The validation of the number of PVs in the active VG against
	the number in the backup file is not required and is in some
	cases wrong, hence it is removed.

	( SR:8606323332 CR:JAGae85797 )
	This problem occurs when,  unknowingly by the user, a volume
	group file is created with a vg index number already in use.
	The  current  LVM  algorithm  rejects  any new minor  number
	(0xMMMMMM) if it  matches  any  pre-existing  minor  number.
	However,  it fails to  recognize  that the vg  index  number
	(represented  by 0xNN0000)  could still be duplicated.  (For
	example 0x123456 and 0x120000).

	Resolution:
	The  fix  for  this  is to  restrict  the  vgcreate(1M)  and
	vgimport(1M)  commands to only accept  group  files with the
	format of 0xNN0000.

	( SR:8606352319 CR:JAGaf13124 )
	The code which opens, reads, and validates the metadata on a
	PV properly aborts if it cannot open or read the PV, but
	fails to abort when it finds invalid metadata.

	Resolution:
	The code now causes the command to abort when it finds
	corrupt metadata.

	PHCO_27913:
	( SR:8606255308 CR:JAGae19635 )
	When a function inside vgimport(1M) discovers that the
	volume group does not have a unique minor number, it prints
	out an error message and returns the wrong value to the
	calling function.  So instead of aborting, vgimport(1M)
	continues to import a volume group with a duplicate minor
	number.  This can result in kernel data structures being
	corrupted.

	Resolution:
	Change the value that the function in vgimport(1M) returns,
	so the command will abort an attempt to import a volume
	group with a duplicate minor number.

	( SR:8606198887 CR:JAGad68076 )
	When a disk is used in a shared volume group, it is
	assigned a cluster id.  When this disk is reused, the
	cluster id is not removed properly.

	Resolution:
	A change was made to vgexport(1M) to clear the cluster id
	and configured activation mode upon export.  When the
	vgcreate(1M) command is ran after vgexport(1M), the cluster
	id is then set to null and the activation mode is set to a
	standard configuration mode.

	( SR:8606199556 CR:JAGad68743 )
	When the lvremove(1M) command removes a logical volume in
	the root volume group, the lvlnboot(1M) command is invoked
	with the "-R" option.  As a result, a "-1" is marked in two
	fields of the Boot Data Reserved Area (BDRA).  This causes
	the subsequent activation to think the swap LV disk is
	itself an LV.  This can eventually result in a system
	panic.

	Resolution:
	The lvlnboot(1M) command was modified to print out a
	warning message when lvlnboot(1M) fails.  It also marks the
	swap device as not present, preventing any confusion upon
	next boot.

	( SR:8606223480 CR:JAGad92577 )
	The vgscan(1M) command was dependent on the order of volume
	groups in /etc/lvmtab.  When the first volume group in
	/etc/lvmtab is not vg00, the physical volumes associated
	with vg00 will not be added to the /etc/lvmtab file.

	Resolution:
	Modified the vgscan(1M) command so that it no longer
	depends on the order of the volume groups in the
	/etc/lvmtab file.

	( SR:8606266304 CR:JAGae30553 )
	The wrong array index was used when setting the error flag
	of a physical volume.  This will only occur when the
	lvlnboot(1M) command is executed and a disk is missing or
	has failed.

	Resolution:
	A one line code change was made to correct the index used
	to mark the bad disk.

	( SR:8606235481 CR:JAGae04635 )
	The vgcfgbackup(1M) and pvremove(1M) commands have some
	read and write calls which do not properly check the amount
	of data read or written.  They currently just check that at
	least one byte of data was written.  Although it is rare,
	there are some cases in which only a part of the data was
	read or written.

	Resolution:
	The read and write calls in both the vgcfgbackup(1M) and
	pvremove(1M) commands now check to ensure that all data was
	read or written correctly.

	( SR:8606230792 CR:JAGae00030 )
	The vgchgid(1M) command replaces the volume group id fields
	correctly, but does not recalculate the checksum with the
	new volume group ids.  This causes the validation of the
	Boot Data Reserved Area (BDRA) to fail, making the system
	using this BDRA not bootable (except in maintenance mode).

	Resolution:
	The vgchgid(1M) command now recalculates the checksum with
	the new volume group ids.

	( SR:8606251163 CR:JAGae17229 )
	Before removing a volume group, vgremove(1M) does not check
	to see if a volume group is part of a cluster. When an
	active clustered volume group is removed in this manner,
	other nodes in the cluster are not notified of the volume
	group's removal.  Because the other nodes do not know that
	the volume group has been removed, the cmhaltcl (1M)
	command will fail.  The vgremove command also does not
	completely remove an active clustered volume group, so
	there will be residual data which may interfere with a
	volume group created in the future.

	Resolution:
	The code has been modified to prevent the vgremove (1M)
	command from removing an active volume group which is part
	of a cluster. The volume group should first be made non-
	clustered and then removed.  The correct procedure to
	remove a clustered volume group is described below:

	1. Deactivate the volume group on all nodes in the cluster.
	2. Export the volume group on all nodes except one.
	3. Make the volume group non-clustered on the remaining
	node.
	4. Activate the volume group locally on the remaining node.
	5. Remove the volume group.

	( SR:8606226992 CR:JAGad96054 )
	The problem is that the lvcreate(1M) command doesn't check
	the parameters against the maximum limit when -L is used.
	The bad parameter eventually causes a memory fault.

	Resolution:
	A check was added to lvcreate(1M) which checks that
	logical_volume_size/physical_extent_size <
	LVM_maximum_extents when the L option is used.  If a size
	specified with the -L option results in too many extents
	(based on the extent size of the VG) then an error message
	will be displayed.

	PHCO_27408:
	( SR:8606251225 CR:JAGae17291 )
	This product update contains minor enhancements required to
	enable the VA7405 and VA7410 disk arrays to be used with
	LVM.

	Resolution:
	Changes were made in LVM to use a unique identifier for each
	LUN belonging to the VA7405 and VA7410 disk arrays.  With
	these changes the VA7405 and VA7410 disk arrays can be used
	with LVM.

	( SR:8606247046 CR:JAGae13486 )
	This problem was exposed when a statically allocated array
	was changed to a dynamically allocated array.  During the
	execution of the vgimport(1M) command, a function was still
	assuming the array to be static, and was trying to access
	elements past the end of the dynamically allocated array.
	Stepping past the end of the array is what caused the
	vgimport(1M) command to core dump.

	Resolution:
	The function no longer assumes the array to be a specific
	size.  The function now looks at a variable which contains
	the number of elements in the array instead of relying on a
	maximum constant variable.

	PHCO_27099:
	( SR:8606262676 CR:JAGae27007 )
	The LVM library was not able to identify VxVM disks that
	contain Cross platform Data Sharing (CDS) identifier labels.

	Resolution:
	Enhance the LVM library to be able to identify
	VxVM disks that contain CDS identifier labels.

	PHCO_25814:
	( SR:8606227294 CR:JAGad96355 )
	Patch PHCO_24809 contained fixes to improve the volume
	group activation time of a volume group containing
	unavailable physical volumes. However, this fix
	introduced a 10 second delay during activation of a
	volume group with all the physical volumes are
	present. In all other cases the fix improves the
	activation time. According to the fix in patch
	PHCO_24809, during attaching of physical volumes, LVM
	will try opening all the physical volumes and if some
	opens fail, it will retry one more time after a delay
	of 10 seconds before giving up on the failed
	physical volumes. So the delay of 10 seconds should
	happen only upon retry, but instead it is happening
	for every try.

	Resolution:
	Corrected the retry loop to invoke delay only during
	retry and not every time.

	PHCO_25390:
	( SR:8606220106 CR:JAGad89247 )
	LVM dump and swap logical volumes should not extend beyond
	the maximum IODC block address of the device on which these
	contiguous logical volumes reside. To enforce this,
	lvlnboot(1M) verifies that logical volume size for dump and
	swap device is less than the maximum IODC block address of
	the device, which is obtained by doing an ioctl to the
	kernel with raw device id of the underlying device as an
	argument.  In PHCO_24809, as part of a code cleanup a typo
	error was made where block device id was set for the ioctl
	instead of raw device id. As a result, the ioctl call was
	failing and it caused the lvlnboot(1M) command to fail.

	Resolution:
	Corrected the problem in the ioctl argument, now it gets
	the maximum IODC block address from the raw device.

	PHCO_24809:
	( SR:8606196725 CR:JAGad65923 )
	When a shared volume group is deactivated and then exported,
	the volume group ID (vgid) is not cleared from the volgrp
	structure. If the shared 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. When the new VG is de-activated the previously
	used (no longer active) volgrp slot may be incorrectly used.
	This will result in the new volgrp being de-activated but
	with the PVs pvol structures still attached. The latest
	volgrp cannot be re-used with a different vgid without a
	system reboot. If this process is repeated the finite number
	of volgrp structures may be exhausted.

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

	( SR:8606204445 CR:JAGad73627 )
	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:8606195190 CR:JAGad64396 )
	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.

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

	( SR:8606202819 CR:JAGad71993 )
	The vgcfgbackup command did not check the file name
	correctly.

	Resolution:
	Modified the vgcfgbackup command to fix the problem.

	( SR:8606214397 CR:JAGad83588 )
	For every volume group configured, has an element in the
	volume group data structures array in the kernel which
	contains information specific to the volume group in the
	kernel. This entry is indexed by the group id (minor
	number) created during creation of the volume group.
	Since each entry contains information specific to a volume
	group, every volume group should have a unique group id.
	If more than one volume groups are created with the same
	group id, then they all map to the same element in the
	kernel data structure, resulting in corruption of the data
	structure. This causes unpredictable results with operations
	on all these volume groups and even the export of these
	volume groups does not happen cleanly resulting in
	prohibiting any further use of these minor numbers even
	after removing these volume groups.

	Resolution:
	Added a new check in vgcreate and vgimport to verify for the
	unique group id, so that an entry in the kernel data
	structure for the volume group is used only by this volume
	group. The check verifies that the group id file is unique
	in the /dev directory and is not used by any volume group.

	( SR:8606198832 CR:JAGad68021 )
	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:8606214419 CR:JAGad83610 )
	In LVM commands, some of the large size arrays are
	statically allocated resulting in stack size overflow,
	which causes the commands to coredump when run.

	Resolution:
	All the arrays and data structures are dynamically
	allocated resulting in less stack size usage.

	( SR:8606186700 CR:JAGad55910 )
	The manual page is incomplete.  It should warn
	of the possible pitfalls of using the -f option.

	Resolution:
	The document was corrected to fully describe the behavior
	of the pvcreate -f option.

	( SR:8606189090 CR:JAGad58306 )
	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.

	( SR:8606166168 CR:JAGad35455 )
	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:8606213740 CR:JAGad82931 )
	During Volume Group activation, LVM opens each physical
	link associated with the volume group. If the link is
	unavailable i.e. open returns ENXIO error, LVM retries
	opening the physical link for a maximum of 10 retries with a
	sleep of one second between each retry. Opening of physical
	links is a serial operation with commands issuing one open
	at a time. Since opening a physical link would take tens of
	seconds and total time of opening links is a cumulative of
	these times it would take several minutes to hours depending
	upon number of unavailable links in the volume group.

	Resolution:
	Fixing this defect requires corresponding kernel and
	commands patch. Since most of the time is spent in the
	one second sleeps between the retries and actual time
	opening the device being negligible changing the retry
	per device to retry per opening of all devices reduces the
	sleep time from (number of unavailable links * 10 seconds)
	to 10 seconds. Hence the total time will be a fraction
	more than the 10 seconds. For this kernel provides
	interface to open a device with no retries and the commands
	opens all the devices and then retries again
	all the unavailable devices after the retry sleep time.

	( SR:8606204444 CR:JAGad73626 )
	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.

	PHCO_23333:
	( SR:8606181365 CR:JAGad50582 )
	"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.

Enhancement: 
	Yes
	PHCO_35313:
	This patch enables support for parallel resynchronization
	capability in lvsync command.
	PHCO_30698:
		LVM Online Disk Replacement
	PHCO_27913:
		Enhancements were delivered in a patch this one has
		superseded.  Please review the Defect Description
		text for more information.

SR: 
	8606449890 8606449884 8606449888 8606430256 8606442543
	8606457243 8606430833 8606456785 8606422021 8606397355
	8606444829 8606443239 8606401135 8606404441 8606426930
	8606399194 8606383951 8606430676 8606400428 8606400434
	8606397510 8606397515 8606364202 8606405595 8606410321
	8606166168 8606181365 8606186700 8606189090 8606195190
	8606196725 8606198832 8606198887 8606199556 8606202819
	8606204444 8606204445 8606213740 8606214397 8606214419
	8606217852 8606220106 8606223480 8606226992 8606227294
	8606230792 8606235481 8606247046 8606251163 8606251225
	8606255308 8606262676 8606266304 8606279722 8606305556
	8606305780 8606305784 8606305787 8606315175 8606315178
	8606315186 8606316260 8606320951 8606322717 8606323332
	8606344120 8606350664 8606350908 8606352319 8606358733
	8606358753 8606358764

Patch Files: 

	LVM.LVM-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_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/lvmchk.1m
	/usr/share/man/man1m.Z/lvmerge.1m
	/usr/share/man/man1m.Z/lvsplit.1m
	/usr/share/man/man1m.Z/lvsync.1m
	/usr/share/man/man1m.Z/pvchange.1m
	/usr/share/man/man1m.Z/pvcreate.1m
	/usr/share/man/man1m.Z/pvdisplay.1m
	/usr/share/man/man1m.Z/vgcfgrestor.1m
	/usr/share/man/man1m.Z/vgchange.1m
	/usr/share/man/man1m.Z/vgdisplay.1m
	/usr/share/man/man1m.Z/vgimport.1m
	/usr/share/man/man1m.Z/vgreduce.1m

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

	LVM.LVM-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
	/usr/lib/nls/msg/C/lvm.cat
	/usr/sbin/lvchange
	/usr/newconfig/usl
	/usr/newconfig/sl
	/sbin/lvchange
	/sbin/lvcreate
	/sbin/lvdisplay
	/sbin/lvextend
	/sbin/lvlnboot
	/sbin/lvreduce
	/sbin/lvremove
	/sbin/lvrmboot
	/sbin/pvchange
	/sbin/pvck
	/sbin/pvcreate
	/sbin/pvdisplay
	/sbin/pvmove
	/sbin/pvremove
	/sbin/vgcfgbackup
	/sbin/vgcfgrestore
	/sbin/vgchange
	/sbin/vgchgid
	/sbin/vgcreate
	/sbin/vgdisplay
	/sbin/vgexport
	/sbin/vgextend
	/sbin/vgimport
	/sbin/vgreduce
	/sbin/vgremove
	/sbin/vgscan
	/usr/sbin/lvcreate
	/usr/sbin/lvdisplay
	/usr/sbin/lvextend
	/usr/sbin/lvlnboot
	/usr/sbin/lvreduce
	/usr/sbin/lvremove
	/usr/sbin/lvrmboot
	/usr/sbin/pvchange
	/usr/sbin/pvck
	/usr/sbin/pvcreate
	/usr/sbin/pvdisplay
	/usr/sbin/pvmove
	/usr/sbin/pvremove
	/usr/sbin/vgcfgbackup
	/usr/sbin/vgcfgrestore
	/usr/sbin/vgchange
	/usr/sbin/vgchgid
	/usr/sbin/vgcreate
	/usr/sbin/vgdisplay
	/usr/sbin/vgexport
	/usr/sbin/vgextend
	/usr/sbin/vgimport
	/usr/sbin/vgreduce
	/usr/sbin/vgremove
	/usr/sbin/vgscan
	/usr/sbin/lvmchk

what(1) Output: 

	LVM.LVM-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
	/usr/share/man/man1m.Z/lvchange.1m:
		None
	/usr/share/man/man1m.Z/lvcreate.1m:
		None
	/usr/share/man/man1m.Z/lvdisplay.1m:
		None
	/usr/share/man/man1m.Z/lvextend.1m:
		None
	/usr/share/man/man1m.Z/lvmchk.1m:
		None
	/usr/share/man/man1m.Z/lvmerge.1m:
		None
	/usr/share/man/man1m.Z/lvsplit.1m:
		None
	/usr/share/man/man1m.Z/lvsync.1m:
		None
	/usr/share/man/man1m.Z/pvchange.1m:
		None
	/usr/share/man/man1m.Z/pvcreate.1m:
		None
	/usr/share/man/man1m.Z/pvdisplay.1m:
		None
	/usr/share/man/man1m.Z/vgcfgrestor.1m:
		None
	/usr/share/man/man1m.Z/vgchange.1m:
		None
	/usr/share/man/man1m.Z/vgdisplay.1m:
		None
	/usr/share/man/man1m.Z/vgimport.1m:
		None
	/usr/share/man/man1m.Z/vgreduce.1m:
		None

	LVM.LVM-MIRROR-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
	/usr/newconfig/usr/sbin/lvchange.mir:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/newconfig/sbin/lvchange.mir:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $

	LVM.LVM-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
	/usr/lib/nls/msg/C/lvm.cat:
		None
	/usr/sbin/lvchange:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/newconfig/usl:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/newconfig/sl:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvchange:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvcreate:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvdisplay:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvextend:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvlnboot:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvreduce:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvremove:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/lvrmboot:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/pvchange:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/pvck:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/pvcreate:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/pvdisplay:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/pvmove:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/pvremove:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgcfgbackup:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgcfgrestore:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgchange:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgchgid:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgcreate:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgdisplay:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgexport:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgextend:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgimport:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgreduce:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgremove:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/sbin/vgscan:
		pthread.c $Date: 2004/03/03 03:31:45 $Revision: r11.
			11/3 PATCH_11.11 (PHCO_30544)
		specific.c $Date: 2004/03/03 03:30:19 $Revision: r11
			.11/1 PATCH_11.11 (PHCO_30544)
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
		$ Version_11.11  Jul 10 2006 21:53:25 $
	/usr/sbin/lvcreate:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/lvdisplay:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/lvextend:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/lvlnboot:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/lvreduce:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/lvremove:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/lvrmboot:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/pvchange:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/pvck:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/pvcreate:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/pvdisplay:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/pvmove:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/pvremove:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgcfgbackup:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgcfgrestore:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgchange:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgchgid:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgcreate:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgdisplay:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgexport:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgextend:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgimport:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgreduce:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgremove:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/vgscan:
		$Revision: @(#) lvm R11.11_BL2006_0916_1 PATCH_11.11
			 PHCO_35313
	/usr/sbin/lvmchk:
		None

cksum(1) Output: 

	LVM.LVM-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
	825219612 6294 /usr/share/man/man1m.Z/lvchange.1m
	3507223391 7222 /usr/share/man/man1m.Z/lvcreate.1m
	1236975187 4180 /usr/share/man/man1m.Z/lvdisplay.1m
	4129757171 3611 /usr/share/man/man1m.Z/lvextend.1m
	3225192748 1182 /usr/share/man/man1m.Z/lvmchk.1m
	3190716736 2923 /usr/share/man/man1m.Z/lvmerge.1m
	3732977337 3265 /usr/share/man/man1m.Z/lvsplit.1m
	208219013 1948 /usr/share/man/man1m.Z/lvsync.1m
	2352165705 6336 /usr/share/man/man1m.Z/pvchange.1m
	2326987365 2986 /usr/share/man/man1m.Z/pvcreate.1m
	3337695536 3826 /usr/share/man/man1m.Z/pvdisplay.1m
	4195900881 3472 /usr/share/man/man1m.Z/vgcfgrestor.1m
	778014915 6828 /usr/share/man/man1m.Z/vgchange.1m
	974412444 4321 /usr/share/man/man1m.Z/vgdisplay.1m
	1761078048 4499 /usr/share/man/man1m.Z/vgimport.1m
	4004309789 3304 /usr/share/man/man1m.Z/vgreduce.1m

	LVM.LVM-MIRROR-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
	300236440 573440 /usr/newconfig/usr/sbin/lvchange.mir
	20398871 921600 /usr/newconfig/sbin/lvchange.mir

	LVM.LVM-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
	2403109796 48698 /usr/lib/nls/msg/C/lvm.cat
	4186777890 552960 /usr/sbin/lvchange
	300236440 573440 /usr/newconfig/usl
	20398871 921600 /usr/newconfig/sl
	2858811828 897024 /sbin/lvchange
	2858811828 897024 /sbin/lvcreate
	2858811828 897024 /sbin/lvdisplay
	2858811828 897024 /sbin/lvextend
	2858811828 897024 /sbin/lvlnboot
	2858811828 897024 /sbin/lvreduce
	2858811828 897024 /sbin/lvremove
	2858811828 897024 /sbin/lvrmboot
	2858811828 897024 /sbin/pvchange
	2858811828 897024 /sbin/pvck
	2858811828 897024 /sbin/pvcreate
	2858811828 897024 /sbin/pvdisplay
	2858811828 897024 /sbin/pvmove
	2858811828 897024 /sbin/pvremove
	2858811828 897024 /sbin/vgcfgbackup
	2858811828 897024 /sbin/vgcfgrestore
	2858811828 897024 /sbin/vgchange
	2858811828 897024 /sbin/vgchgid
	2858811828 897024 /sbin/vgcreate
	2858811828 897024 /sbin/vgdisplay
	2858811828 897024 /sbin/vgexport
	2858811828 897024 /sbin/vgextend
	2858811828 897024 /sbin/vgimport
	2858811828 897024 /sbin/vgreduce
	2858811828 897024 /sbin/vgremove
	2858811828 897024 /sbin/vgscan
	4186777890 552960 /usr/sbin/lvcreate
	4186777890 552960 /usr/sbin/lvdisplay
	4186777890 552960 /usr/sbin/lvextend
	4186777890 552960 /usr/sbin/lvlnboot
	4186777890 552960 /usr/sbin/lvreduce
	4186777890 552960 /usr/sbin/lvremove
	4186777890 552960 /usr/sbin/lvrmboot
	4186777890 552960 /usr/sbin/pvchange
	4186777890 552960 /usr/sbin/pvck
	4186777890 552960 /usr/sbin/pvcreate
	4186777890 552960 /usr/sbin/pvdisplay
	4186777890 552960 /usr/sbin/pvmove
	4186777890 552960 /usr/sbin/pvremove
	4186777890 552960 /usr/sbin/vgcfgbackup
	4186777890 552960 /usr/sbin/vgcfgrestore
	4186777890 552960 /usr/sbin/vgchange
	4186777890 552960 /usr/sbin/vgchgid
	4186777890 552960 /usr/sbin/vgcreate
	4186777890 552960 /usr/sbin/vgdisplay
	4186777890 552960 /usr/sbin/vgexport
	4186777890 552960 /usr/sbin/vgextend
	4186777890 552960 /usr/sbin/vgimport
	4186777890 552960 /usr/sbin/vgreduce
	4186777890 552960 /usr/sbin/vgremove
	4186777890 552960 /usr/sbin/vgscan
	1439250424 1603 /usr/sbin/lvmchk

Patch Conflicts: None

Patch Dependencies: 
	s700: 11.11: PHKL_24779
	s800: 11.11: PHKL_24779

Hardware Dependencies: None

Other Dependencies: 
	PHCO_33310:
	Serviceguard configurations using shared logical volumes
	should also install the following softwares/patches to
	obtain the online volume reconfiguration fix for
	8606364202 (JAGaf24856).
	- LVM kernel - PHKL_33390
	- Serviceguard - PHSS_33834

	PHCO_30698:
	In order to support the changes to the LVM logical
	volume i/o timeout described by JAGae85184, the following
	product update must also be installed:  PHKL_30697.

	PHCO_30698:
	This product update pre-enables a new feature which allows
	for the online disk replacement of disks in LVM.  This
	feature is described by CRs:
	8606358733 (JAGaf19429),  8606358753 (JAGaf19449), and
	8606358764 (JAGaf19460).
	To fully enable this feature, the following
	update must also be installed: PHKL_31216.
	PHCO_30698 will disallow restoring LVM configuration with
	vgcfgrestore(1M) on physical volumes attached to an active
	volume group to prevent the possibility of silent data
	corruption.  Before executing vgcfgrestore(1M), the volume
	group must be first deactivated.  PHKL_31216 will allow the
	operation without requiring deactivation, by making
	available a new option to pvchange(1M) to detach a physical
	disk.
	Without PHKL_31216, the new option to pvchange(1M) which
	allows detaching a physical disk, will not work.

	PHCO_29379:  To enable iSCSI  support in LVM, the  following
	must  be   installed:  PHKL_30552   and   PHCO_29379.  These
	product updates may be installed in any order.

	This patch is a member of a set of patches needed to enable
	VxVM rootability on HP-UX 11i.  The patch set includes
	PHKL_27096, PHCO_27099, PHCO_27100, PHCO_27101, PHCO_27103,
	and PHCO_27209.  If any of the patches belonging to this
	set is not installed on the system, then the VxVM
	rootability feature will not function.  When the HP-UX 11i
	0902 OEUR is installed, it will install the full set of
	required patches for VxVM, including this patch.

Supersedes: 
	PHCO_34196 PHCO_34061 PHCO_33310 PHCO_30698 PHCO_29379 PHCO_27913
	PHCO_27408 PHCO_27099 PHCO_25814 PHCO_25390 PHCO_24809 PHCO_23333

Equivalent Patches: None

Patch Package Size: 2060 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_35313

	5. Run swinstall to install the patch:

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

	By default swinstall will archive the original software in
	/var/adm/sw/save/PHCO_35313.  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 PHCO_35313.text file is
	available in the product readme:

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

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

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

Special Installation Instructions: None