VxVM volumes may get locally disabled on secondary nodes after InfoScale upgrade on Solaris 11 with LDOM (4054250)

Last published : Sep 18, 2026
In a rare occurrence, after an InfoScale upgrade on Solaris 11 with an LDOM configuration, a few VxVM volumes may get locally disabled on secondary nodes. Their state may appear as LDISABLED in the vxprint command output, for example:
\# vxprint | grep LDISABLED
v  vol1         fsgen        LDISABLED 2097152 -        ACTIVE   -       -
v  vol1-L01     fsgen        LDISABLED 419456  -        ACTIVE   -       -
...
This issue occurs because some of the DMP disks may not be enabled during the initial device discovery after an InfoScale upgrade. These disks may get enabled again later during the next device discovery, when vxdisk scandisks is run internally.
Workaround: If a volume is in the LDISABLED state after an InfoScale upgrade, perform the following tasks to enable the volume.
  1. Enable the LDISABLED volume.
# vxvol -g vrts_dg enable vol1
  1. Clear any faults on the dependent VCS resources.
# ./hares -clear cvmvoldg -sys puninsunt4bl04-v01
# ./hares -clear cvmvoldg -sys puninsunt4bl04-v02
  1. Bring the dependent VCS resources online.
# ./hagrp -offline vrts_vea_cfs_int_cfsmount1 -sys puninsunt4bl04-v02
# ./hagrp -offline vrts_vea_cfs_int_cfsmount2 -sys puninsunt4bl04-v02
# ./hagrp -online vrts_vea_cfs_int_cfsmount1 -sys puninsunt4bl04-v02
# ./hagrp -online vrts_vea_cfs_int_cfsmount2 -sys puninsunt4bl04-v02