 |
≫ |
|
|
|
パッチ名: PHCO_35890
パッチ摘要: s700_800 11.23 VxVM 4.1コマンドパッチ05
作成日: 07/04/12
公開日: 07/04/17
ハードウェアプラットフォームおよびOSリリース:
s700: 11.23
s800: 11.23
現象:
PHCO_35890:
1.(SR:8606470105 CR:JAGag25246)
Veritas不具合番号: 899646(862878)
vxvmconvertの実行後vxresizeコマンドを実行すると、次のようなエラーメッ
セージが表示されます。
# /opt/VRTS/bin/vxresize -F vxfs -g dg01 lvol1 300m
VxVM vxresize ERROR V-5-1-4283 resizing volume other
than FSGEN or RAID5 can result in loss of data.
Use -f option to force resize this volume.
2.(SR:8606455268 CR:JAGag11831)
Veritas不具合番号: 899675(900203)
/etc/vx/bin/vxbrk_rootmirスクリプトを使って代替ブートディスクを作成し
ようとすると、次のようなエラーメッセージが表示されます。
# /etc/vx/bin/vxbrk_rootmir -v -b c0t0d0
vxbrk_rootmir: 17:19: Checking specified disk(s)
for presence and type
vxbrk_rootmir: 17:19: Mirroring root disk
vxrootmir: 17:19: Gathering information on the
current VxVM root configuration
vxrootmir: 17:19: Checking specified disk(s) for
usability
vxrootmir: 17:19: Preparing disk c0t0d0 as
a VxVM root disk
vxrootmir: 17:19: Adding disk c0t0d0 to rootdg
as DM rootdisk02
vxrootmir: 17:19: Mirroring all volumes
on root disk
vxrootmir: 17:19: Mirroring volume standvol
vxrootmir: 17:20: Mirroring volume swapvol
vxrootmir: 17:25: Mirroring volume rootvol
vxrootmir: 17:26: Mirroring volume optvol
vxrootmir: 17:31: Mirroring volume tmpvol
vxrootmir: 17:31: Mirroring volume usrvol
vxrootmir: 17:34: Mirroring volume homevol
vxrootmir: 17:34: Mirroring volume varvol
vxrootmir: 17:40: Mirroring volume swapvol2
vxrootmir: 17:40: Mirroring volume testvol
vxrootmir: 17:41: Disk c0t0d0 is now a mirrored
root disk
vxbrk_rootmir: 17:41: Saving configuration data
for later restoration
sed: Function s/plex=.*$/plex=swapvol-02
cannot be parsed.
vxbrk_rootmir: 17:41: Breaking off root mirror
on DA c0t0d0
vxbrk_rootmir: 17:41: Setting broken off mirror on
c0t0d0 as unique root disk
vxvm:vxmake: ERROR: duplicate plex, context:
plex swapvol2-02
tutil0="
vxbrk_rootmir: ERROR: Attempting to recreate
volume meta-data on rootdisk02/c0t0d0
3.(SR:8606474302 CR:JAGag28848)
Veritas不具合番号: 899681(641439)
クライアントへのスナップショットの送信中に、vradmindコマンドでコアダン
プが取られます。
4.(SR:8606471971 CR:JAGag26927)
Veritas不具合番号: 960396(855057)
/etc/fstabファイル内に複数のLVエントリを持つVGの変換中に、
vxautoconvertが/etc/fstabファイルを正しくアップデートしません。
5.(SR:8606467094 CR:JAGag22530)
Veritas不具合番号: 927439(832358)
(マイナー番号が)衝突しているdmpメタノードに対してI/Oを実行すると、関連
したアクティブなdmpノードが使用不可になることがあります。次のようなメ
ッセージがsyslogに記録されます。
NOTICE: vxvm:vxdmp: disabled path 31/0x46000
belonging to the dmpnode 1/0x20
NOTICE: vxvm:vxdmp: disabled dmpnode 1/0x20
問題点の説明:
PHCO_35890:
1.(SR:8606470105 CR:JAGag25246)
Veritas不具合番号: 899646(862878)
vxvmconvertユーティリティは、ファイルシステムが存在するかチェックせず
に、FSGENではなくGENタイプのボリュームを作成していました。そのため、
その後に行うGENタイプボリュームのvxresizeがエラーになっていました。
解決方法:
fstabファイル内にファイルシステムのエントリがあるかチェックし、かつ、
fstypコマンドを使ってファイルシステムのタイプを調べるようにコードを修
正しました。
2.(SR:8606455268 CR:JAGag11831)
Veritas不具合番号: 899675(900203)
vxbrk_rootmirスクリプトは、ディスクグループ内の別のボリューム名の副文
字列を持つボリューム名を処理しませんでした。
解決方法:
ディスクグループ内の別のボリューム名の副文字列を持つボリューム名を処理
するようにスクリプトを修正しました。
3.(SR:8606474302 CR:JAGag28848)
Veritas不具合番号: 899681(641439)
VRASのコードは、RDSポインタがNULLでないかチェックせずにRDSオブジェクト
にアクセスしていました。このコードは、vradmindがそのデータベースのスナ
ップショットをVVRプロバイダのようなvradmindクライアントに送信する際に
実行されます。
解決方法:
文字列の長さが64Kを超えていないかチェックし、超えていればエラーを返す
ようにコードを修正しました。これで、メモリー割り当て問題は起きません。
4.(SR:8606471971 CR:JAGag26927)
Veritas不具合番号: 960396(855057)
パラレル変換での論理的な誤りにより、vxautoconvertがエントリを上書きし
ていました。
解決方法:
エントリを必ず追加するように、/etc/fstabエントリをアップデートするスク
リプトを修正しました。
5.(SR:8606467094 CR:JAGag22530)
Veritas不具合番号: 927439(832358)
"vxdctl initdmp"を使ってdmpデバイスツリーを作成する際に、DMPは
/dev/vx/(r)dmp内の既存の、あるいは衝突しているデバイスノードを削除して
いませんでした。そのため、重複した、あるいは無効なdmpメタノードが生じ
ることがありました。その結果、存在しないデバイスに対してI/Oを実行する
と、マイナー番号の衝突により、アクティブなdmpノードが使用不可になるこ
とがありました。また、スライス/パーティションに対してI/Oを実行すると、
無効なデバイスと衝突しているベースデバイスが使用不可になることがありま
した。
解決方法:
vxvmの起動フェーズで既存のdmpデバイスノードをすべて削除し、その後、
"vxdctl initdmp"を使ってノードを再作成するようにコードを修正しました。
これで、dmpデバイスツリー内に重複した無効なデバイスノードが含まれるこ
とはありません。また、無効な、あるいは存在しないサービスパーティション
に対するI/Oはエラーになるので、アクティブなベースdmpノードが使用不可に
なることはありません。
-----------------------------------------------------------------------------
Patch Name: PHCO_35890
Patch Description: s700_800 11.23 VxVM 4.1 Command Patch 05
Creation Date: 07/04/12
Post Date: 07/04/17
Hardware Platforms - OS Releases:
s700: 11.23
s800: 11.23
Products:
VxVM 4.1
Filesets:
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=HP
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=VERITAS
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=HP
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=VERITAS
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=HP
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=VERITAS
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=HP
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=VERITAS
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=HP
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=VERITAS
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=HP
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=VERITAS
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=HP
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=VERITAS
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=HP
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=VERITAS
VRTSvxvm.VXSE,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,v=HP
VRTSvxvm.VXSE,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,v=VERITAS
VRTSvxvm.VXSE,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,v=HP
VRTSvxvm.VXSE,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,v=VERITAS
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,v=HP
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,v=VERITAS
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,v=HP
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,v=VERITAS
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_35890: ABORT
PHCO_35738: ABORT MEMORY_LEAK
PHCO_35476: ABORT HANG PANIC MEMORY_LEAK CORRUPTION
PHCO_34811: ABORT MEMORY_LEAK CORRUPTION
PHCO_33509: ABORT HANG PANIC
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_35890
Symptoms:
PHCO_35890:
(SR: 8606470105 CR: JAGag25246)
Veritas Incident Number: 899646 (862878)
After vxvmconvert, the vxresize command fails
with the following error:
# /opt/VRTS/bin/vxresize -F vxfs -g dg01 lvol1 300m
VxVM vxresize ERROR V-5-1-4283 resizing volume other
than FSGEN or RAID5 can result in loss of data.
Use -f option to force resize this volume.
(SR: 8606455268 CR: JAGag11831)
Veritas Incident Number: 899675 (900203)
When the /etc/vx/bin/vxbrk_rootmir script is
used to create an alternate bootable disk, the
script fails with the following error:
# /etc/vx/bin/vxbrk_rootmir -v -b c0t0d0
vxbrk_rootmir: 17:19: Checking specified disk(s)
for presence and type
vxbrk_rootmir: 17:19: Mirroring root disk
vxrootmir: 17:19: Gathering information on the
current VxVM root configuration
vxrootmir: 17:19: Checking specified disk(s) for
usability
vxrootmir: 17:19: Preparing disk c0t0d0 as
a VxVM root disk
vxrootmir: 17:19: Adding disk c0t0d0 to rootdg
as DM rootdisk02
vxrootmir: 17:19: Mirroring all volumes
on root disk
vxrootmir: 17:19: Mirroring volume standvol
vxrootmir: 17:20: Mirroring volume swapvol
vxrootmir: 17:25: Mirroring volume rootvol
vxrootmir: 17:26: Mirroring volume optvol
vxrootmir: 17:31: Mirroring volume tmpvol
vxrootmir: 17:31: Mirroring volume usrvol
vxrootmir: 17:34: Mirroring volume homevol
vxrootmir: 17:34: Mirroring volume varvol
vxrootmir: 17:40: Mirroring volume swapvol2
vxrootmir: 17:40: Mirroring volume testvol
vxrootmir: 17:41: Disk c0t0d0 is now a mirrored
root disk
vxbrk_rootmir: 17:41: Saving configuration data
for later restoration
sed: Function s/plex=.*$/plex=swapvol-02
cannot be parsed.
vxbrk_rootmir: 17:41: Breaking off root mirror
on DA c0t0d0
vxbrk_rootmir: 17:41: Setting broken off mirror on
c0t0d0 as unique root disk
vxvm:vxmake: ERROR: duplicate plex, context:
plex swapvol2-02
tutil0="
vxbrk_rootmir: ERROR: Attempting to recreate
volume meta-data on rootdisk02/c0t0d0
(SR: 8606474302 CR: JAGag28848)
Veritas Incident Number: 899681 (641439)
The vradmind command results in a core dump
while sending a snapshot to the client.
(SR: 8606471971 CR: JAGag26927)
Veritas Incident Number: 960396(855057)
While converting VGs with multiple LV
entries in the /etc/fstab file, vxautoconvert
does not update the /etc/fstab file correctly.
(SR: 8606467094 CR: JAGag22530)
Veritas Incident Number: 927439(832358)
I/O to a conflicting dmp metanode can lead to
disabling associated active dmpnode with the
following message in the syslog:
NOTICE: vxvm:vxdmp: disabled path 31/0x46000
belonging to the dmpnode 1/0x20
NOTICE: vxvm:vxdmp: disabled dmpnode 1/0x20
PHCO_35738:
(SR: 8606472168 CR: JAGag27068)
Veritas Incident Number: 795130 (795129)
In the MC/SG clustered environment, while
running the 'cmhaltcl' command on the second
or a third slave nodes, one of the Disk Groups
(DG) loses the shared flag, the cluster ID,
and the autoimport flag for all disks in
that DG.
(SR: 8606473669 CR: JAGag28300)
Veritas Incident Number: 831065 (804673)
When the "vxddladm addsupport all" command was
run, it dumped core with the following stack
trace:
#0 0x60000000c4557560:0 in __milli_memcmp+0x6c0 ()
from /usr/lib/hpux32/libvxscsi.sl
#1 0x60000000c4545a30:0 in nv_free+0x60 ()
from /usr/lib/hpux32/libvxscsi.sl
#2 0x402c600:0 in ddl_vendor_info+0x16f0 ()
#3 0x4029e30:0 in ddl_add_support+0x2a0 ()
#4 0x40185a0:0 in vxddl_addsupport+0x2f0 ()
#5 0x4016d50:0 in main+0x12f0 ()
(SR: 8606472173 CR: JAGag27073)
Veritas Incident Number: 833619 (610841)
When the 'vxbrk_rootmir' command is run to break
the mirror, the following error message is displayed:
'VxVM vxbrk_rootmir ERROR V-5-2-4008 rootdg DG
contains more than 1 disk.'
(SR: 8606473664 CR: JAGag28295)
Veritas Incident Number: 836473 (834318)
All the VxVM commands respond very slowly after
running the 'vxdisk scandisks' command repeatedly.
(SR: 8606472172 CR: JAGag27072)
Veritas Incident Number: 839168 (839077)
The 'vxresize' command fails on file systems
greater than 2 TB. This displays the following
error message:
'VxVM vxresize ERROR V-5-1-2605 cannot stat/mnt.'
(SR: 8606472171 CR: JAGag27071)
Veritas Incident Number: 833704 (833700)
Need to increase the maximum I/O Size on a VxVM
volume from 256k to 1MB.
(SR: 8606472174 CR: JAGag27074)
Veritas Incident Number: 844510 (783758)
The vgcreate (1M) fails while converting a VxVM root
disk to LVM root disk using the vxres_lvmroot (1M)
command. This displays the following error message:
"VxVM vxres_lvmroot ERROR V-5-2-1691: vgcreate
failed"
(SR: 8606473668 CR: JAGag28299)
Veritas Incident Number: 851396 (405564)
The vxdiskunsetup (1M) command takes a long time
to complete on large configuration.
PHCO_35476:
(SR: 8606467245 CR: JAGag22669)
Veritas Incident Number: 781473
vxvmconvert is not able to convert some volume
groups correctly. The converter is unable to
recognize and convert extent based volume
groups.
(SR: 8606467112 CR: JAGag22546)
Veritas Incident Number: 790788
Importing a disk group with many cascaded space
optimized snapshots fails with the following error:
"VxVM vxdg ERROR V-5-1-587 Disk group sf04dg: import
failed: No more space in disk group configuration"
(SR: 8606467110 CR: JAGag22544)
Veritas Incident Number: 788674
The vxsnap command executed with an argument
exceeding 100 characters results in the following
error:
"VxVM vxsnap ERROR V-5-1-447 Cannot execute
/usr/sbin/vxassist: Bad address"
(SR: 8606467113 CR: JAGag22547)
Veritas Incident Number: 795046
The "vxsnap -g <dg> print" process uses more than
1GB of memory.
(SR: 8606430187 CR: JAGaf89646)
Veritas Incident Number: 795049
In a mirror-stripe setup, while adding more LUNS
into the configuration and increasing the number
of stripes, if one controller (card in the system
or a controller on the storage or a storage box
itself) is down, then both plexes are disabled.
vxassist(1M) silently transfers the layout from
highly available to non-highly available.
(SR: 8606405601 CR: JAGaf65522)
Veritas Incident Number: 795065
When a mirror-stripe volume that spans across 16
disks (two plexes across 8 disks each) is being
configured, it results in the following errors:
vxvm:vxvol: ERROR: Volume vxvol01: READ error at
block 2147483648:
System error: Bad file number
xvm:vxvol: ERROR: Volume vxvol01: synchronizing
read loop failed, it should
vxvm:vxvol: ERROR: be stopped and restarted
vxvm:vxvol: INFO: Attempting to cleanup after
failure ...
(SR: 8606420552 CR: JAGaf80381)
Veritas Incident Number: 795965
The installation of VxVM fails with the following
NOTICE message in the syslog:
NOTICE: MOD: modld: Module already loaded
PHCO_34811:
(SR:8606445097 CR:JAGag02580)
Veritas Incident No:540604
During diskgroup deport, vxconfigd issues warnings
like:
VxVM vxconfigd WARNING V-5-1-11551 array_da_to_disk:
Cannot find active path for dmpnode EMC0_1 and then
dumps core with the following stack trace :
0xff1344e4 in strlen () from /usr/lib/libc.so.1
0xff186c30 in _doprnt () from /usr/lib/libc.so.1
0xff188960 in fprintf () from /usr/lib/libc.so.1
0x6ca28 in array_select_da ()
0x6c62c in da_select_diskid ()
0x65d18 in da_find_diskid ()
0x64394 in da_dg_deport ()
0x89008 in dg_deport_finish ()
0x88de4 in vold_dg_deport ()
0x85f60 in req_dg_deport ()
0xd1d8c in request_loop ()
0xb063c in main ()
(SR: 8606445098 CR:JAGag02581)
Veritas Incident No:496817
Built-in 4.1 MP1 ASL for HDS 9500 Tagmastore
needs to differentiate from the AMS 500
Tagmastore by serial number.
(SR:8606445099 CR: JAGag02582)
Veritas Incident No:496821
vxasldebug output: Failed to open two
discovery.d libraries:libvxautoraid.sl,
libvxdgc.sl.
Here's a segment showing first open error
on libvxautoraid.sl...
checking ASL library outputs
***********************************************
libvxautoraid.sl
***********************************************
ERROR: Error opening shared library
/etc/vx/lib/discovery.d/libvxautoraid.sl
***********************************************
libvxcscovrts.sl
***********************************************
libvxcscovrts.sl:vendor_info()
VID: CSCOVRTS
PID: MDS9
ANAME: MDS9Series
ATYPE: A/A
ASL_VERSION: vm-4.1-rev-1
libvxcscovrts.key()
ASL Name: libvxcscovrts.sl
Feature Needed : 95
VxVM Version Needed: 41
Device: /dev/rdsk/c10t0d0
Vendor Identification: HITACHI
Product Identification : DF600F
Revision Number: 0000
Serial Number: 750100490059
libvxcscovrts.sl:claim_device(): UNCLAIMED
Device: /dev/rdsk/c10t0d1
Vendor Identification: HITACHI
Product Identification: DF600F
Revision Number: 0000
Serial Number: 75010049005A
libvxcscovrts.sl:claim_device(): UNCLAIMED
(SR: 8606445101 CR: JAGag02584)
Veritas Incident No:540075
Under the following scenario, detached plexes
remain out-of-sync even after recovery. This
may lead to silent data corruption.
1) A volume has 2 or more plexes all of which are
ACTIVE (none is DETACHED).
2) The volume does not have any snapshots.
3) Some of the plexes become unavailable while
multiple I/Os are active on the volume.
4) System crashes after the unavailable plexes are
marked DETACHED but before the DCO captures the
differences between the good and detached plexes.
(SR:8606445103 CR:JAGag02585)
Veritas Incident No: 578954
Need to add on the fly debugging ability to
vxconfigd.
(SR: 8606445105 CR:JAGag02587)
Veritas Incident No:598403
Memory leak on vxnotify.
(SR:8606445109 CR:JAGag02591)
Veritas Incident No:608290
vxasldebug output for EVA8000 (HSV210) gives
an error:
Device : /dev/rdsk/c4t0d1
Vendor Identification : HP
Product Identification : HSV210
Revision Number : 5100
Serial Number : A299AS802LA2
libvxhpalua.sl:claim_device(): CLAIMED
VID : HP
PID : HSV210
CAB_SERIAL_NO : 50001FE150062930
LUN_SERIAL_NO : 600508B400107306000110000391000 0
REVISION : 5100
UDID : HP_HSV210_50001FE150062930_6005
08B4001073060001100003910000
LUN_OWNER : Y
CUR_OWNER : Y
PORT_SERIAL_NO : 50001FE150062939
ANAME : EVA8000
ERROR: vendor_info() VIDs don't match, inquiry
HP vendor_info COMPAQ.
(SR:8606445113 CR:JAGag02595)
Veritas Incident No:496847
In CVM environment, deport of shared disk group
takes lot of time. For example, two node cluster
with shared disk group having 10 disks of a size
1 GB each takes approximately 5 minutes for deport.
(SR:8606445114 CR:JAGag02596)
Veritas Incident No:604299
On account of keeping the major number associations
around after removing a driver package
(feature of HP-UX 11.23), EMC TPD drivers are not
getting cleared from the kernel even when the driver
is actually removed from the system. One can verify the
stale entry by running "lsdev" command as keeping the
major number of associations.
# lsdev | grep emcp
Character Block Driver
114 2 emcp
This gives a notion that VxVM disks are still
controlled by EMC TPD, but actually they aren't.
(SR:8606445117 CR:JAGag02599)
Veritas Incident No:596112
When vxconfigd debug is turned on, diskgroup import
can fail with error.
vxvm:vxdg: ERROR: Disk group sybdg: import failed:
Internal configuration daemon error.
(SR:8606445118 CR:JAGag02600)
Veritas Incident No:603234
In CVM cluster, there is a small window during
shared disk group deport operation on the slave node,
when a command like vxprint could cause vxconfigd
to generate some warnings like:
VxVM vxconfigd WARNING V-5-1-7989 Get of record
testvol from kernel failed:No such file or
directory.
(SR:8606445119 CR:JAGag02601)
Veritas Incident No:577108
Running vxdisksetup on a system with a large number
of luns (more than a thousand) takes very long time.
(SR:8606445120 CR:JAGag02602)
Veritas Incident No:519644
In a Clustered Environment with two arrays attached
to the cluster, a disk group is created spanning
both arrays. Powering off one array with I/Os in
progress, snapshot of a volume residing on one
array to disks on the second array, cause Serial
Split Brain errors like:
VxVM vxdg ERROR V-5-1-10127 associating disk-media
testdg04 with c4t5d0: Serial Split Brain detected.
Run vxsplitlines.
(SR:8606445121 CR:JAGag02603)
Veritas Incident No:521576
False Serial Split Brain hit on master if slave and
one of arrays are brought down together.
(SR:8606445122 CR:JAGag02604)
Veritas Incident No:303628
HP requests that a check is made for the pfto
argument in vxdisk not to be lower than 15s.
(SR:8606445312 CR:JAGag02782)
Veritas Incident No:493411
EVA GL 3000, 5000 disk arrays are not recognized by VxVM.
(SR:8606445313 CR:JAGag02783)
Veritas Incident No:519628
During CVM reconfiguration in a 2-node cluster,
vxconfigd dumps core with the following stack:
------------------------------------------------
strcpy.strcpy() at 0x1001c170
advreq_master(0x2017d7f8)
advreq(0x2017d7f8)
vold_getrequest(0x5)
send_slaves(0x1, 0x2ff225f8, 0x5, 0x0)
master_send_da(0x201aa2a0, 0x2ff22650, 0x1)
vold_dm_as_da(0x2018e220, 0x201aa050,
0x20181df0, 0x8)
req_dm_as_da(0x20181df0, 0x200760b8)
request_loop()
(SR:8606446350 CR:JAGag03724)
Veritas Incident No:565987
In a CVM environment, after disabling the primary
path of a shared disk via
"vxdmpadm disable ctrl=<ctrl_name>" on the CVM master,
I/Os doesn't fail over to the secondary path(s) on CVM
slaves nodes.
(SR:8606446351 CR:JAGag03725)
Veritas Incident No:569033
HP EVA ALUA ASL failed to claim HSV disks with
the following vxconfigd errors:
$ vxdctl enable
"VxVM vxconfigd ERROR V-5-1-8784 disk /dev/rdsk/c92t0d7
can't be claimed - DDL_ERROR hpalua
claim_device: AAS invalid hpalua claim_device:AAS
invalid: Error 0
VxVM vxconfigd ERROR V-5-1-8784 disk /dev/rdsk/c92t0d5
can't be claimed - DDL_ERROR: Error
vxcheckasl or vxasldebug shows
"libvxhpalua.sl:claim_device() : ERROR"
(SR:8606442723 CR:JAGag00460)
Veritas Incident No:618400
System becomes unbootable from EMC8830 if PHCO_33509
installed. The following messages appear while booting:
Starting vxconfigd in boot mode (pre_init_rc).
NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 1/0x0
WARNING: VxVM vxio V-5-0-2 Subdisk ROOT block 82497:
Uncorrectable read error
WARNING: VxVM vxio V-5-0-2 Subdisk ROOT block 224068:
Uncorrectable read error
Synchronous Page I/O error occurred while paging
to/from disk
VxVM vxconfigd ERROR V-5-1-0 Bus error
(SR:8606455828 CR:JAGag12320)
Veritas Incident Number:602717
We have implemented a timeout for vxconfigd such that,
it can timeout if a long time is taken to read private
regions of faulty disks. The timeout value can be tuned
by the user and its usage is given in details in the
man page for vxdctl.
(SR:8606447238 CR:JAGag04585)
Veritas Incident Number:634791
vxdisksetup -iB allows overwriting for the disk
in use by LVM.
(SR:8606455839 CR:JAGag12331)
Veritas Incident Number:612603
For space optimized snapshot, vxsnap does not create
dco on the disk specified in alloc option.
(SR:8606449570 CR:JAGag06724)
Veritas Incident Number:633161
During overlapping CVM reconfigurations, such as a node
join being interrupted by another node leaving the
cluster, vxconfigd times out on any one of the nodes,
which can lead to MCSG halting the node in
ServiceGuard/CFS stack. This problem is reproducible
with internal testing/stress testing. A typical symptom
of this problem is that the kernel thread is spawned by
CVM node id daemon, while in node id protocol, is stuck
on vol_vold_in_join variable to be reset. Typical stack
trace of the kernel thread associated with the symptom
is:
kt_stat: TSSLEEP
kt_cntxt_flags: 0x0
kt_wchan: vol_vold_join_sync+0x8
swtch_to_thread+0x550
_swtch+0x30
real_sleep+0x9e0
sleep_spinunlock+0x1b0
_vol_syncwait+0x4a0
vol_set_membership+0x14c0
volcvm_set_members+0x15b0
kthread_daemon_startup+0x40
kthread_daemon_startup+0x0
swtch_to_thread+0x550
PHCO_33509:
(SR: 8606419256 CR:JAGaf79086)
Doing an ignite_ux install using the VxVM listener
"smapi", sometimes get error that device node
does not exist.
(SR:8606405497 CR:JAGaf65418)
1) Doing an ignite_ux install using the VxVM listener
"smapi" gets an error, if a "system volume" is specified
for a different disk group other than the root disk group.
2) Trying to install VxVM 4.1 rootdg that does not
contain a designated root disk fails.
(SR:8606419263 CR: JAGaf79093)
If a path to a dmpnode was disabled due to a port on a
SAN switch being disabled, it would go to DISABLED state.
Once the port was re-enabled and after waiting for a couple
of seconds (to allow host to redetect the fabric), a
'vxdisk scandisks' or 'vxdctl enable' should bring the
path back to ENABLED state. In this case, the path did
not go to ENABLED state until a few additional
'vxdctl enable' or vxdisk scandisks' were issued.
(SR: 8606419265 CR: JAGaf79095)
Creation of a new diskgroup using 'vxdiskadm' fails with
an error similar to the following one,
if Enclosure Based Naming is used:
VxVM vxislvm ERROR V-5-1-6218 vxislvm:
Cannot stat /dev/rdsk/TagmaStore0_2
VxVM vxislvm ERROR V-5-1-6218 vxislvm:
Cannot stat /dev/rdsk/TagmaStore0_2
VxVM vxdisk ERROR V-5-1-558 Disk dg02:
Disk not in the configuration
(SR: 8606419267 CR: JAGaf79097)
Overlapping reconfigurations during CVM node join
get hung in between and as a result, node's join
get timed out.
(SR: 8606408073 CR: JAGaf67976)
Messages like the following are emitted on the console
in a CVM environment:
"VxVM vxvol ERROR V-5-1-1217 Volume vol is already
started"
(SR: 8606413328 CR: JAGaf73189)
The cvm node join operation takes more than 30 minutes
to join. Therefore it might timeout if there are
many shared disk groups.
(SR: 8606419276 CR: JAGaf79106)
If a volume is mounted on bootdg, then the vxresize
command will fail to work.
# vxresize -g bootdg test1 15m
VxVM vxresize ERROR V-5-1-2741 volume test1:
Disk group is ambiguous.
Specify [-g diskgroup].
(SR: 8606406994 CR: JAGaf66900)
In CVM environment, cluster reconfiguration timed out
due to cvm node join time out.
(SR: 8606419264 CR: JAGaf79094)
Severe performance degradation due to vxplex attach of a
large number of volumes in a clustered environment.
(SR: 8606419266 CR: JAGaf79096)
DMP multipathing does not work as expected with EMC DMX
800 array.
(SR: 8606411927 CR: JAGaf71792)
During a cluster startup, the following message
appears on the console:
VxVM vxconfigd ERROR V-5-1-4109 -1 returned
from volcvm_establish
(SR: 8606419269 CR: JAGaf79099)
When run on an array with the "No Auto Trespass"
feature enabled, the
"vxdmpadm getsubpath dmpnodename=<Name>"
command can hang while getting the dmp subpath
information to display.
(SR: 8606419271 CR: JAGaf79101)
The vxrootmir command complains about not being
able to deal with plexes with an unassociated subdisk
i.e. name of "-".
(SR: 8606419272 CR: JAGaf79102 )
In CVM environment the master takeover
fails at the vxconfigd level join.
(SR: 8606413083 CR: JAGaf72945)
On a two node cluster, during master takeover,
the master fails to import the shared diskgroups.
The following messages are seen in syslog
of the new master:
"V-5-1-5537 AUTOimport-Importing shared disk groups"
"V-5-1-5536 imported 0 shared disk groups"
(SR:8606405567 CR: JAGaf65488)
Once the vxconfigd is started, previously
initialised disks were set to error state.
vxdisk list command confirms the same:
DEVICE TYPE DISK GROUP STATUS
c4t2d0 auto:hpdisk - - error
(SR: 8606419808 CR: JAGaf79638)
Need to make commands sent to other nodes in a cluster
use cmexec when SG is involved in cluster management.
(SR: 8606408077 CR: JAGaf67980)
Commands that receive/send information from the
vxconfigd process, e.g. vxprint, can get an
error message like:
"Configuration daemon is not accessible"
(SR: 8606419813 CR: JAGaf79643)
After forcibly unloading glm DLKM module,
if a user tries to start cvm as a part of a
cluster startup, the cluster command or script
returns success but fails to start cvm.
(SR: 8606419815 CR: JAGaf79645)
vxvol coredumps while trying to get the dg
configuration objects.
Stack trace is as follows:
#0 0x4087410:1 in get_srcvols at comstart.c:6548
#1 0x4065e80:0 in common_start_resync at comstart.c:293
#2 0x4065a40:0 in do_start at comstart.c:205
#3 0x4047e40:0 in main
(SR: 8606419816 CR: JAGaf79646)
vxdisk resize hangs.
Stack trace is as below:
bmap_test() + 18
priv_update_toc() + 318
priv_resize() + 794
da_resize_common() + 1dc
auto_disk_op() + 7c
vold_disk_resize() + d8c]
req_disk_resize() + 108
request_loop() + 8e4
main() + c1c
(SR: 8606419818 CR: JAGaf79648)
Serial Split Brain during vxdg adddisk on an imported
disk group.
(SR: 8606419820 CR: JAGaf79650)
Panic during a dco update on a NPFMR-2 snapshot
while firing I/Os to that snapshot for a volume
which also has PFMR-3 snapshot associated with it.
Stack trace is as below:
voldco_needupdate_instant+0x10
voldco_needupdate+0x30
volfmr_needupdate - frame recycled
vol_mv_write_start+0x17c
volkcontext_process+0x518
volkiostart+0x7f0
vxiostrategy+0xa8
bdev_strategy+0x90
ufs_putsummaryinfo+0x140
logmap_roll_dev - frame recycled
ufs_flush+0x1c8
ufs_unmount+0x1cc
dounmount+0x54
umount2+0x188
syscall_trap32+0xa8
(SR: 8606419821 CR: JAGaf79651)
IO errors while accessing a filesystem that disabled.
The log file syslog.log has SCSI write errors as well
as VxVM vxio errors, like:
WARNING: VxVM vxio V-5-0-2 Subdisk c4t0d0-01
block 1139762: Uncorrectable write error
The problem happens only if SCSI PGR keys are used.
(SR: 8606419822 CR: JAGaf79652)
vxsnap fails to take snapshots of a volume
in a shared DG and dumps core.
Stack trace follows:
#0 0x4147850:0 in real_free+0x2f0 ()
#1 0x41474d0:0 in _free+0x90 ()
#2 0x4152f70:0 in free+0x1d0 ()
#3 0x4093430:0 in vol_freeze_cluster at vxfsfreeze.c:400
#4 0x405fe40:0 in sync_volumes at fsgensync.c:196
#5 0x405e2c0:0 in do_snapsync at volume.c:5089
#6 0x4048440:0 in main at volume.c:402
(SR:8606423407 CR:JAGaf82930)
The new ASL for emc library doesn't get claimed
with all SYM 5x71 devices(<8k and >8k LUN's)
due to the error by VM because of
"ERROR: check_nvlists: Claiming error LUN_SER_NO
not specified".
(SR:8606423408 CR: JAGaf82931)
vxconfigd invokes an uninitialized function pointer in
the DDL static library resulting in a core dump.
The stack trace looks like the following:
#1 ddl_vendor_select_device volddl_claim.c:3881
#2 array_select_da () at daselect.c:171
#3 da_select_diskid () at daselect.c:101
#4 da_find_diskid() at da.c:5556
#5 dg_join_disks() at dgimport.c:3771
#6 dg_import_internal() at dgimport.c:1070
#7 req_dg_import() at dgimport.c:727
#8 request_loop () at request.c:488
#9 main() at main.c:534
(SR:8606423409 CR: JAGaf82932)
In a configuration where both swapvol(SWAP)
and dumpvol(DUMP) are separate, results in error.
Prior to the smapi version of ignite_UX (RA0509),
this configuration could be created without any error.
But with the smapi version of IUX,
we see the following error message:
ERROR: MAKE_BOOT: Volume dumpvol does not
contain a file system.
* smapi listener returned "ACTION_FAILURE"
for message "MAKE_BOOT"
(SR:8606423414 CR:JAGaf82937)
An harmless error message occurred when trying to
halt a one node cluster in CVM environment.
ERROR message:
VxVM ERROR V-5-2-0 VOLCVM_GET_NIDMAP failed
(SR:8606423411 CR: JAGaf82934)
In CVM environment, one of the vxconfigd utility
namely vxvol keeps forking child vxvol during
volume resynchronization. It leads to a standstill
of operations performed on shared disk groups.
Stack trace looks like the following:
#0 _wait_sys+0x10 ()
#1 wait+0x48 ()
#2 wait_readloop()
#3 fork_readloop()
#4 call_readloop ()
#5 common_start_resync()
#6 do_start ()
#7 main ()
(SR:8606423410 CR: JAGaf82933)
In CVM environment vxconfigd dumps core
when a gab write happens as a result,
the node id map is not getting updated
at vxconfigd level.
Stack trace looks like the following:
#0 mknod+0x18 () from /usr/lib/libc.2
#1 srand+0x4c () from /usr/lib/libc.2
#2 __hpmfcobol_strcoll_sb+0x118 ()
from /usr/lib/libc.2
#3 audit_daemon+0x8 () from /usr/lib/libc.2
#4 srand+0x4c () from /usr/lib/libc.2
(SR: 8606423412 CR: JAGaf82935)
DDL doesn't claim EVA 4k,6k LUNs in HPUX.
(SR: 8606419810 CR: JAGaf79640)
Veritas Storage Expert rules are not working.
# /opt/VRTS/vxse/vxvm/vxse_stripes2 info
/usr/lib/dld.sl: Can't open shared library:
/net/prague/u2/sap/nightly/obdev/hp/lib/libvxapi.sl
/usr/lib/dld.sl: No such file or directory
ABORT instruction (core dumped)
(SR: 8606419803 CR: JAGaf79633)
Cumulative VVR fixes
1)Veritas Incident Number:426233
vxmake rlink command fails with the following
error:
" could not get local host name "
2)Veritas Incident Number:415076
vradmin repstatus command can show blank
value for "Logging to:" field in some situations
3)Veritas Incident Number:415078
vradmind daemon may hang if there are more
than 256 volumes under RVG.
Defect Description:
PHCO_35890:
(SR: 8606470105 CR: JAGag25246)
Veritas Incident Number: 899646(862878)
The vxvmconvert utility does not check for file
system existence and creates volumes of GEN type
instead of FSGEN. Subsequently, the vxresize of
a GEN type volume fails.
Resolution:
The code has been modified to check for the
existence of the file system in the fstab file,
as well as by using the fstyp command.
(SR: 8606455268 CR: JAGag11831)
Veritas Incident Number: 899675(900203)
The vxbrk_rootmir script does not handle volume
names with a substring of another volume name in
a disk group.
Resolution:
The script has been modified to handle volume names
with a substring of another volume name in a disk group.
(SR: 8606474302 CR: JAGag28848)
Veritas Incident Number: 899681(641439)
In the VRAS code, a RDS object
is accessed without checking if the RDS pointer
is not NULL. This code is executed when vradmind
sends a snapshot of its database to a vradmind client such
as VVR provider.
Resolution:
The length of the string is checked, and an error
is returned for lengths exceeding 64k.
This is done to avoid memory allocation problem.
(SR: 8606471971 CR: JAGag26927)
Veritas Incident Number: 960396(855057)
Due to a logical error in parallel conversion,
the entries are being overwritten by vxautoconvert.
Resolution:
The script which updates the /etc/fstab
entry has been modified to ensure that the
entries are appended.
(SR: 8606467094 CR: JAGag22530)
Veritas Incident number: 927439(832358)
When DMP builds its device tree through 'vxdctl initdmp',
it does not remove any existing or conflicting device
nodes in /dev/vx/(r)dmp. This can lead to duplicate or
stale dmp metanodes. An I/O to a non-existent device can
further cause the existing dmp node to disable due to
conflicting minor numbers. Also, the I/Os on
slice/partitions can end up disabling base devices that
conflict with stale devices.
Resolution:
The code has been modified to cleanup all existing dmp
device nodes during vxvm-startup phase and let
'vxdctl initdmp' recreate the nodes. This ensures that
no pre-existing stale device nodes are present in the
dmp device tree. Also, I/Os on the stale or non-existent
service partition are failed to avoid disabling of the
active base dmpnode.
PHCO_35738:
(SR: 8606472168 CR: JAGag27068)
Veritas Incident Number: 795130 (795129)
After the master node goes down, one of the
slave nodes takes over the responsibility
of the master node. This is known as
Master-Takeover operation. The shared DG
reimport occurring as part of the
Master-takeover operation on the slave node
at the userland (vxconfigd) level coincides
with the node abort signal from MC/SG. It
results in the cleaning-up of the shared DG
from the vxio kernel while vxconfigd still
trying to reimport this DG. Because of
this, vxconfigd encounters errors while
attempting kernel ioctl operation on the
DG. The Master-takeover code cannot handle
the ioctl error conditions that occur during
the shared DG reimport. The ioctl can fail
either due to the ENOENT (No such file or
directory) error or due to the EINTR
(interrupted system call) error during the
shared DG reimport.
Resolution:
The error-handling for the EINTR error is
introduced in the Master-takeover operation
code. The Master-takeover operation can now
handle both the ENOENT and EINTR kernel ioctl
failures.
(SR: 8606473669 CR: JAGag28300)
Veritas Incident Number: 831065 (804673)
No memory was allocated to nvlist structure in
the ddl_vendor_info()routine. Later a free()
was done on this, which was not required. This
causes a free() operation on a wrong address
and, as a result, vxconfigd dumps core.
core dump.
Resolution:
Redundant call to free nvlist has been removed.
(SR: 8606472173 CR: JAGag27073)
Veritas Incident Number: 833619 (610841)
There was a logical error in the vxbrk_rootmir
code while calculating the number of disks that
do not have all the volumes of the root disk.
This occurs because all the mirrors of the VxVM
root disk are not taken into account.
Resolution:
All mirrors of the boot disk are taken into
account while calculating the number of disks
that do not have all the volumes of the root
disk.
(SR: 8606473664 CR: JAGag28295)
Veritas Incident Number: 836473 (834318)
The licensing code reallocates some of the
structures without freeing the old ones.
This leads to a memory leak in vxconfigd
daemon.
Resolution:
Memory allocation for the structures is done
only after verifying that the memory for those
structures is freed.
(SR: 8606472172 CR: JAGag27072)
Veritas Incident Number: 839168 (839077)
The vxresize (1M) command uses statvfs (2) system
call to obtain the file system information.
The file systems that are greater than 2TB
in size cause an overflow in the "statvfs"
structure fields.
This can be verified by the tusc traces on
vxresize process, which shows EOVERFLOW error.
Resolution:
Use the 64 bit version of statvfs(), that is,
statvfs64(), to obtain the information about
the mounted file systems.
(SR: 8606472171 CR: JAGag27071)
Veritas Incident Number: 833704 (833700)
VxVM I/Os are limited by MAXIOSIZE, which is
currently set to 256Kb for HP-UX. This limit
is based on the old MAXPHYS definition. There
is a tunable, vol_maxio, to set the maximum IO
size but it is ignored for any value over 256Kb.
Physical I/Os can be up to 1MB in size.
MAXIOSIZE should be changed to allow 1MB I/Os.
Resolution:
Increase the MAXIOSIZE to 1MB. This change also
entails a change in the default value of
vol_maxspecialio that governs the maximum I/O
size of an IOCTL from 256k to 1024k.
(SR: 8606472174 CR: JAGag27074)
Veritas Incident Number: 844510 (783758)
If the original size of a physical extent is
small enough while creating the VG, the number
of physical extents (PEs) in a VG exceeds its
maximum value that results in this problem.
Resolution:
Run the vgcreate(1M) with the next power of
2 PE size if it is determined that the failure
is due to exceeding maximum number of PEs.
(SR: 8606473668 CR: JAGag28299)
Veritas Incident Number: 851396 (405564)
The last command used prior to the normal exit in
vxdiskunsetup (1M) was the "vxdisk -a online" command.
This command brings all the disks online, which
makes it slow. vxdiskunsetup (1M) performs the
'vxdisk online <disk>' command within its processing
loop after removing the VxVM partitions. So, the
'vxdisk -a online' command is redundant and should
be removed.
Resolution:
The call to the redundant command "vxdisk -a online"
has been removed from the vxdiskunsetup (1M) command.
PHCO_35476:
(SR: 8606467245 CR: JAGag22669)
Veritas Incident Number: 781473
Problem Description:
The "vg_timestamp" field was removed from the LVM
private structure. vxvmconvert was using this field
to identify the latest copy of the configuration.
Without this value vxvmconvert may use an outdated
configuration which may lead to corrupted/incomplete
volume Group.
Resolution:
Instead of using the LVM private structure, the
command line interfaces (vgdisplay/lvdisplay/pvdisplay)
are now used to obtain the information the converter
needs to accomplish the conversion. Using the LVM
command line interfaces also enables identification
and conversion of extent based volume groups (if
the configuration fits into a valid VxVM disk group
configuration).
(SR: 8606467112 CR: JAGag22546)
Veritas Incident Number: 790788
Problem Description:
While creating the temporary database, the DCO
blocks were not being considered for space
allocation resulting in the error.
Resolution:
The code has been modified to ensure that the
DCO blocks are considered when space is
allocated for creating the temporary database.
(SR: 8606467110 CR: JAGag22544)
Veritas Incident Number: 788674
Problem Description:
The maximum size of the argument allowed in vxsnap
was fixed to 100 characters. This resulted in an
overflow if the argument exceeded the set limit.
Resolution:
The problem has been resolved by ensuring
that the maximum size of argument to vxsnap
is now dynamically allocated.
SR: 8606467113 CR: JAGag22547)
Veritas Incident Number: 795046
Problem Description:
There were many memory leaks in the functions
printfmr3(), getsnaplist(), do_print_vols(),
print_mapinfo() and vol_getformat().
Resolution:
The code has been modified to fix the memory
leaks.
(SR: 8606430187 CR: JAGaf89646)
Veritas Incident Number: 795049
/Problem Description:/
The main defect found in this customer case is
that "mirror=ctlr"/"mirror=target" are broken
and do not provide a HA layout following relayout.
Resolution:
The code has been modified to switch the order in
which temporary storage (used by the relayout
operation to create TMP configuration records)
and real storage are allocated. The way columns
are expanded through relayout_expand_column() has
also been reordered.
(SR: 8606405601 CR: JAGaf65522)
Veritas Incident Number: 795065
Problem Description:
The resync of volumes consisting of more than a
single plex was failing after a 2TB offset. An
error was encountered while configuring a
mirror-stripe volume that spanned across 16 disks
(two plexes across 8 disks each). The total volume
size was less than 16TB. This resulted in the loss
of information when 64 bits were converted to 32
bits.
Resolution:
The code has been modified to use appropriate
type casting so that the error is avoided.
(SR: 8606420552 CR: JAGaf80381)
Veritas Incident Number: 795965
Problem Description:
During the VxVM installation, when a module was
loaded in the OS, VxVM was not checking the prior
existence of the module. If the module existed, the
installation would fail with a NOTICE message being
written to the syslog.
Resolution:
The code has been modified to ensure that VxVM checks
for prior existence of a module before it is loaded
in the OS.
PHCO_34811:
(SR:8606445096 CR:JAGag02579)
Veritas Incident Number:496405
Problem Description:
ASL is returning UNCLAIMED instead of SKIPPED.
So the disk is claimed under JBOD.
Resolution:
Corrected the string comparison in claiming
device function of the ASL.
(SR:8606445097 CR:JAGag02580)
Veritas Incident Number:540604
Problem Description:
Few of the disks on customer's system were ending
up with duplicate disk ids. Segmentation fault occurred
while vxconfigd was processing a disk group deport
request. If there was no ASL on the system and the disks
were just mirrors of each other, then the duplicate disk
id detection code merely reports about the duplicate
disks and returns back NULL (no device selected).
Resolution:
If any STD device is offline, warning message will be
printed as:
"VxVM vxconfigd WARNING V-5-1-11551 array_da_to_disk:
Cannot find active path for dmpnode EMC0_1".
The diskgroup deport operation continues to finish.
However if the EMC BCV is offline and STD device is
online for which the part of this DG, the duplicate
diskid selection code will not be entered. So no
problem can be encountered.
(SR: 8606445098 CR:JAGag02581)
Veritas Incident Number:496817
Problem Description:
Built-in ASL for HDS 9500 Tagmastore needs to
differentiate from the AMS 500 Tagmastore by Serial
number, though both use HDS' DF600 controller. The
built-in ASL simply recognizes the DF600 Product ID,
and displays it as a 9500 array controller.
Resolution:
Changed the HDS ALUA ASL to differentiate between
HDS9500V and AMS/WMS series based on serial number.
(SR:8606445099 CR: JAGag02582)
Veritas Incident Number:496821
Problem Description:
ASL is returning UNCLAIMED.
Resolution:
Corrected the string comparison, in claiming device
function of the ASL.
(SR: 8606445101 CR: JAGag02584)
Veritas Incident Number:540075
Problem Description:
DCO fails to capture all differences between good
plexes and detached plexes in this particular
scenario.
Resolution:
Capture all the differences between good and
unavailable plexes before marking any plex DETACHED.
If the system crashes after the plex is marked
DETACHED then it will be properly recovered since
DCO has information about all the differences between
the good and DETACHED plex. If the system crashes before
an unavailable plex is marked DETACHED, recovery will
use DRL, if one exists, or complete plex resynchronization.
(SR:8606445103 CR:JAGag02585)
Veritas Incident Number:578954
Problem Description:
Need to set debugging level on the fly i.e without having
to stop vxconfigd. The syntax for switching on or off
debugging is:
vxdctl debug 0-9 [file], 0 turns off debugging.
Resolution:
Add a vxconfigd operation to address such requests.
(SR: 8606445105 CR:JAGag02587)
Veritas Incident Number:598403
Problem Description:
The notify note or notification event received from vold
is returned back to the caller. Its allocated memory is
expected to be freed by the caller. This was not happening
in some cases.
Resolution:
Free the note in all cases.
(SR:8606445109 CR:JAGag02591)
Veritas Incident Number:608290
Problem Description:
vxcheckasl was not handling multiple VIDs properly.
Resolution :
Loop through the vendor id list and check for a match.
(SR:8606445113 CR:JAGag02595)
Veritas Incident Number:496847
Problem Description :
Once the deport of disk group is over on master node,
the control message SLAVE_DISK_OP_NOTIFY is issued to
all slaves nodes separately for each of their DA records.
This, in turn, triggers a da_reonline_all_disks() on the
slaves, thereby delaying the execution of vxconfigd on
the slave side. Even on the master side, subsequent
vxconfigd operations does get impacted and finally the
cascading effect brings about a huge latency in deport
operation.
Resolution :
After the deport of disk group in master node, a single
control message SLAVE_DISK_OP_NOTIFY is issued for all
the Disk Access records rather than one for each record.
(SR:8606445114 CR:JAGag02596)
Veritas Incident Number:604299
Problem Description :
The detection of the existence of third party driver
(TPD) is based on the output of lsdev command which
resulted in a stale entry even after removing the
module from the system. So the detection of TPD's
should be done at the kernel level to verify whether
it is loaded rather than invoking user level lsdev
command.
Resolution:
kcmodule(1M) command is used to check for the presence
of the TPD driver.
(SR:8606445117 CR:JAGag02599)
Veritas Incident Number:596112
Problem Description:
The global error number - errno, used to interpret the
status of the configuration ioctls could unexpectedly
change on the way of the completion of the ioctl when
vxconfigd is operating in debug mode. In the ioctl
debugging code, one of the system calls failure may
bring about the change in the global errno.
Resolution:
Before the ioctl debug info printing code, save the
error value immediately after the ioctl completion,
and use this value to report the ioctl status.
(SR:8606445118 CR:JAGag02600)
Veritas Incident Number:603234
Problem Description:
A shared deport involves first unloading the disk group
objects from the kernel and then performing a deport at
the vxconfigd level. There is a small window between
the unloading of the disk group and prior to vxconfigd
level deport wherein any attempt to fetch the kernel
records for the disk group objects on the slave could
result in "Get of record failed" warnings. These are
harmless warnings that can be ignored as the kernel
objects are genuinely not available in that small
window.
Resolution:
Warnings are skipped for the shared disk group deport
operation by the slave node.
(SR:8606445119 CR:JAGag02601)
Veritas Incident Number:577108
Problem Description :
Found that we were doing a vxdisk scandisks command
each time we executed this script. This takes a long
time on a large configuration. There is no need to do
the vxdisk scandisks, if an autoconfig DA record already
exists for the disk that is being initialized.
Resolution:
Check if an autoconfig DA record exists first before
doing the vxdisk scandisks. If it does exist, then we can
skip doing the vxdisk scandisks operation and running
vxdisksetup will take less than a second.
(SR:8606445120 CR:JAGag02602)
Veritas Incident Number:519644
Problem Description:
The problem is in the function which increment SSBs
on private regions and DM records of all disks that
are online. It was not doing the undo of the private
region ssb_actualid increment after priv_change_header
failures.
Resolution:
Undo Serial Split Brain updates for private region
update failures.
(SR:8606445121 CR:JAGag02603)
Veritas Incident Number:521576
Problem Description:
The disconnecting of the array causes dmp to disable
paths/dmpnodes corresponding to the unavailable disks.
vxconfigd receives a signal and in the ensuing
processing, it tries to increment actual and expected
SSB ids. However, if the slave also dies at this
stage, the increment of expected SSB id will fail as
the transaction fails with VE_CLUSTER error.
Subsequently when the surviving master nodes tries to
form a single node cluster, again it traverses the
same code path to increment the SSB ids. Both the
expected & actual SSB ids will now be incremented by 1.
But there's already a lag between expected & actual SSB
ids, which leads to a false SSB hit.
Resolution:
Handle VE_CLUSTER error and skip incrementing actual SSB
id again so that actual & expected SSB ids are same again
at the end of cluster reconfiguration.
(SR:8606445122 CR:JAGag02604)
Veritas Incident Number:303628
Problem Description:
The FC/SCSI stacks (particularly the former) requires
a minimum of 15 seconds to ensure events are handled
correctly. The pfto argument of vxdisk therefore needs
to ensure the value is no lower than 15.
Resolution:
Introduced a check so that vxdisk pfto value is not
accepted as lower than 15.
(SR:8606445312 CR:JAGag02782)
Veritas Incident Number:493411
Problem Description:
Connect EVA GL array with following VID/PID
=========================================
Spec on EVA GL AA. VID, PID and behavior
EVA 3000 AA: VID= HP; PID = HSV101
EVA 5000 AA; VID= COMPAQ; PID = HSV 111
=========================================
to the system, and DDL layer in vxconfigd has no
information about the above VID/PID pair to
claim the device.
Resolution:
Added support to the above array in our DDL layer.
(SR:8606445313 CR:JAGag02783)
Veritas Incident Number:519628
Problem Description:
When slave node tries to communicate with master node,
it register its node-id on master for further
communication. The problem is that the node-id is
not getting registered properly, which resulted in
core dump.
Resolution:
Register the node-id of all the slave nodes in master
when CVM is coming up. Also, check for possible empty
contents while receiving the message from slave.
(SR:8606446350 CR:JAGag03724)
Veritas Incident No:565987
Problem Description:
Such disabling/enabling of DMP paths in a CVM
environment was not supported previously.
Resolution:
Add support for disabling/enabling of DMP paths in
a CVM environment.
(SR:8606446351 CR:JAGag03725)
Veritas Incident No:569033
Problem Description:
HP EVA ALUA ASL expects the vendor ID (VID) for the
EVA disks should be COMPAQ when in fact it is HP.
Resolution:
Fix the ASL to accept HP as the VID for HSV disks.
(SR:8606442723 CR:JAGag00460)
Veritas Incident Number:618400
Problem Description:
There is a bug in the 4.1 Patch1 that got released
w.r.t EMC arrays as the Mask bit that is responsible
for claiming the arrays got included in the libvxemc.sl
binary but unfortunately the vxconfigd binary(Static)
did not include these changes. This is the reason
behind EMC Arrays not getting claimed or
not getting booted with EMC's bootable disks.
It's not a source change, just that the building of
binaries are not done correctly.
Resolution:
Correct static vxconfigd binary was built and included
in 4.1 Cp2.
(SR:8606455828 CR:JAGag12320)
Veritas Incident Number:602717
Problem Description:
The availability of vxconfigd is necessary for most
of the vxvm utilities. If vxconfigd doesn't respond
then these utilities will hang. One major reason for
unavailability of vxconfigd is due to I/O hangs. I/O
hangs can happen with the misbehavior of disk drivers
in the system. vxconfigd usually waits in the kernel
for I/O completion, and if that I/O hangs, then
vxconfigd will be stuck in the kernel forever. So, an
I/O hang can make vxconfigd and vxvm utilities unusable.
Resolution:
This problem can be solved if vxconfigd initiated I/Os
timeout automatically. Fortunately most of the I/O waits
for vxconfigd happens in vxio module. So we can have some
control on these I/O waits. In case vxconfigd comes out,
without waiting for the I/O completion, the corresponding
operation will fail or abort, and it should abort in a
clean way.
(SR:8606447238 CR:JAGag04585)
Veritas Incident Number:634791
Problem Description:
The vxdisksetup script just checks for the valid primary
partition on the disk. It does not fail for the disk not
having valid primary partition even if the disk is under
control of LVM.
Resolution:
The format of the disk is checked before taking the
disk under vxvm control.
(SR:8606455839 CR:JAGag12331)
Veritas Incident Number:612603
Problem Description:
The user specified options are not copied properly in
the structure which contains attributes.
Resolution:
Copied the user supplied attributes into the attribute
structure.
(SR:8606449570 CR:JAGag06724)
Veritas Incident Number:633161
Problem Description:
If an overlapping reconfiguration, say a node leave, is
delivered when a join operation is in progress, the join
is expected to be aborted, node leave processing should be
completed and then join processing resumes. If such an
overlapping reconfig is delivered when the join is in vold
level, then vxconfigd does not clean up correctly and does
not abort the existing reconfig. Thus, vol_vold_in_join
is not reset. This leads to a subsequent reconfig waiting
forever in the kernel for this variable to be reset and
vxconfigd part of the reconfig finally times out.
Resolution:
If an overlapping reconfig is delivered in kernel, and
the current reconfig is in vold level, a special signal
is sent to vxconfigd, which in turn cleans up vold level
context associated with the existing reconfig and also
gets into kernel and aborts the current reconfig. This way
vol_vold_in_join is reset and subsequent reconfigs are
allowed to proceed.
PHCO_33509:
(SR: 8606419256 CR:JAGaf79086)
Veritas Incident Number:361769
Problem Description:
Device nodes in /dev/rdsk may not exist in ramdisk
FS, if the device that was selected was not a dmpnode
(i.e. not the device path with the highest controller
number).
Resolution:
Add routine to search the ignite_ux supplied
hw.info file for a match on the dmpnode name
of the specified device. Use the included HW path
to run an insf command to generate the required
device nodes in the ramdisk FS.
(SR:8606405497 CR:JAGaf65418)
Veritas Incident Number:370210
Problem Description:
1). If we encounter other disk groups with the same
name as the root disk group, we will deport the other
disk group. But in this case, it was not the root
disk group that contained the volume that the /var
file system was to be mounted on (e.g.rootdg1/varvol).
2). Found that we were always looking for a "rootdisk"
specification when creating rootdg.
Resolution:
1). Extend the policy of deporting disk groups that were
found with the reserved volume name to include non-root
disk groups.
2). Allow a rootdg to be created without a rootdisk
specification. In this case, use the first "disk"
specification to init the rootdg disk group with.
(SR:8606419263 CR: JAGaf79093)
Veritas Incident Number:374273
Problem Description:
After a switch port was disabled, the DMP path to it
(called as cur pri path) failed which resulted in DMP
failover to other port of the array. When such failover
happens the arrays sets a unit attention condition for
all initiators to notify them of a failover. If there is a
unit attention for any initiator set by an array, any
SCSI command other than an inquiry would fail with the check
condition status of unit attention. In our case due to a
unit attention, the RTPG command issued by ASL
failed which resulted in a device being UNCLAIMED
even though it was accessible. The device gets claimed
after a couple or more discovery commands because the unit
attention condition gets cleared after the data is
transferred to an initiator during failed SCSI command.
Resolution :
The fix was to retry the SCSI command if during a discovery
it was found failing with a unit attention status.
(SR: 8606419265 CR: JAGaf79095)
Veritas Incident Number:374371
Problem Description:
vxislvm is used to find out if the disk, which is being
initialized by vxdisksetup is already under LVM control. If
it is, we do not touch that. When Enclosure based naming
scheme is enabled, vxislvm expects an entry like
TagmaStore0_2 to be present in /dev/rdsk. Since this is a
VxVM generated name, it will not exist in /dev/rdsk.
It will be present in /dev/vx/rdmp only and
hence stat call fails on /dev/rdsk/ name.
Resolution :
Modify vxislvm to use dmpnode(entry in /dev/vx/rdmp)rather
than /dev/rdsk entries.
(SR: 8606419267 CR: JAGaf79097)
Veritas Incident Number:380327
Problem Description:
Due to a timing issue, the joinp structure of the cvmkernel
was not getting updated with the right state and as a
result, overlapping reconfiguration got hung.
Resolution:
Cleanly update the flag when aborting the current
reconfiguration to move on to the next one.
(SR: 8606408073 CR: JAGaf67976)
Veritas Incident Number:390570
Problem Description:
If a volume is started and we attempt to start it again,
a message saying that the "volume is already started"
is emitted. This message is an informational message and
should not be tagged as an error. Also, if different
disk groups have volumes with the same name it will be
difficult to distinguish for which
volume, the message has been emitted.
Resolution:
The message is now tagged as an INFO instead of an error.
Also, the name of the diskgroup, to which
the volume belongs, is printed.
(SR: 8606413328 CR: JAGaf73189)
Veritas Incident Number: 412680
Problem Description:
During vxconfigd level join when the dg is imported
the reonline of all disks is done which causes a
delay in dg import
Resolution:
reonline of disks should only be done when needed.
Thus a new check is in place in sliced_dg_join()
which does online/offline only if it is required.
(SR: 8606419276 CR: JAGaf79106)
Veritas Incident Number: 413980
Problem Description:
Let's say bootdg points to rootdg. There was an
ambiguity check while doing resize, which would find
the volume to be a part of rootdg and thus would
prevent vxresize on bootdg.
Resolution:
The fix is to allow vxresize on a bootdg if bootdg is
pointing to another dg.
(SR: 8606406994 CR: JAGaf66900)
Veritas Incident Number:414287
Problem Description:
1. Bug in advresp() due to which the vold used to
wait for 5 or 10 minutes doing nothing.
2. Extra da_reonline_all_disks in mode.c
3. Extra da_reonline during the join of the nodes.
Resolution:
Make sure that the check is moved from advresp() to
advresp_master() for peer clients. Extra da_reonlines
were removed to decrease the join times.
(SR: 8606419264 CR: JAGaf79094)
Veritas Incident Number:414387
Problem Description:
For large VxVM configuration involving large number
of volumes in CVM, plex resyncs take days to complete.
Oracle takes hours to come up.During this time any
VM commands tend to hang.The problem occurs when a
full resync is initiated.
Resolution:
This was a vxrecover fix given with the intention of
having slow=<IODELAY> option incorporated into the
/etc/default/vxrecover file, so that vxrecover uses
this during reboot(persistent). As a result of
this flag, the I/O load was reduced by pausing between
resyncs, which also brought down the ilock msg
load on the kmsg subsystem.
(SR: 8606419266 CR: JAGaf79096)
Veritas Incident Number: 414391
Problem Description:
When the vxcheckasl utility is run on the emc
shared library the lun serial number field
results in blank space and
check_nvlists results in error.
Resolution:
It is resolved by passing the correct pointer
to an emc lun id. Thereby vxvm does the correct
multipathing of array disks and
DMX luns show the correct LUN number.
(SR: 8606411927 CR: JAGaf71792)
Veritas Incident Number:414690
Problem Description:
The problem was that the join operation was retried
and the error message was printed.
Resolution:
Changed message type to informational.
(SR: 8606419269 CR: JAGaf79099)
Veritas Incident Number:414807
Problem Description:
dmp_getsubpaths() is calling the library
routine VOL_PART_IS_OS_PART() on the subpath that
is locked out. Therefore IO directed at this
subpath hangs and is eventually timed out.
Resolution:
Remove the call to VOL_PART_IS_OS_PART() in
dmp_getsubpaths() as well as dmp_get_whole_disk()
since it is not needed in both places.
(SR: 8606419271 CR: JAGaf79101)
Veritas Incident Number: 414808
Problem Description:
The problem was that there was an unassociated
subdisk in the configuration i.e. name of "-".
This caused the expression used, to pick up the
volumes to be mirrored having the name of "-" which
it need not.
Resolution:
Ignore volume names which are entirely "-".
(SR: 8606419272 CR: JAGaf79102)
Veritas Incident Number:416282
Problem Description:
The new master gets 2 VOLOP_CONNECT from the
joiner and hence gets confused. It thinks
that the slave is out of sync with the master
and hence stop the processing of the join.
Resolution:
Make sure that VOLOP_CONNECT on the slave
is not sent from the free_stale_client() context.
(SR: 8606413083 CR: JAGaf72945)
Veritas Incident Number:420819
Problem Description:
As a part of diskgroup import, the disks are
scanned and added to the diskgroup. During this
operation, the private region contents stored
incore are read to build the configuration
and log copies. This was failing leading to the
diskgroup import failure.
Resolution:
The disk private region contents are re-read,
if the above problem is encountered.
(SR:8606405567 CR: JAGaf65488)
Veritas Incident Number:423304
Problem Description:
A disk that was previously initialized and
used as cdsdisk can no longer be brought online.
/etc/vx/diag.d/vxprivutil scan sees valid label
but vxdisk list shows that it is a hpdisk.
Resolution:
vxdiskadm command is not re-initializing the
disk correctly. This may cause a problem
during the disk re-initialization
which could lead to another problem later.
(SR: 8606419808 CR: JAGaf79638)
Veritas Incident Number:415074
Problem Description:
Commands to resize a filesystem need to be run on the
master node. Need to use cmexec in the SG environment.
Resolution:
If we are running in an HP/SG environment, use cmexec.
(SR: 8606408077 CR: JAGaf67980)
Veritas Incident Number:407517
Problem Description:
The listen queue for vxconfigd was set to 5.
Resolution:
Increased listen queue length to 30.
(SR: 8606419813 CR: JAGaf79643)
(Veritas Incident Number:414109)
Problem Description:
Internal variable 'vol_join_allowed' was not reset
to zero before GAB/GLM initialization.
Resolution:
Reset 'vol_join_allowed' to 0 before any GAB/GLM
initialization.
Handle EFAULT return value from
VOLCVM_INIT/VOLCVM_INIT_CONFIG ioctls, which
indicates GAB/GLM init failures.
Add a new global vol_retry_join to distinguish
between GAB/GLM init failures and GLM_API_TRYLOCK
failure (which indicates another node is joining).
(SR: 8606419815 CR: JAGaf79645)
Veritas Incident Number:424888
Problem Description:
vxvol dumps core while trying to start the volumes.
vxvol gets the dg configuration objects while
starting the volumes. If the dg config. retrieval
fails, then a NULL is returned. This wasn't handled
properly and lead to a coredump.
Resolution:
Handle the return conditions properly.
(SR: 8606419816 CR: JAGaf79646)
Veritas Incident Number:413978
Problem Description:
The code is looping and accessing the same free bit
that was returned from the function while
updating the bitmap of the table of contents
in a private region.
Resolution:
The looping was due to incorrect handling of
the variable while scanning the bitmap in
the reverse direction. This was addressed by
decrementing the variable representing the
free-bit to start the next phase of free-bitmap
scan if that bit was set in the pending
allocation bitmap.
(SR: 8606419818 CR: JAGaf79648)
Veritas Incident Number:414744
Problem Description:
If a diskgroup is imported with -o selectcp option,
the DG goes into SSB state.
Resolution:
The problem was because we weren't resetting the
dm_expected ssbid on the disk, for -o
selectcp imports. Importing a DG by selecting a
config-copy should reset both the da_actual
ssbid on the disk and also the dm_expected ssbid.
We were clearing the da expected ssbid
but weren't doing it for dm ssbid.
(SR: 8606419820 CR: JAGaf79650)
Veritas Incident Number:415069
Problem Description:
Having 1 old style NPFMR2 snapshot + 1 instant(new
style PFMR3) snapshot of a source volume
and firing an I/O to the old style snapshot
would panic during a dco_update of the old snapshot.
Resolution:
The solution should be to disallow a snapshot prepare
of new-style FMR-3 snapshots on a volume
if it already has old format NPFMR2 SNAPSHOTS.
(SR: 8606419821 CR: JAGaf79651)
Veritas Incident Number:419448
Problem Description:
The filesystem is disabled after receiving IO errors as
PGR keys are not being set for all the
paths. PGR keys have to be set for
all the active/enabled paths of the dmpnode
in order for I/Os to succeed through them.
Resolution:
PGR keys weren't getting removed during unregistration
or deport leading to stale PGR Keys
during import which can fail PGR registrations.
(SR: 8606419822 CR: JAGaf79652)
Veritas Incident Number:420208
Problem Description:
Snapshots cannot be taken for a volume in a shared
DG as vxvol dumps core. The problem was an invalid
free of a variable in the function that freezes
the cluster before taking the snapshots.
Resolution:
Check for an invalid free of a variable.
(SR:8606423407 CR:JAGaf82930)
Veritas Incident Number:498461
Problem Description:
When the SPC-2 flag is off, the new ASL works
with or without PowerPath. It seems the new ASL
didn't interpret LUN_SER_NO in Pagecode 0x83
with regard to re-creating emcpower
links during boot with PowerPath release 4.5.
It was found that the vxdisk list duplicates
appear after running the first
vxvm script (vxvm-sysboot).
Resolution:
Solution is to wait until the root filesystem is
writable, then we can recreate the emcpower
links before running vxvm-sysboot.
Duplicates do not appear in this case.
(SR:8606423408 CR: JAGaf82931)
Veritas Incident Number:499360
Problem Description:
In one of the DDL routine we make a call to vendor info
function routine to get the function pointers for
appropriate routines such as VENDOR_INFO_ROUTINE,
VENDOR_CLAIM_ROUTINE, VENDOR_SELECT_DEVICE_ROUTINE and
VENDOR_GET_DYNAMIC_ATTR_ROUTINE. We don't check the
return values for these routines which leads to
invoking a wrong function pointer.
Resolution:
The function pointers in the DDL routine is
initialised to NULL variable so that the vxconfigd
code later will not attempt to invoke bad function
pointer.
(SR:8606423409 CR: JAGaf82932)
Veritas Incident Number:496511
Problem Description:
It was found that the special name "dumpvol"
was not being considered as an
exception to need to have a filesystem.
Resolution:
The fix is to check the volume name and if it
is equal to dumpvol, then we do
not require it to have a filesystem in place.
(SR:8606423414 CR: JAGaf82937)
Veritas Incident Number:430703
Problem Description:
While shutting down an HP/SG cluster the error
message:
VxVM ERROR V-5-2-0 VOLCVM_GET_NIDMAP failed
appears.Message is harmless and it might
cause confusion to the customer.
Resolution:
Remove the error message from the CVM code.
(SR:8606423411 CR: JAGaf82934)
Veritas Incident Number:427557
Problem Description:
In CVM environment when there are many mirrored
volumes on the disk group configuration, volume
resynchronisation forks vxvol for every plex in
the mirrored volume.
Resolution:
A default "plex fork" tunable option is implemented in the
CVM code.
(SR:8606423410 CR: JAGaf82933)
Veritas Incident Number:424893
Problem Description:
In CVM environment, the nodeid map namely
voldnid_map is not getting updated at the vxconfigd level
whenever vxclust utility is reinitialised.
Resolution:
Solution is to copy the kernel nodeid map at the
vxconfigd level during the cluster operation.
(SR: 8606423412 CR: JAGaf82935 )
Veritas Incident Number: 429306
Problem Description:
Addition of new EVA diskarrays namely EVA4k6k, EVA3000,
EVA5000 resulted in the VM code change to support
these ASLs.
Resolution:
These ASL's are included in DDL code with the
corresponding VID and PID so that the disks get claimed
in VxVM 4.1 HPUX.
(SR: 8606419810 CR: JAGaf79640)
Veritas Incident Number: 361716
Problem Description:
The problem is with the binaries vxse_stripes1 etc.
at run time they are looking for some shared libraries
on prague machine under
/net/prague/u2/sap/nightly/obdev/hp/lib which is
not accessible. This is because of the wrong library
path being picked up while compiling these binaries.
Resolution:
Pick up the correct library path for compiling the
binaries.
(SR: 8606419803 CR: JAGaf79633 )
Cumulative VVR fixes
1)Veritas Incident Number:426233
Problem Description:
If the hostname and domain name together exceed 31
characters, then the hostname lookup fails.
Resolution:
The error message has been enhanced to reflect
that the host name is too big.
2)Veritas Incident Number:415076
Problem Description:
In a multiple-secondary configuration, vradmin
repstatus command can show blank value against
the "Logging to:" field for one secondary if
primary RLINKs are detached.
Resolution:
The code is fixed to set the default value of the
"Logging to:" field to 20 (corresponding to SRL),
rather than -1. In case the RVG is in
pass-through mode, the "Logging to:"
field will be set to "N/A".
3)Veritas Incident Number:415078
Problem Description:
The hang might occur if there are more than 256
volumes in an RVG. The vradmind daemon will eat up
lots of system memory and stop responding.
Resolution:
The solution is to free the allocated memory after
it has been used.
Enhancement:
No (superseded patches contained enhancements)
PHCO_34811:
With PHCO_34811 one can turn on vxconfigd daemon debugging
on the fly, i.e without having to restart vxconfigd.
The syntax for switching on or off debugging and logging
the debug messages into a [file] is:
vxdctl debug 0-9 [file], where 0 turns off debugging.
The default debug file location is /var/adm/vxconfigd.log
SR:
8606419256 8606405497 8606419263 8606419265 8606419267
8606408073 8606413328 8606419276 8606406994 8606419264
8606419266 8606411927 8606419269 8606419271 8606419272
8606413083 8606405567 8606419808 8606408077 8606419813
8606419815 8606419816 8606419818 8606419820 8606419821
8606419822 8606419803 8606423407 8606423408 8606423409
8606423414 8606423411 8606423410 8606423412 8606419810
8606445096 8606445097 8606445098 8606445099 8606445101
8606445103 8606445105 8606445109 8606445113 8606445114
8606445117 8606445118 8606445119 8606445120 8606445121
8606445122 8606445312 8606445313 8606446350 8606446351
8606442723 8606455828 8606447238 8606455839 8606449570
8606467245 8606467112 8606467110 8606467113 8606430187
8606405601 8606420552 8606472168 8606473669 8606472173
8606473664 8606472172 8606472171 8606472174 8606473668
8606470105 8606455268 8606474302 8606471971 8606467094
Patch Files:
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=HP:
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=VERITAS:
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=HP:
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=VERITAS:
/etc/vx/static.d/default/libvxarrays.a
/etc/vx/static.d/default/ddlarrays.proto
/etc/vx/static.d/default/libvxscsi.a
/etc/vx/static.d/build/vold.o
/etc/vx/type/static/vxconfigd
/etc/vx/type/static/vxprivutil
/etc/vx/type/static/vxmake
/etc/vx/type/static/vxrvg
/etc/vx/type/static/vxprint
/etc/vx/type/static/vxrlink
/etc/vx/type/static/vxedit
/etc/vx/type/static/vxcache
/etc/vx/type/static/vxconfigdump
/etc/vx/type/gen/vxinfo
/etc/vx/type/gen/vxmend
/etc/vx/type/gen/vxplex
/etc/vx/type/gen/vxsd
/etc/vx/type/gen/vxvol
/etc/vx/type/gen/vxmake
/etc/vx/type/gen/vxmake_static
/etc/vx/type/fsgen/vxplex
/etc/vx/type/fsgen/vxvol
/etc/vx/type/fsgen/fs.d/vxfs/vxsync
/etc/vx/type/raid5/vxmend
/etc/vx/type/raid5/vxplex
/etc/vx/type/raid5/vxsd
/etc/vx/type/raid5/vxvol
/etc/vx/type/raid5/vxmake
/etc/vx/aslkey.d/libvxemc.key
/etc/vx/aslkey.d/libvxhpalua.key
/etc/vx/aslkey.d/libvxhdsalua.key
/etc/vx/apmkey.d/64/dmphpalua.key
/etc/vx/apmkey.d/64/dmphdsalua.key
/sbin/vxdisk
/sbin/vxdmpadm
/sbin/vxrecover
/sbin/vxdg
/sbin/vxsnap
/sbin/vol_mgr/vxvm/smapi_listener
/sbin/vxdctl
/sbin/vxcache
/sbin/vxrelayout
/sbin/vxmend
/sbin/vxplex
/sbin/vxsd
/sbin/vxvol
/sbin/vxvmboot
/sbin/vxiod
/sbin/init.d/vxvm-reconfig
/sbin/init.d/vxvm-startup
/usr/conf/mod/dmphpalua
/usr/conf/mod/dmphdsalua
/usr/lib/libvrascmd.sl
/usr/lib/hpux32/libvxscsi.sl
/usr/lib/libvxddl.sl
/usr/lib/libvxsg.sl
/usr/lib/vxvm/bin/vxparms
/usr/lib/vxvm/bin/vxclustd
/usr/lib/vxvm/bin/vxclustipc
/usr/lib/vxvm/bin/vxcheckda
/usr/lib/vxvm/bin/vxckdiskrm
/usr/lib/vxvm/bin/vxlvminfo
/usr/lib/vxvm/bin/vxdisksetup
/usr/lib/vxvm/bin/vxclustadm
/usr/lib/vxvm/bin/vxresize
/usr/lib/vxvm/bin/vxhpcap
/usr/lib/vxvm/bin/vxislvm
/usr/lib/vxvm/bin/vxrootmir
/usr/lib/vxvm/bin/vxcap-lvmpart
/usr/lib/vxvm/bin/vxcap-lvmvol
/usr/lib/vxvm/bin/vxchg_rootid
/usr/lib/vxvm/bin/vxcp_lvmroot
/usr/lib/vxvm/bin/vxdestroy_lvmroot
/usr/lib/vxvm/bin/vxdiskunsetup
/usr/lib/vxvm/bin/vxedvtoc
/usr/lib/vxvm/bin/vxevac
/usr/lib/vxvm/bin/vxlvmencap
/usr/lib/vxvm/bin/vxmirror
/usr/lib/vxvm/bin/vxnewdmname
/usr/lib/vxvm/bin/vxprtvtoc
/usr/lib/vxvm/bin/vxres_lvmroot
/usr/lib/vxvm/bin/vxtaginfo
/usr/lib/vxvm/bin/vxbrk_rootmir
/usr/lib/vxvm/diag.d/vxkprint
/usr/lib/vxvm/diag.d/vxcheckasl
/usr/lib/vxvm/diag.d/vxiotimeout
/usr/lib/vxvm/diag.d/vxr5logutil
/usr/lib/vxvm/diag.d/vxdmpdbprint
/usr/lib/vxvm/diag.d/kmsgdump
/usr/lib/vxvm/diag.d/vxdmpdebug
/usr/lib/vxvm/diag.d/vxaslkey
/usr/lib/vxvm/diag.d/vxpatch_volboot
/usr/lib/vxvm/lib/discovery.d/libvxhpalua.sl
/usr/lib/vxvm/lib/discovery.d/libvxhdsalua.sl
/usr/lib/vxvm/lib/discovery.d/libvxemc.sl
/usr/lib/vxvm/voladm.d/bin/disk.doinit
/usr/lib/vxvm/voladm.d/bin/disk.analysis
/usr/lib/vxvm/voladm.d/bin/disk.anal.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.convert
/usr/lib/vxvm/voladm.d/bin/disk.init
/usr/lib/vxvm/voladm.d/bin/disk.lvm.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.rollback
/usr/lib/vxvm/voladm.d/bin/disk.savelvm
/usr/lib/vxvm/voladm.d/bin/vxcheck_sysconf
/usr/lib/vxvm/voladm.d/bin/vxsave_lvmrecs
/usr/lib/vxvm/voladm.d/lib/vxadm_lvmlib.sh
/usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh
/usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh
/usr/sbin/vradmind
/usr/sbin/vxmake
/usr/sbin/vxddladm
/usr/sbin/vxdg
/usr/sbin/vxassist
/usr/sbin/vxconfigd
/usr/sbin/vxedit
/usr/sbin/vxprint
/usr/sbin/vxnotify
/usr/sbin/vxtrace
/usr/sbin/vxstat
/usr/sbin/vxtask
/usr/sbin/vxrvg
/usr/sbin/vxrlink
/usr/sbin/vxdco
/usr/sbin/vxvset
/usr/sbin/vxsp
/usr/sbin/vxnetd
/usr/sbin/vxibc
/usr/sbin/cluster_init
/usr/sbin/cluster_master
/usr/sbin/cluster_slave
/usr/sbin/cluster_join
/usr/sbin/cluster_stop
/usr/sbin/vrport
/usr/sbin/vxtranslog
/usr/sbin/vxinfo
/usr/sbin/vxsnptadm
/usr/sbin/vradmin
/usr/sbin/vrnotify
/usr/sbin/vrstat
/usr/sbin/vxrsync
/usr/sbin/in.vxrsyncd
/usr/sbin/vxmemstat
/usr/sbin/vxtune
/usr/sbin/vxautoanalysis
/usr/sbin/vxautoconvert
/usr/sbin/vxautorollback
/usr/sbin/vxvmconvert
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=HP:
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=VERITAS:
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=HP:
VRTSvxvm.VXVM-RUN,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=VERITAS:
/etc/vx/static.d/default/libvxarrays.a
/etc/vx/static.d/default/ddlarrays.proto
/etc/vx/static.d/default/libvxscsi.a
/etc/vx/static.d/build/vold.o
/etc/vx/type/static/vxconfigd
/etc/vx/type/static/vxprivutil
/etc/vx/type/static/vxmake
/etc/vx/type/static/vxconfigdump
/etc/vx/type/static/vxrvg
/etc/vx/type/static/vxprint
/etc/vx/type/static/vxrlink
/etc/vx/type/static/vxedit
/etc/vx/type/static/vxcache
/etc/vx/type/gen/vxinfo
/etc/vx/type/gen/vxmend
/etc/vx/type/gen/vxplex
/etc/vx/type/gen/vxsd
/etc/vx/type/gen/vxmake
/etc/vx/type/gen/vxmake_static
/etc/vx/type/gen/vxvol
/etc/vx/type/fsgen/vxplex
/etc/vx/type/fsgen/vxvol
/etc/vx/type/fsgen/fs.d/vxfs/vxsync
/etc/vx/type/raid5/vxmend
/etc/vx/type/raid5/vxplex
/etc/vx/type/raid5/vxsd
/etc/vx/type/raid5/vxvol
/etc/vx/type/raid5/vxmake
/etc/vx/aslkey.d/libvxemc.key
/etc/vx/aslkey.d/libvxhpalua.key
/etc/vx/aslkey.d/libvxhdsalua.key
/etc/vx/apmkey.d/64/dmphpalua.key
/etc/vx/apmkey.d/64/dmphdsalua.key
/sbin/vxdisk
/sbin/vxdmpadm
/sbin/vxrecover
/sbin/vxdg
/sbin/vxsnap
/sbin/vol_mgr/vxvm/smapi_listener
/sbin/vxdctl
/sbin/vxcache
/sbin/vxrelayout
/sbin/vxmend
/sbin/vxplex
/sbin/vxsd
/sbin/vxvol
/sbin/vxvmboot
/sbin/vxiod
/sbin/init.d/vxvm-reconfig
/sbin/init.d/vxvm-startup
/usr/conf/mod/dmphpalua
/usr/conf/mod/dmphdsalua
/usr/lib/libvxscsi.sl
/usr/lib/libvxddl.sl
/usr/lib/libvxsg.sl
/usr/lib/libvrascmd.sl
/usr/lib/vxvm/bin/vxclustd
/usr/lib/vxvm/bin/vxclustipc
/usr/lib/vxvm/bin/vxcheckda
/usr/lib/vxvm/bin/vxckdiskrm
/usr/lib/vxvm/bin/vxclustadm
/usr/lib/vxvm/bin/vxresize
/usr/lib/vxvm/bin/vxislvm
/usr/lib/vxvm/bin/vxparms
/usr/lib/vxvm/bin/vxcap-lvmpart
/usr/lib/vxvm/bin/vxcap-lvmvol
/usr/lib/vxvm/bin/vxchg_rootid
/usr/lib/vxvm/bin/vxcp_lvmroot
/usr/lib/vxvm/bin/vxdestroy_lvmroot
/usr/lib/vxvm/bin/vxdisksetup
/usr/lib/vxvm/bin/vxdiskunsetup
/usr/lib/vxvm/bin/vxedvtoc
/usr/lib/vxvm/bin/vxevac
/usr/lib/vxvm/bin/vxlvmencap
/usr/lib/vxvm/bin/vxmirror
/usr/lib/vxvm/bin/vxnewdmname
/usr/lib/vxvm/bin/vxprtvtoc
/usr/lib/vxvm/bin/vxrootmir
/usr/lib/vxvm/bin/vxres_lvmroot
/usr/lib/vxvm/bin/vxtaginfo
/usr/lib/vxvm/bin/vxhpcap
/usr/lib/vxvm/bin/vxlvminfo
/usr/lib/vxvm/bin/vxbrk_rootmir
/usr/lib/vxvm/lib/discovery.d/libvxhpalua.sl
/usr/lib/vxvm/lib/discovery.d/libvxhdsalua.sl
/usr/lib/vxvm/lib/discovery.d/libvxemc.sl
/usr/lib/vxvm/diag.d/vxr5logutil
/usr/lib/vxvm/diag.d/vxdmpdbprint
/usr/lib/vxvm/diag.d/vxcheckasl
/usr/lib/vxvm/diag.d/vxiotimeout
/usr/lib/vxvm/diag.d/kmsgdump
/usr/lib/vxvm/diag.d/vxkprint
/usr/lib/vxvm/diag.d/vxdmpdebug
/usr/lib/vxvm/diag.d/vxaslkey
/usr/lib/vxvm/diag.d/vxpatch_volboot
/usr/lib/vxvm/voladm.d/bin/disk.doinit
/usr/lib/vxvm/voladm.d/bin/disk.analysis
/usr/lib/vxvm/voladm.d/bin/disk.anal.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.convert
/usr/lib/vxvm/voladm.d/bin/disk.init
/usr/lib/vxvm/voladm.d/bin/disk.lvm.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.rollback
/usr/lib/vxvm/voladm.d/bin/disk.savelvm
/usr/lib/vxvm/voladm.d/bin/vxcheck_sysconf
/usr/lib/vxvm/voladm.d/bin/vxsave_lvmrecs
/usr/lib/vxvm/voladm.d/lib/vxadm_lvmlib.sh
/usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh
/usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh
/usr/sbin/vxmemstat
/usr/sbin/vxtune
/usr/sbin/vradmind
/usr/sbin/vxmake
/usr/sbin/vxddladm
/usr/sbin/vxdg
/usr/sbin/vxassist
/usr/sbin/vxconfigd
/usr/sbin/vxedit
/usr/sbin/vxprint
/usr/sbin/vxnotify
/usr/sbin/vxtrace
/usr/sbin/vxstat
/usr/sbin/vxtask
/usr/sbin/vxrvg
/usr/sbin/vxrlink
/usr/sbin/vxdco
/usr/sbin/vxvset
/usr/sbin/vxsp
/usr/sbin/vxnetd
/usr/sbin/vxibc
/usr/sbin/cluster_init
/usr/sbin/cluster_master
/usr/sbin/cluster_slave
/usr/sbin/cluster_join
/usr/sbin/cluster_stop
/usr/sbin/vrport
/usr/sbin/vxtranslog
/usr/sbin/vxinfo
/usr/sbin/vxsnptadm
/usr/sbin/vradmin
/usr/sbin/vrnotify
/usr/sbin/vrstat
/usr/sbin/vxrsync
/usr/sbin/in.vxrsyncd
/usr/sbin/vxautoanalysis
/usr/sbin/vxautoconvert
/usr/sbin/vxautorollback
/usr/sbin/vxvmconvert
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=HP:
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=VERITAS:
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=HP:
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_IA,v=VERITAS:
/opt/VRTSvxms/lib/map/pa20_64/libvxdmp.sl
/opt/VRTSvxms/lib/map/pa20_64/libvxvm.sl
/opt/VRTSvxms/lib/map/pa20_64/libvmrd.sl
/opt/VRTSvxms/lib/map/libvxdmp.sl
/opt/VRTSvxms/lib/map/libvmrd.sl
/opt/VRTSvxms/lib/map/libvxvm.sl
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=HP:
VRTSvxvm.VXMS,fr=4.1.011,fa=HP-UX_B.11.23_PA,v=VERITAS:
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=HP:
VRTSvxvm.VXMS,fr=4.1.010,fa=HP-UX_B.11.23_PA,v=VERITAS:
/opt/VRTSvxms/lib/map/pa20_64/libvxdmp.sl
/opt/VRTSvxms/lib/map/pa20_64/libvmrd.sl
/opt/VRTSvxms/lib/map/pa20_64/libvxvm.sl
/opt/VRTSvxms/lib/map/libvxdmp.sl
/opt/VRTSvxms/lib/map/libvmrd.sl
/opt/VRTSvxms/lib/map/libvxvm.sl
VRTSvxvm.VXSE,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,v=HP:
VRTSvxvm.VXSE,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,v=VERITAS:
VRTSvxvm.VXSE,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,v=HP:
VRTSvxvm.VXSE,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,v=VERITAS:
/opt/VRTS/vxse/vxvm/vxse_dg1
/opt/VRTS/vxse/vxvm/vxse_dg2
/opt/VRTS/vxse/vxvm/vxse_dg3
/opt/VRTS/vxse/vxvm/vxse_dg4
/opt/VRTS/vxse/vxvm/vxse_dg5
/opt/VRTS/vxse/vxvm/vxse_dg6
/opt/VRTS/vxse/vxvm/vxse_disk
/opt/VRTS/vxse/vxvm/vxse_disklog
/opt/VRTS/vxse/vxvm/vxse_drl1
/opt/VRTS/vxse/vxvm/vxse_drl2
/opt/VRTS/vxse/vxvm/vxse_host
/opt/VRTS/vxse/vxvm/vxse_mirstripe
/opt/VRTS/vxse/vxvm/vxse_raid5
/opt/VRTS/vxse/vxvm/vxse_raid5log1
/opt/VRTS/vxse/vxvm/vxse_raid5log2
/opt/VRTS/vxse/vxvm/vxse_raid5log3
/opt/VRTS/vxse/vxvm/vxse_redundancy
/opt/VRTS/vxse/vxvm/vxse_spares
/opt/VRTS/vxse/vxvm/vxse_stripes1
/opt/VRTS/vxse/vxvm/vxse_stripes2
/opt/VRTS/vxse/vxvm/vxse_volplex
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,
v=HP:
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.011,fa=HP-UX_B.11.23_IA/PA,
v=VERITAS:
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,
v=HP:
VRTSvxvm.VXVM-ENG-A-MAN,fr=4.1.010,fa=HP-UX_B.11.23_IA/PA,
v=VERITAS:
/usr/share/man/man1m.Z/vxdctl.1m
/usr/share/man/man1m.Z/vxresize.1m
/usr/share/man/man1m.Z/vxconfigd.1m
what(1) Output:
VRTSvxvm.VXVM-RUN,fr=4.1.011,fa=HP-UX_B.11.23_IA,v=HP:
/etc/vx/apmkey.d/64/dmphpalua.key:
None.
/etc/vx/apmkey.d/64/dmphdsalua.key:
None.
/etc/vx/aslkey.d/libvxemc.key:
None.
/etc/vx/aslkey.d/libvxhpalua.key:
None.
/etc/vx/aslkey.d/libvxhdsalua.key:
None.
/etc/vx/static.d/build/vold.o:
Copyright (c) 1992 Lomarline Ltd
avltree.c 1.2.2 9/30/94 14:34:18 LMRN
$Header: NAME: License Manager with ELM Support VERS
ION: 3.02.006 BUILT: Nov 21 2003 17:09:29 Co
pyright 1996-2004 VERITAS SOFTWARE Corpora
tion. All Rights Reserved. $
$ Sep 17 2004 11:14:56
$
client.c $Date: 2005/08/18 20:50:10 $Revision: 1.46.
2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
cluster.c $Date: 2006/10/17 12:27:18 $Revision: 1.42
.2.18.4.5.6.3.2.1 PATCH_11.23PI (PHCO_35738)
da.c $Date: 2006/10/17 12:27:39 $Revision: 1.99.2.36
.4.10.2.1.2.1 PATCH_11.23PI (PHCO_35738)
dapriv.c $Date: 2006/10/17 12:12:47 $Revision: 1.15.
2.12.30.3.2.1 PATCH_11.23PI (PHCO_35738)
daselect.c $Date: 2006/04/05 09:49:03 $Revision: 1.2
0.2.3.30.6.2.1 PATCH_11.23PI (PHCO_34811)
dasup.c $Date: 2006/10/17 12:28:04 $Revision: 1.37.2
.8.64.4.6.2.2.1 PATCH_11.23PI (PHCO_35738)
dg.c $Date: 2005/12/26 08:09:57 $Revision: 1.106.2.3
7.4.7.4.2 PATCH_11.23PI (PHCO_34811)
dgimport.c $Date: 2006/10/17 12:28:33 $Revision: 1.8
7.2.43.4.5.6.2 PATCH_11.23PI (PHCO_35738)
dgmove.c $Date: 2006/10/17 12:28:49 $Revision: 1.33.
2.21.10.6.14.1 PATCH_11.23PI (PHCO_35738)
haops.c $Date: 2005/09/08 16:25:17 $Revision: 1.11.2
.5.32.4.2.1 PATCH_11.23PI (PHCO_33509)
kernel.c $Date: 2006/07/28 10:51:41 $Revision: 1.177
.2.44.4.16.4.6 PATCH_11.23PI (PHCO_34811)
krecover.c $Date: 2006/10/17 12:29:15 $Revision: 1.4
0.2.6.72.1 PATCH_11.23PI (PHCO_35738)
main.c $Date: 2006/04/06 08:39:40 $Revision: 1.33.2.
11.4.3.4.1 PATCH_11.23PI (PHCO_34811)
master.c $Date: 2006/10/17 12:29:31 $Revision: 1.50.
2.10.4.1.6.2.2.1 PATCH_11.23PI (PHCO_35738)
misc.c $Date: 2006/04/06 08:39:36 $Revision: 1.23.2.
9.10.4.2.1 PATCH_11.23PI (PHCO_34811)
mode.c $Date: 2006/04/06 08:39:37 $Revision: 1.51.2.
6.4.4.2.3 PATCH_11.23PI (PHCO_34811)
priv.c $Date: 2005/08/11 10:36:05 $Revision: 1.22.2.
9.10.1.2.1 PATCH_11.23PI (PHCO_33509)
query.c $Date: 2006/05/08 16:07:33 $Revision: 1.61.2
.15.10.9.2.1 PATCH_11.23PI (PHCO_34811)
reqtbl.c $Date: 2006/04/06 08:39:37 $Revision: 1.47.
2.4.34.6.4.1 PATCH_11.23PI (PHCO_34811)
request.c $Date: 2006/03/16 12:21:48 $Revision: 1.44
.2.11.10.2.6.1 PATCH_11.23PI (PHCO_34811)
ssb.c $Date: 2005/12/20 08:27:09 $Revision: 1.3.2.12
.10.2.6.2 PATCH_11.23PI (PHCO_34811)
slave.c $Date: 2006/10/17 12:30:15 $Revision: 1.62.2
.12.10.3.6.2.2.1 PATCH_11.23PI (PHCO_35738)
sliced.c $Date: 2006/10/17 12:30:29 $Revision: 1.43.
2.11.10.1.6.4.2.1 PATCH_11.23PI (PHCO_35738)
cbrtranslog.c $Date: 2006/04/06 10:33:51 $Revision:
1.10.2.12.10.8.4.1 PATCH_11.23PI (PHCO_34811
)
voldctlsup.c $Date: 2006/04/06 08:39:37 $Revision: 1
.13.106.2.4.1 PATCH_11.23PI (PHCO_34811)
volddl_sys.c $Date: 2005/11/09 06:17:01 $Revision: 1
.12.2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
volddl_vendor_lib.c $Date: 2006/11/06 07:51:35 $Revi
sion: 1.16.2.21.6.11.22.1 PATCH_11.23PI (PHC
O_35738)
volddl_migration.c $Date: 2006-03-16 12:21:53 $Revis
ion: 1.16.2.20.10.19.2.1 PATCH_11.23PI (PHCO
_34811)
volddl_dmp.c $Date: 2006/03/16 12:21:55 $Revision: 1
.9.2.5.10.9.2.1 PATCH_11.23PI (PHCO_34811)
vxscsilib.c $Date: 2006/07/28 11:44:33 $Revision: 1.
5.102.4.4.4 PATCH_11.23PI (PHCO_34811)
voldipc.c $Date: 2005/12/20 10:34:18 $Revision: 1.44
.2.12.10.1.6.6 PATCH_11.23PI (PHCO_34811)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
ddlapm.c $Date: 2006/09/13 07:32:02 $Revision: 1.5.2
.8.10.1.32.1 PATCH_11.23PI (PHCO_35476)
/etc/vx/static.d/default/libvxarrays.a:
ddlemc.c $Date: 2006/05/08 05:29:49 $Revision: 1.10.
2.4.4.4.4.4 PATCH_11.23PI (PHCO_34811)
ddlhpalua.c $Date: 2006-03-09 $Revision: 1.1.4.1.2.1
3 PATCH_11.23PI (PHCO_34811)
ddlhdsalua.c $Date: 2006/04/11 05:28:59 $Revision: 1
.1.4.2.2.2 PATCH_11.23PI (PHCO_34811)
/etc/vx/static.d/default/ddlarrays.proto:
None.
/etc/vx/static.d/default/libvxscsi.a:
vxrtpg.c $Date: 2005/08/17 12:59:33 $Revision: 1.1.4
.1.2.1 PATCH_11.23PI (PHCO_33509)
vxscsilib.c $Date: 2006/07/28 11:44:33 $Revision: 1.
5.102.4.4.4 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/fsgen/fs.d/vxfs/vxsync:
vxfsfreeze.c $Date: 2005/09/02 15:59:38 $Revision: 1
.1.2.8.10.2.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/fsgen/vxplex:
volplex.c $Date: 2006/12/28 07:58:16 $Revision: 1.12
6.2.35.4.10.4.1.2.2 PATCH_11.23PI (PHCO_3481
1)
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/fsgen/vxvol:
comstart.c $Date: 2006/09/04 05:58:52 $Revision: 1.6
9.2.30.4.6.4.3.2.1 PATCH_11.23PI (PHCO_35476
)
vxfsfreeze.c $Date: 2005/09/02 15:59:38 $Revision: 1
.1.2.8.10.2.6.1 PATCH_11.23PI (PHCO_33509)
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/gen/vxinfo:
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/gen/vxmend:
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/gen/vxplex:
volplex.c $Date: 2006/12/28 07:58:16 $Revision: 1.12
6.2.35.4.10.4.1.2.2 PATCH_11.23PI (PHCO_3481
1)
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/gen/vxsd:
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/gen/vxvol:
comstart.c $Date: 2006/09/04 05:58:52 $Revision: 1.6
9.2.30.4.6.4.3.2.1 PATCH_11.23PI (PHCO_35476
)
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/gen/vxmake:
volmakesup.c $Date: 2005-09-23 08:25:24 $Revision: 1
.34.2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/gen/vxmake_static:
volmakesup.c $Date: 2005-09-23 08:25:24 $Revision: 1
.34.2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/raid5/vxmend:
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/raid5/vxplex:
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/raid5/vxsd:
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/raid5/vxvol:
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/raid5/vxmake:
volmakesup.c $Date: 2005-09-23 08:25:24 $Revision: 1
.34.2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxconfigd:
$Header: NAME: License Manager with ELM Support VERS
ION: 3.02.006 BUILT: Nov 21 2003 17:09:29 Co
pyright 1996-2004 VERITAS SOFTWARE Corpora
tion. All Rights Reserved. $
client.c $Date: 2005/08/18 20:50:10 $Revision: 1.46.
2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
cluster.c $Date: 2006/10/17 12:27:18 $Revision: 1.42
.2.18.4.5.6.3.2.1 PATCH_11.23PI (PHCO_35738)
da.c $Date: 2006/10/17 12:27:39 $Revision: 1.99.2.36
.4.10.2.1.2.1 PATCH_11.23PI (PHCO_35738)
dapriv.c $Date: 2006/10/17 12:12:47 $Revision: 1.15.
2.12.30.3.2.1 PATCH_11.23PI (PHCO_35738)
daselect.c $Date: 2006/04/05 09:49:03 $Revision: 1.2
0.2.3.30.6.2.1 PATCH_11.23PI (PHCO_34811)
dasup.c $Date: 2006/10/17 12:28:04 $Revision: 1.37.2
.8.64.4.6.2.2.1 PATCH_11.23PI (PHCO_35738)
dg.c $Date: 2005/12/26 08:09:57 $Revision: 1.106.2.3
7.4.7.4.2 PATCH_11.23PI (PHCO_34811)
dgimport.c $Date: 2006/10/17 12:28:33 $Revision: 1.8
7.2.43.4.5.6.2 PATCH_11.23PI (PHCO_35738)
dgmove.c $Date: 2006/10/17 12:28:49 $Revision: 1.33.
2.21.10.6.14.1 PATCH_11.23PI (PHCO_35738)
haops.c $Date: 2005/09/08 16:25:17 $Revision: 1.11.2
.5.32.4.2.1 PATCH_11.23PI (PHCO_33509)
kernel.c $Date: 2006/07/28 10:51:41 $Revision: 1.177
.2.44.4.16.4.6 PATCH_11.23PI (PHCO_34811)
krecover.c $Date: 2006/10/17 12:29:15 $Revision: 1.4
0.2.6.72.1 PATCH_11.23PI (PHCO_35738)
main.c $Date: 2006/04/06 08:39:40 $Revision: 1.33.2.
11.4.3.4.1 PATCH_11.23PI (PHCO_34811)
master.c $Date: 2006/10/17 12:29:31 $Revision: 1.50.
2.10.4.1.6.2.2.1 PATCH_11.23PI (PHCO_35738)
misc.c $Date: 2006/04/06 08:39:36 $Revision: 1.23.2.
9.10.4.2.1 PATCH_11.23PI (PHCO_34811)
mode.c $Date: 2006/04/06 08:39:37 $Revision: 1.51.2.
6.4.4.2.3 PATCH_11.23PI (PHCO_34811)
priv.c $Date: 2005/08/11 10:36:05 $Revision: 1.22.2.
9.10.1.2.1 PATCH_11.23PI (PHCO_33509)
query.c $Date: 2006/05/08 16:07:33 $Revision: 1.61.2
.15.10.9.2.1 PATCH_11.23PI (PHCO_34811)
reqtbl.c $Date: 2006/04/06 08:39:37 $Revision: 1.47.
2.4.34.6.4.1 PATCH_11.23PI (PHCO_34811)
request.c $Date: 2006/03/16 12:21:48 $Revision: 1.44
.2.11.10.2.6.1 PATCH_11.23PI (PHCO_34811)
ssb.c $Date: 2005/12/20 08:27:09 $Revision: 1.3.2.12
.10.2.6.2 PATCH_11.23PI (PHCO_34811)
slave.c $Date: 2006/10/17 12:30:15 $Revision: 1.62.2
.12.10.3.6.2.2.1 PATCH_11.23PI (PHCO_35738)
sliced.c $Date: 2006/10/17 12:30:29 $Revision: 1.43.
2.11.10.1.6.4.2.1 PATCH_11.23PI (PHCO_35738)
cbrtranslog.c $Date: 2006/04/06 10:33:51 $Revision:
1.10.2.12.10.8.4.1 PATCH_11.23PI (PHCO_34811
)
voldctlsup.c $Date: 2006/04/06 08:39:37 $Revision: 1
.13.106.2.4.1 PATCH_11.23PI (PHCO_34811)
volddl_sys.c $Date: 2005/11/09 06:17:01 $Revision: 1
.12.2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
volddl_vendor_lib.c $Date: 2006/11/06 07:51:35 $Revi
sion: 1.16.2.21.6.11.22.1 PATCH_11.23PI (PHC
O_35738)
volddl_migration.c $Date: 2006-03-16 12:21:53 $Revis
ion: 1.16.2.20.10.19.2.1 PATCH_11.23PI (PHCO
_34811)
volddl_dmp.c $Date: 2006/03/16 12:21:55 $Revision: 1
.9.2.5.10.9.2.1 PATCH_11.23PI (PHCO_34811)
vxscsilib.c $Date: 2006/07/28 11:44:33 $Revision: 1.
5.102.4.4.4 PATCH_11.23PI (PHCO_34811)
ddlemc.c $Date: 2006/05/08 05:29:49 $Revision: 1.10.
2.4.4.4.4.4 PATCH_11.23PI (PHCO_34811)
ddlhpalua.c $Date: 2006-03-09 $Revision: 1.1.4.1.2.1
3 PATCH_11.23PI (PHCO_34811)
ddlhdsalua.c $Date: 2006/04/11 05:28:59 $Revision: 1
.1.4.2.2.2 PATCH_11.23PI (PHCO_34811)
vxrtpg.c $Date: 2005/08/17 12:59:33 $Revision: 1.1.4
.1.2.1 PATCH_11.23PI (PHCO_33509)
voldipc.c $Date: 2005/12/20 10:34:18 $Revision: 1.44
.2.12.10.1.6.6 PATCH_11.23PI (PHCO_34811)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
ddlapm.c $Date: 2006/09/13 07:32:02 $Revision: 1.5.2
.8.10.1.32.1 PATCH_11.23PI (PHCO_35476)
/etc/vx/type/static/vxprivutil:
priv.c $Date: 2005/08/11 10:36:05 $Revision: 1.22.2.
9.10.1.2.1 PATCH_11.23PI (PHCO_33509)
misc.c $Date: 2006/04/06 08:39:36 $Revision: 1.23.2.
9.10.4.2.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxconfigdump:
misc.c $Date: 2006/04/06 08:39:36 $Revision: 1.23.2.
9.10.4.2.1 PATCH_11.23PI (PHCO_34811)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxrvg:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxprint:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxrlink:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxedit:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxcache:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/etc/vx/type/static/vxmake:
volmakesup.c $Date: 2005-09-23 08:25:24 $Revision: 1
.34.2.7.10.2.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/init.d/vxvm-reconfig:
vxvm-reconfig.sh $Date: 2007/01/29 13:01:31 $Revisio
n: 1.37.6.5.10.2.28.3 PATCH_11.23PI(PHCO_358
90)
/sbin/init.d/vxvm-startup:
vxvm-startup.sh $Date: 2007/01/15 13:23:18 $Revision
: 1.8.6.7.4.5.26.1 PATCH_11.23PI(PHCO_35890)
/sbin/vol_mgr/vxvm/smapi_listener:
smapi_listener.c $Date: 2005/10/30 17:20:35 $Revisio
n: 1.3.2.11.2.5 PATCH_11.23PI (PHCO_33509)
/sbin/vxdctl:
voldctl.c $Date: 2006/04/06 08:39:35 $Revision: 1.43
.2.25.10.5.4.1 PATCH_11.23PI (PHCO_34811)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxcache:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxrelayout:
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxmend:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxplex:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxsd:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxvol:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxvmboot:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxiod:
None.
/sbin/vxdisk:
volpfto_trans.c $Date: 2006/05/16 13:54:55 $Revision
: 1.8.2.2.88.1 PATCH_11.23PI (PHCO_34811)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxdmpadm:
$Header: NAME: License Manager with ELM Support VERS
ION: 3.02.006 BUILT: Nov 21 2003 17:09:29 Co
pyright 1996-2004 VERITAS SOFTWARE Corpora
tion. All Rights Reserved. $
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
ddlapm.c $Date: 2006/09/13 07:32:02 $Revision: 1.5.2
.8.10.1.32.1 PATCH_11.23PI (PHCO_35476)
/sbin/vxrecover:
volrecover.c $Date: 2005/10/23 07:46:12 $Revision: 1
.49.2.23.4.4.6.2 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxdg:
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/sbin/vxsnap:
volsnap.c $Date: 2006-09-13 09:53:07 $Revision: 1.4
2.2.107.4.20.2.1.2.2 PATCH_11.23PI (PHCO_354
76)
get_fmr_info.c $Date: 2006/09/13 10:02:15 $Revision:
1.3.2.1.32.1.32.1 PATCH_11.23PI (PHCO_35476
)
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/conf/mod/dmphpalua:
dmphpalua_apm.c $Date: 2006/05/11 13:40:30 $Revision
: 1.1.4.1.2.6 PATCH_11.23PI (PHKL_34812)
/usr/conf/mod/dmphdsalua:
None.
/usr/lib/hpux32/libvxscsi.sl:
vxscsilib.c $Date: 2006/07/28 11:44:33 $Revision: 1.
5.102.4.4.4 PATCH_11.23PI (PHCO_34811)
vxrtpg.c $Date: 2005/08/17 12:59:33 $Revision: 1.1.4
.1.2.1 PATCH_11.23PI (PHCO_33509)
/usr/lib/vxvm/bin/vxclustadm:
vxclustadm.c $Date: 2006/04/17 09:05:08 $Revision: 1
.61.2.38.4.15.2.2 PATCH_11.23PI (PHCO_34811)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/bin/vxresize:
volresize.c $Date: 2006/11/06 21:04:38 $Revision: 1.
59.2.23.4.10.2.1.2.1 PATCH_11.23PI (PHCO_357
38)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/bin/vxhpcap:
vxhpcap.sh $Date: 2007/01/29 13:01:32 $Revision: 1.1
.2.3 PATCH_11.23PI (PHCO_35890)
/usr/lib/vxvm/bin/vxislvm:
$Header: NAME: License Manager with ELM Support VERS
ION: 3.02.006 BUILT: Nov 21 2003 17:09:29 Co
pyright 1996-2004 VERITAS SOFTWARE Corpora
tion. All Rights Reserved. $
vxislvm.c $Date: 2005/08/16 14:30:26 $Revision: 1.7.
2.1.64.1.6.2 PATCH_11.23PI (PHCO_33509)
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/bin/vxrootmir:
vxrootmir.sh $Date: 2006/08/23 17:03:58 $Revision: 1
.13.2.11.24.1.2.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxparms:
None.
/usr/lib/vxvm/bin/vxclustd:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/bin/vxclustipc:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/bin/vxcheckda:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/bin/vxckdiskrm:
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/bin/vxlvminfo:
vxlvminfo.sh $Date: 2006-08-23 17:03:59 $Revision: 1
.1.2.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxdisksetup:
vxdisksetup.sh $Date: 2006/10/12 14:37:45 $Revision:
1.29.2.11.10.3.2.2.2.2 PATCH_11.23PI (PHCO_
35476)
/usr/lib/vxvm/bin/vxbrk_rootmir:
vxbrk_rootmir.sh $Date: 2006/12/21 11:09:26 $Revisio
n: 1.2.4.1.10.2.22.3 PATCH_11.23PI (PHCO_358
90)
/usr/lib/vxvm/bin/vxcap-lvmpart:
vxcap-lvmpart.sh $Date: 2006/08/23 17:03:56 $Revisio
n: 1.4.26.1.134.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxcap-lvmvol:
vxcap-lvmvol.sh $Date: 2006/08/23 17:03:56 $Revision
: 1.7.8.3.96.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxchg_rootid:
vxchg_rootid.sh $Date: 2006-08-23 17:03:59 $Revision
: 1.2.2.2.22.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxcp_lvmroot:
vxcp_lvmroot.sh $Date: 2006/08/23 17:03:56 $Revision
: 1.23.6.15.4.2.22.1 PATCH_11.23PI (PHCO_354
76)
/usr/lib/vxvm/bin/vxdestroy_lvmroot:
vxdestroy_lvmroot.sh $Date: 2006/08/23 17:03:57 $Rev
ision: 1.6.6.8.10.1.22.1 PATCH_11.23PI (PHCO
_35476)
/usr/lib/vxvm/bin/vxdiskunsetup:
vxdiskunsetup.sh $Date: 2006/11/10 05:41:05 $Revisio
n: 1.19.4.8.76.2 PATCH_11.23PI (PHCO_35738)
/usr/lib/vxvm/bin/vxedvtoc:
vxedvtoc.sh $Date: 2006/08/23 17:03:57 $Revision: 1.
7.26.2.134.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxevac:
vxevac.sh $Date: 2006/08/23 17:03:57 $Revision: 1.9.
2.11.96.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxlvmencap:
vxlvmencap.sh $Date: 2006/08/30 14:56:29 $Revision:
1.17.6.5.6.3.28.2 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxmirror:
vxmirror.sh $Date: 2006/08/23 17:03:58 $Revision: 1.
22.2.10.76.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxnewdmname:
vxnewdmname.sh $Date: 2006/08/23 17:03:58 $Revision:
1.7.26.2.134.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxprtvtoc:
vxprtvtoc.sh $Date: 2006/08/23 17:03:58 $Revision: 1
.7.26.2.134.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/bin/vxres_lvmroot:
vxres_lvmroot.sh $Date: 2006/11/08 13:30:33 $Revisio
n: 1.10.4.9.4.1.24.2 PATCH_11.23PI (PHCO_357
38)
/usr/lib/vxvm/bin/vxtaginfo:
vxtaginfo.sh $Date: 2006/08/23 17:03:58 $Revision: 1
.7.26.3.102.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/diag.d/vxkprint:
vol_copy.c $Date: 2006/09/13 09:54:52 $Revision: 1.3
4.2.6.4.1.32.1 PATCH_11.23PI (PHCO_35476)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/diag.d/vxcheckasl:
$Header: NAME: License Manager with ELM Support VERS
ION: 3.02.006 BUILT: Nov 21 2003 17:09:29 Co
pyright 1996-2004 VERITAS SOFTWARE Corpora
tion. All Rights Reserved. $
vxcheckasl.c $Date: 2006/05/15 07:39:03 $Revision: 1
.6.2.10.6.6.4.1 PATCH_11.23PI (PHCO_34811)
ddlapm.c $Date: 2006/09/13 07:32:02 $Revision: 1.5.2
.8.10.1.32.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/diag.d/vxiotimeout:
vxiotimeout.c $Date: 2006/07/12 04:33:39 $Revision:
1.3.2.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/diag.d/vxr5logutil:
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/diag.d/vxdmpdbprint:
dmpapi.c $Date: 2005/08/14 16:37:37 $Revision: 1.54.
2.14.10.15.2.1 PATCH_11.23PI (PHCO_33509)
voladdslice.c $Date: 2005/08/14 16:37:41 $Revision:
1.15.102.4.6.1 PATCH_11.23PI (PHCO_33509)
voldctlib.c $Date: 2006/04/06 08:39:38 $Revision: 1.
9.2.1.36.1.4.1 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/diag.d/kmsgdump:
None.
/usr/lib/vxvm/diag.d/vxdmpdebug:
vxdmpdebug.sh $Date: 2006/08/23 17:03:57 $Revision:
1.8.6.3.64.2.28.1 PATCH_11.23PI (PHCO_35476)
vxvm:$Source: /project/unixvm-cvs/src/hp/cmd/vxvm/su
pport/vxdmpdebug.sh,v $
/usr/lib/vxvm/diag.d/vxaslkey:
$Header: NAME: License Manager with ELM Support VERS
ION: 3.02.006 BUILT: Nov 21 2003 17:09:29 Co
pyright 1996-2004 VERITAS SOFTWARE Corpora
tion. All Rights Reserved. $
ddlapm.c $Date: 2006/09/13 07:32:02 $Revision: 1.5.2
.8.10.1.32.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/diag.d/vxpatch_volboot:
vxpatch_volboot.sh $Date: 2006-08-23 17:03:59 $Revis
ion: 1.2.4.2.70.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/lib/discovery.d/libvxhdsalua.sl:
ddlhdsalua.c $Date: 2006/04/11 05:28:59 $Revision: 1
.1.4.2.2.2 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/lib/discovery.d/libvxhpalua.sl:
ddlhpalua.c $Date: 2006-03-09 $Revision: 1.1.4.1.2.1
3 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/lib/discovery.d/libvxemc.sl:
ddlemc.c $Date: 2006/05/08 05:29:49 $Revision: 1.10.
2.4.4.4.4.4 PATCH_11.23PI (PHCO_34811)
/usr/lib/vxvm/voladm.d/bin/disk.doinit:
disk.doinit.sh $Date: 2005/09/14 01:22:14 $Revision:
1.11.2.4.70.1 PATCH_11.23PI (PHCO_33509)
/usr/lib/vxvm/voladm.d/bin/disk.analysis:
disk.analysis.sh $Date: 2006/08/23 17:04:00 $Revisio
n: 1.28.6.7.32.2.10.1 PATCH_11.23PI (PHCO_35
476)
/usr/lib/vxvm/voladm.d/bin/disk.anal.ckinit:
disk.anal.ckinit.sh $Date: 2006/08/23 17:04:00 $Revi
sion: 1.21.4.8.72.1 PATCH_11.23PI (PHCO_3547
6)
/usr/lib/vxvm/voladm.d/bin/disk.ckinit:
disk.ckinit.sh $Date: 2006/08/23 17:04:00 $Revision:
1.17.6.7.94.1 PATCH_11.23PI (PHCO_35476)
/usr/lib/vxvm/voladm.d/bin/disk.convert:
disk.convert.sh $Date: 2006/08/23 17:04:01 $Revision
: 1.45.4.6.32.1.10.1 PATCH_11.23PI (PHCO_354
76)
/usr/lib/vxvm/voladm.d/bin/disk.init:
disk.init.sh $Date: 2006/08/23 17:04:01 |
