 |
≫ |
|
|
|
パッチ名: PHCO_36597
パッチ摘要: s700_800 11.11 VERITAS VM管理サービスプロバイダパッチ07
作成日: 07/08/08
公開日: 07/08/14
ハードウェアプラットフォームおよびOSリリース:
s700: 11.11
s800: 11.11
現象:
PHCO_36597:
(SR:8606493872 CR:JAGag45805)
Veritas不具合番号: 1048823
VxVMコマンドパッチPHCO_36595での変更をサポートするために、このパッチを
作成しました。
問題点の説明:
PHCO_36597:
(SR:8606493872 CR:JAGag45805)
Veritas不具合番号: 1048823
VxVMコマンドパッチでの変更がVxVM内部のユーザーレベルライブラリに影響を
与えていました。VRTSvmpro製品はこのライブラリに依存しているので、VMプ
ロバイダパッチをVxVMコマンドパッチと一緒に提供する必要があります。
-----------------------------------------------------------------------------
Patch Name: PHCO_36597
Patch Description: s700_800 11.11 VERITAS VM Mgmt Service Provider Patch 07
Creation Date: 07/08/08
Post Date: 07/08/14
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
VRTSvmpro 3.5m
Filesets:
VRTSvmpro.VMPRO-PRG,fr=3.5m,fa=HP-UX_B.11.11_32/64,v=HP
VRTSvmpro.VMPRO-PRG,fr=3.5m,fa=HP-UX_B.11.11_32/64,v=VERITAS
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHCO_33402: PANIC HANG
Category Tags:
defect_repair general_release critical panic halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_36597
Symptoms:
PHCO_36597:
( SR: 8606493872 CR: JAGag45805)
Veritas Incident Number: 1048823
This patch is built to support
changes in VxVM Commands patch PHCO_36595
PHCO_35827:
( SR: 8606478909 CR: JAGag33148 )
Veritas Incident Number: 992602
This patch is built for compatibility issues with
VxVM patch, PHCO_35815
PHCO_34348:
( SR: 8606429984 CR: JAGaf89443)
This patch is built for compatibility issues with
VxVM patch, PHCO_34255
PHCO_33402:
( SR: 8606405457 CR: JAGaf65378)
Compatibility issues observed with
VxVM patches, PHCO_33362.
Panic is observed with the following stack trace:
panic+0x6c
assfail+0x3c
scsi_strategy+0x300
dmp_dev_strategy+0x1b8
gendmpstrategy+0x4a0
dmpstrategy+0x10
vol_dev_strategy+0x11c
voldiosio_start+0x114
volkcontext_process+0x3f8
volsiowait+0x70
voldio+0x398
vol_voldio_read+0x1c
volconfig_ioctl+0x534
volsioctl_real+0x1d0
volsioctl+0x10
vols_ioctl+0x58
spec_ioctl+0xac
vno_ioctl+0x98
ioctl+0x118
syscall+0x768
syscallinit+0x55c
( SR: 8606408697 CR: JAGaf68599)
Symptoms:
1. Veritas incident: 309092
Rename DG operation from VEA fails in setting activation
for that DG.
/usr/sbin/vxdg -g dg2 set activation=rw
VxVM vxdg ERROR V-5-1-3203
Disk group dg2: activation failed: rw:
Invalid mode for shared disk group
2. Veritas incident: 297371
VEA incorrectly shows DRL logs for DCM logs
3. Veritas incident: 286497
The relayout status monitor is showing the Initial Volume
layout and the Desired Volume layout incorrectly.
4. Veritas incident: 299697
VEA will not initialize to the default hpdisk format.
5. Veritas incident: 286501
maxsize option in resize volume operation from VEA GUI uses
incorrect disk data.
6. Veritas incident: 302852
vxsvc may spin in vmprovider
PHCO_31203:
( SR: 8606378772 CR: JAGaf39030)
This patch is built for compatibility issues with
VxVM patch, PHCO_30850.
PHCO_31059:
( SR: 8606364915 CR: JAGaf25554)
VEA doesn't show controllers after installing
PHCO_29980.
PHCO_28693:
( SR: 8606310698 CR: JAGae73569)
Incremental fixes made to the VM Provider product
(VRTSvmpro) since the 3.5m release on the 0902 OEUR.
Defect Description:
PHCO_36597:
( SR: 8606493872 CR: JAGag45805)
Veritas Incident Number: 1048823
The changes made in VxVM command patch have impacted a
VxVM internal user-level library. Since the VRTSvmpro
product has a dependency on the library, a VM
provider patch has to be delivered together with VxVM
command patch.
PHCO_35827:
( SR: 8606478909 CR: JAGag33148)
Veritas Incident Number: 992602
The changes made in VxVM command patch have impacted a
VxVM internal user-level library. Since the VRTSvmpro
product has a dependency on the library, a VM
provider patch has to be delivered together with VxVM
command patch.
PHCO_34348:
The changes made in VxVM command patch have impacted a
VxVM internal user-level library. Since the VRTSvmpro
product has a dependency on the library, a VM
provider patch has to be delivered together with VxVM
command patch.
PHCO_33402:
( SR: 8606405457 CR: JAGaf65378)
Changes made in VxVM command patch have impacted
a VxVM internal user-level library. Since the
VMPRO product has a dependency on this library,
we need to provide an updated VM provider patch.
( SR: 8606408697 CR: JAGaf68599)
Defect Descriptions:
1. Veritas incident: 309092
dg activation would be incorrectly set on non-shared
disk groups.
Resolution:
Properly check if a disk group is not shared and don't set
activation mode if not shared.
2. Veritas incident: 297371
The problem is hit in following scenario.
Create a volume with DCM log:
# vxassist -g rootdg make edvol 10M logtype=dcm nlog=1
In VEA, select "Volumes" in the right pane.
The left pane reports:
Name Group name Status ... Log
edvol rootdg Healthy ... DRL
Resolution:
Added a new property "hasdcm" on volume to separate out
DCM log from DRL.
3. Veritas incident: 286497
Users has a striped-pro volume(stripe-mirror 2 mirrors
2 stripes). User tries to relayout it to a striped
volume(2 cols) through the VEA GUI, relayout states are
shown improperly in the relayout status monitor.
Resolution:
Properly parse the output of the vxrelayout status command
and properly show relayout states in the gui.
4. Veritas incident: 299697
VEA will not recognize hpdisk format in the
/etc/default/vxdisk file.
Resolution:
Check /etc/default/vxdisk file for hpdisk string and use as
default if used.
5. Veritas incident: 286501
For resize volume, when a user selects no disks, the maxgrow
command uses an alloc= followed by *all* the disks in the
disk group. No alloc= option should be used at all.
Additionally, but more important, if a user selects disks
and then selects maxgrow, the maxgrow commands still uses
alloc= with *all* the disks in the disk group. It should
have used an alloc= with only the selected disks.
Resolution:
Pass the selected disks to the vxassist maxgrow command. If
user did not select any disks, no alloc option will be used.
6. Veritas incident: 302852
vxsvc may spin in vmprovider vs_notify_process_event with
VE_SYS error when vxconfigd is restarted. This uses
too much cpu time.
Resolution:
Appropriately check for a VE_SYS return code from
notification events when vxconfigd is restarted.
PHCO_31203:
changes made in VxVM command patch have impacted
a VxVM internal user-level library.Since the
VMPRO product has a dependency on this library,
we need to provide an updated VM provider patch.
PHCO_31059:
( SR: 8606364915 CR: JAGaf25554)
Customer found that VEA didn't show controllers
c4 and c5 connected to their EMC disk array after
installing VxVM 3.5 patches PHCO_29980 and PHKL_29981.
Data structure changes made in PHCO_29980 impacted
the VxVM internal user-level library.Since the VM
provider was not rebuilt using the updated user-level
library, this introduced behavior that caused VEA to
no longer show the host bus adapters under the
"controllers" menu. The fix is to provide an
updated VM provider patch to address this situation.
PHCO_28693:
( SR: 8606310698 CR: JAGae73569)
This patch contains bug fixes for VERITAS Volume
Manager Management Service Provider (VRTSvmpro)
3.5m release distributed with the 0902 OEUR as
reported by different VERITAS point products
using VEA.
Enhancement:
No
SR:
8606310698 8606364915 8606378772 8606405457 8606408697
8606429984 8606478909 8606493872
Patch Files:
VRTSvmpro.VMPRO-PRG,fr=3.5m,fa=HP-UX_B.11.11_32/64,v=HP:
VRTSvmpro.VMPRO-PRG,fr=3.5m,fa=HP-UX_B.11.11_32/64,
v=VERITAS:
/opt/VRTSvmpro/config/vmprov.sh
/opt/VRTSvmpro/config/vxvm.xml
/opt/VRTSvmpro/lib/searchprovider.sl
/opt/VRTSvmpro/lib/vxvmprovider.sl
/opt/VRTSvmpro/extensions/VxVmCE.jar
/opt/VRTSvmpro/extensions/VxVmHelp.en.jar
/opt/VRTSvmpro/extensions/VxSearchCE.jar
/opt/VRTSvmpro/extensions/SearchResourceBundle.en.jar
/opt/VRTSvmpro/extensions/VmLibResourceBundle.en.jar
/opt/VRTSvmpro/extensions/VmResourceBundle.en.jar
/opt/VRTSvmpro/extensions/VxVmOneguiResourceBundle.en.jar
/opt/VRTSvmpro/extensions/VxVmVxFsResourceBundle.en.jar
what(1) Output:
VRTSvmpro.VMPRO-PRG,fr=3.5m,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/VRTSvmpro/config/vmprov.sh:
None.
/opt/VRTSvmpro/config/vxvm.xml:
None.
/opt/VRTSvmpro/extensions/SearchResourceBundle.en.jar:
None.
/opt/VRTSvmpro/extensions/VmLibResourceBundle.en.jar:
None.
/opt/VRTSvmpro/extensions/VmResourceBundle.en.jar:
None.
/opt/VRTSvmpro/extensions/VxSearchCE.jar:
None.
/opt/VRTSvmpro/extensions/VxVmCE.jar:
None.
/opt/VRTSvmpro/extensions/VxVmHelp.en.jar:
None.
/opt/VRTSvmpro/extensions/VxVmOneguiResourceBundle.en.jar:
None.
/opt/VRTSvmpro/extensions/VxVmVxFsResourceBundle.en.jar:
None.
/opt/VRTSvmpro/lib/searchprovider.sl:
None.
/opt/VRTSvmpro/lib/vxvmprovider.sl:
clntipc.c $Date: 2006/01/12 10:56:04 $ $Revision: 1.
17.66.3.4.2 $ PATCH_11.11 (PHCO_34255)
voldctlib.c $Date: 2006/12/06 09:18:51 $ $Revision:
1.5.10.6 $ PATCH_11.11 (PHCO_35815)
dmpapi.c $Date: 2005/06/02 13:39:09 $ $Revision: 1.3
0.66.5.4.4 $ PATCH_11.11 (PHCO_33362)
dg_ops.c $Date: 2006/01/21 09:35:15 $ $Revision: 1.9
.45.1.6.4 $ PATCH_11.11 (PHCO_34255)
volguid_init.c $Date: 2005/06/02 13:41:19 $ $Revisio
n: 1.2.66.1.4.2 $ PATCH_11.11 (PHCO_30850)
cksum(1) Output:
VRTSvmpro.VMPRO-PRG,fr=3.5m,fa=HP-UX_B.11.11_32/64,v=HP:
1918267776 40032 /opt/VRTSvmpro/config/vmprov.sh
3100844488 10262 /opt/VRTSvmpro/config/vxvm.xml
1233177547 1806 /opt/VRTSvmpro/extensions/
SearchResourceBundle.en.jar
2460203814 3707 /opt/VRTSvmpro/extensions/
VmLibResourceBundle.en.jar
58006758 31666 /opt/VRTSvmpro/extensions/
VmResourceBundle.en.jar
2523420144 63977 /opt/VRTSvmpro/extensions/VxSearchCE.jar
2709340135 3026314 /opt/VRTSvmpro/extensions/VxVmCE.jar
303632638 532854 /opt/VRTSvmpro/extensions/VxVmHelp.en.jar
3085888417 1434 /opt/VRTSvmpro/extensions/
VxVmOneguiResourceBundle.en.jar
3206167519 6940 /opt/VRTSvmpro/extensions/
VxVmVxFsResourceBundle.en.jar
4196559073 69632 /opt/VRTSvmpro/lib/searchprovider.sl
901023383 3212928 /opt/VRTSvmpro/lib/vxvmprovider.sl
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_36595
s800: 11.11: PHCO_36595
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_28693 PHCO_31059 PHCO_31203 PHCO_33402 PHCO_34348 PHCO_35827
Equivalent Patches: None
Patch Package Size: 4440 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_36597
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_36597.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_36597. 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_36597.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHCO_36597.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_36597.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
|
