VxVM continues to display LUN even though Solaris does not see it (Leadville stack) - cfgadm reports failing state
Article ID: 100001076
Updated On:
Resolution
Solaris"format" utility does not display the removed LUN, however, vxdisk list does -cfgadm is reporting the device paths as 'failing'
ERROR CODE/MESSAGE:
vxdisk listemc0_65535
Device:emc0_65535
devicetag:emc0_65535
type:auto
flags: errorprivate autoconfig
pubpaths:block=/dev/vx/dmp/emc0_65535 char=/dev/vx/rdmp/emc0_65535
guid:-
udid:INVALID
site:-
errno: Devicepath not valid
Multipathinginformation:
numpaths:6
c5t5006048C52A53E27d196state=disabled
c4t5006048452A53E38d195state=disabled
c6t5006048C52A53E07d195state=disabled
c3t5006048452A53E18d196s2state=disabled
c4t5006048452A53E38d196state=disabled
c6t5006048C52A53E07d196state=disabled
DIAGNOSTICSTEPS:
As theleadville stack still reports the device paths for the removed LUN in a"failing" state rather than the expected "unusable" state, the LUN detailscannot be removed from DMP nor VxVM
# cfgadm -aloshow_FCP_dev | grep -i failing
c3::5006048452a53e18,196disk connected configured failing
c4::5006048452a53e38,195disk connected configured failing
c4::5006048452a53e38,196disk connected configured failing
c5::5006048c52a53e27,196disk connected configured failing
c6::5006048c52a53e07,195disk connected configured failing
c6::5006048c52a53e07,196disk connected configured failing
PROBLEMDESCRIPTION:
Solaris"format" does not display the removed LUN anymore, however, "vxdisk list" doesshow the removed LUN.
Why?
CAUSE:
cfgadm failedto report the removed LUN as unusable or the incorrect LUN removal steps were performed
Documents sent in regards to LUN provisioning.
SOLUTION:
Process sent inan attempt to clean-up the removed lun from all aspect of the I/O stack,Solaris/DMP and VxVM
Currently the paths are disabled from the VxVM/DMP perspective
Multipathing information:
numpaths:6
c5t5006048C52A53E27d196state=disabled
c4t5006048452A53E38d195state=disabled
c6t5006048C52A53E07d195state=disabled
c3t5006048452A53E18d196s2state=disabled
c4t5006048452A53E38d196state=disabled
c6t5006048C52A53E07d196state=disabled
However, theleadville stack is reporting the devices as "failing".
I guess the"vxdisk rm "command possibly failed, or the cfgadm unconfigureoperation failed earlier during the LUN removal process.
Recommendations:
Please run:
1.] vxdisk rmemc0_65535
2.] luxadm -eoffline /dev/rdsk/c#t#d#s2 for all 6 of the device paths
c5t5006048C52A53E27d196s2
c4t5006048452A53E38d195s2
c6t5006048C52A53E07d195s2
c3t5006048452A53E18d196s2
c4t5006048452A53E38d196s2
c6t5006048C52A53E07d196s2
3.] "cfgadm-alo show_FCP_dev" should now convert the "failing" state to "unusable"
Once in the"unusable" state, cfgadm can remove the LUN
4.] cfgadm -ounusable_FCP_dev -c unconfigure
c3::5006048452a53e18,196disk connected configured failing
c4::5006048452a53e38,195disk connected configured failing
c4::5006048452a53e38,196disk connected configured failing
c5::5006048c52a53e27,196disk connected configured failing
c6::5006048c52a53e07,195disk connected configured failing
c6::5006048c52a53e07,196disk connected configured failing
cfgadm commands(x4) would be:
cfgadm -ounusable_FCP_dev -c unconfigure c3::5006048452a53e18
cfgadm -ounusable_FCP_dev -c unconfigure c4::5006048452a53e38
cfgadm -ounusable_FCP_dev -c unconfigure c5::5006048c52a53e27
cfgadm -ounusable_FCP_dev -c unconfigure c6::5006048c52a53e07
cfgadm -aloshow_FCP_dev should no longer report the ,195 and ,196 entries, if so, pleaserun "defsadm -Cv" to clean-up the Solaris stack
If the abovecommand complete fine, please run
# vxdisk scandisks
# vxddladm assign names
# vxdisk -oalldgs list
Issue/Introduction
VxVM continues to display LUN even though Solaris does not see it (Leadville stack) - cfgadm reports failing state
Was this article helpful?
Yes
No
Powered by
