Error opening the snapshot disks using given transport mode: Status 23
Hi,
Bit of a strange one this !
7.6.0.3 HP-UX Master, VMware backups using SAN transport to 5230's as the backup hosts.
All was working ok.
New LUN added, made visible to the appliances, cant back any VM up on new LUN. Get the status 23 error.
My storage guy assures me LUN has same access as all other LUNs so should be ok.
Now a few other previously working backups have started to fail. Ones residing on the old LUNs !
I have enabled vxms logging up to 8 but all I see in the logs is below.
Its says disk open error. I know that, just need to know why !
Any help much appreciated - Darren
07/21/2015 16:13:19 : setTimeouts:VMWareVIClient.cpp:110 <TRACE> : out
07/21/2015 16:13:19 : connectToHost:VixGuest.cpp:937 <TRACE> : out
07/21/2015 16:13:19 : openLeafSnapshotDisks:VixGuest.cpp:462 <TRACE> : connectToHost() success
07/21/2015 16:13:19 : openLeafSnapshotDisks:VixGuest.cpp:483 <DEBUG> : Calling vdOpen(Disk: [3par_Live_LUN20] VM_NAME/VM_NAME-000002.vmdk, Flags: 0x4)
07/21/2015 16:13:19 : vdOpen:VixInterface.cpp:437 <TRACE> : in
07/21/2015 16:13:19 : vdOpen:VixInterface.cpp:464 <INFO> : Calling VixDiskLib_Open()
07/21/2015 16:13:28 : vdOpen:VixInterface.cpp:471 <DEBUG> : Done with VixDiskLib_Open(): 0
07/21/2015 16:13:28 : vdOpen:VixInterface.cpp:492 <ERROR> : VixDiskLib_Open() error: 13
07/21/2015 16:13:28 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-07-21T16:13:28.476+01:00 [7FB0F153E700 trivia 'HttpConnectionPool-000000'] [DecC
onnectionCount] Number of connections to <cs p:00007fb0e402d950, TCP:vcenter-b:443> decremented to 0
07/21/2015 16:13:28 : vdOpen:VixInterface.cpp:437 <TRACE> : out
07/21/2015 16:13:28 : openLeafSnapshotDisks:VixGuest.cpp:494 <DEBUG> : vdOpen() error = 13. Calling closeLeafSnapshotDisks()
07/21/2015 16:13:28 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-07-21T16:13:28.476+01:00 [7FB0EBFFF700 trivia 'ThreadPool'] HandleWork() leaving
07/21/2015 16:13:28 : closeLeafSnapshotDisks:VixGuest.cpp:382 <TRACE> : in
07/21/2015 16:13:28 : closeLeafSnapshotDisks:VixGuest.cpp:382 <TRACE> : out
07/21/2015 16:13:28 : openLeafSnapshotDisks:VixGuest.cpp:407 <TRACE> : out
07/21/2015 16:13:28 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-07-21T16:13:28.476+01:00 [7FB0F157F700 trivia 'ThreadPool'] ThreadPool[idle:3, bus
y_io:1, busy_long:0] HandleWork(type: 0, fun: N5boost3_bi6bind_tIvNS_4_mfi3mf3IvN7Vmacore6System14ThreadPoolAsioERKNS_10shared_ptrINS4_9ExceptionEEEiRKNS4_7FunctorIvPS8_iNS4_3Ni
lESE_SE_SE_SE_EEEENS0_5list4INS0_5valueINS4_3RefIS6_EEEENSK_IS9_EENSK_IiEENSK_ISF_EEEEEE)
This has now been fixed in conjunction with Support.
There were conflicts between the scsci layer and the VxDMP layer and we were seeing some disks twice and some disks not at all.
To clear these conflicts we had to rebuild the device tree.
Commands performed in conjunction with support as below.
mv /etc/vx/array.info /etc/vx/array.info.old
mv /etc/vx/disk.info /etc/vx/disk.info.old
mv /etc/vx/jbod.info /etc/vx/jbod.info.old
mv /etc/vx/dmppolicy.info /etc/vx/dmppolicy.info.old --> If this file exists else ignore.
Remove all the entries from the /dev/dsk, /dev/rdsk, /dev/vxdmp, and /dev/vx/rdmp directories except entires for bootdisk or bootmirror from the following directories.
rm -rf /dev/vx/dmp/*
rm -rf /dev/vx/rdmp/*
rm -rf /dev/sd*
vxconfigd -k -x cleartempdirWe are now back with successful SAN based backups.
This fix applied to us and may not apply to your issue so I would not recommend these being issued without support in attendance.
- Darren
