VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes
Patches and Fixes in This Version
Chapter 142
Free Space Reported Differently
Problem: vxdg free reports free space differently than vxprint -ht.
Workaround: None.
Subdisks are not Aligned on Cylinder Boundaries After a
Relayout
When relayout is performed on a volume, Volume Manager does not
grow subdisks such that they end on cylinder boundaries. If you
subsequently increase the size of the volume, its subdisks are not
grown using contiguous disk space.
To ensure that a volume’s subdisks are grown using contiguous disk
space, specify the attribute layout=nodiskalign to vxassist, as shown
here:
# vxassist growby volume length layout=nodiskalign
NOTE Specifying layout=nodiskalign permanently enforces
this layout policy on the volume.
Resizing Layered Volumes Fails while Resynchronization is
Ongoing.
Problem: Due to the current implementation to handle the resize of
layered volumes, it is recommended that you do not grow or shrink
layered volumes (stripe-mirror, concat-mirror, and so on) while
resynchronization is ongoing.
Internally, VxVM converts the layout of layered volumes and updates
the configuration database before it shrinksor grows their sizes. This
causes any ongoing operation, such as the resynchronization, to fail.
Workaround: 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, the user has to use vxassist convert to restore
the volume to its original layout.
After a layered volume is resized, the volume names, the plex names
and the subdisk names associated with the subvolumes, are changed.