Veritas Volume Manager 5.0 Release Notes (5900-0593, March 2010)

Veritas Volume Manager 5.0 Release Notes
Known Issues
Chapter 124
# vxdisk scandisks
All the nodes should now be using the primary path. [579536]
• Volume persists in SYNC state
If a node leaves the cluster while a plex is being attached to a volume, the volume can
remain in the SYNC state indefinitely. To avoid this, after the plex attach completes,
resynchronize the volume manually with the following command:
# vxvol -f resync volume
[20448]
• RAID-5 volumes
VxVM does not currently support RAID-5 volumes in cluster-shareable disk groups.
• File systems supported in cluster-shareable disk groups
The use of file systems other than Veritas Storage Foundation Cluster File System
(SFCFS) on volumes in cluster-shareable disk groups can cause system deadlocks.
• Reliability of information about cluster-shareable disk groups
If the vxconfigd program is stopped on both the master and slave nodes and then
restarted on the slaves first, VxVM output and VEA displays are not reliable until the
vxconfigd program is started on the master and the slave is reconnected (which can take
about 30 seconds). In particular, shared disk groups are marked disabled and no
information about them is available during this time. The vxconfigd program must
therefore be started on the master first.
• Messages caused by open volume devices
When a node aborts from the cluster, open volume devices in shared disk groups on which
I/O is not active are not removed until the volumes are closed. If this node later joins the
cluster as the master while these volumes are still open, the presence of these volumes
does not cause a problem. However, if the node tries to rejoin the cluster as a slave, this
can fail with the following error message:
cannot assign minor #
WARNING:minor number ### disk group group in use
Remote Mirror issues
• Volume relayout
Volume relayout is not supported for site-confined volumes or for site-consistent volumes
in this release. [528677]