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

Veritas Volume Manager 5.0 Release Notes
Known Issues
Chapter 120
# vxvol -g mydg init zero vol-L01
# vxvol -g mydg init zero vol-L02
10. Growing or shrinking layered volumes
Due to the current implementation of a resize of layered volumes, it is recommended
that you do not grow or shrink layered volumes (for example, stripe-mirror or
concat-mirror) during resynchronization. This limitation does not apply to ISP layered
volumes.
Internally, VxVM converts the layout of layered volumes and updates the
configuration database before it does the actual resize. This causes any ongoing
operation, such as a resynchronization, to fail.
If the system reboots before the grow or shrink of a layered volume completes, the
volume is left with an intermediate layout. In this case, you have to use vxassist
convert to restore the volume to its original layout.
After a layered volume is resized, the volume, plex, and subdisk names associated
with the subvolumes, are changed.
11. vxconfigd hangs due to a faulty disk
If I/O hangs for some reason, such as a disk failing while the VxVM configuration
daemon, vxconfigd performing I/O from or to the disks, there is no way to
communicate with vxconfigd via signals or native interprocess communication. This
can potentially cause two kinds of problem:
— The node becomes unavailable for VxVM administrative commands.
— In a clustered or HA environment where Veritas Cluster Server agents need to
communicate with vxconfigd to determine the health of VxVM components,
service groups start timing out and failing.
• Restoring storage after failure
When all failed paths to the storage are restored, dmp automatically re-discovers them.
However, you would have to run vxdctl enable for VxVM/CVM to get the disks back
online. If the paths were restored before the reboot happens, then as part of boot, device
discovery would happen automatically. However if the paths are restored after the
reboot, and we have to run vxdctl enable to have VxVM rescan and rediscover the failed
devices. Also, if some operation had failed due to above reason, the operation needs to be
retried after discovery of device.
• Current naming scheme