Veritas Volume Manager known issues

Last published : Sep 09, 2026
Related information
Storage Foundation known issues
vradmin delsec fails to remove a secondary RVG from its RDS (3983296)FSS disk group creation fails for clusters with eight or more nodes that have several directly attached disks (3986110)Core dump issue after restoration of disk group backup (3909046)Failed verifydata operation leaves residual cache objects that cannot be removed (3370667)LUNs claimed but not in use by VxVM may report \"Device Busy\" when it is accessed outside VxVM (3667574)VxVM commands may respond slowly when you disable the primary paths and run the vxdisk scandisks command (3450060)Unable to set master on the secondary site in VVR environment if any pending I/O's are on the secondary site (3874873)Mounting CFS under VVR may fail, after rolling upgrade phase 1 on one node.VRAS verifydata command fails without cleaning up the snapshots createdSmartIO VxVM cache invalidated after relayout operation (3492350)Performance impact when a large number of disks are reconnected (2802698)device.map must be up to date before doing root disk encapsulation (2202047)Veritas Volume Manager (VxVM) might report false serial split brain under certain scenarios (1834513)Co-existence check might fail for CDS disksRecovery and rollback to original configuration may not succeed if the system reboots while the online migration setup is in partial state (2611423)Disk group import of BCV LUNs using -o updateid and -ouseclonedev options is not supported if the disk group has mirrored volumes with DCO or has snapshots (2831658)After devices that are managed by EMC PowerPath lose access to storage, Veritas Volume Manager commands are delayed (2757198)vxresize does not work with layered volumes that have multiple plexes at the top level (3301991)Running the vxdisk disk set clone=off command on imported clone disk group luns results in a mix of clone and non-clone disks (3338075)Restarting the vxconfigd daemon on the slave node after a disk is removed from all nodes may cause the disk groups to be disabled on the slave node (3591019)Failback to primary paths does not occur if the node that initiated the failover leaves the cluster (1856723)Issues if the storage connectivity to data disks is lost on a CVM slave node while vxconfigd was not running on the node (2562889)The vxcdsconvert utility is supported only on the master node (2616422)Re-enabling connectivity if the disks are in local failed (lfailed) state (2425977)Issues with the disk state on the CVM slave node when vxconfigd is restarted on all nodes (2615680)Plex synchronization is not completed after resuming synchronization on a new master when the original master lost connectivity (2788077)A master node is not capable of doing recovery if it cannot access the disks belonging to any of the plexes of a volume (2764153)CVM fails to start if the first node joining the cluster has no connectivity to the storage (2787713)CVMVolDg agent may fail to deport CVM disk group when CVMDeportOnOffline is set to 1The vxsnap print command shows incorrect value for percentage dirtyMksysb restore fails if physical volumes have identical PVIDs (3133542)vxconfigd daemon hangs when Veritas InfoScale Storage or Veritas InfoScale Enterprise is run on AIX7.2SP1 or any earlier version (3901325)Systems may panic after GPT disk resize operation (3930664)