Veritas Volume Manager 4.1 Release Notes (5900-0590, March 2010)

After a layered volume is resized, the volume, plex and subdisk names associated with the
subvolumes, are changed.
• Problems with Relayout Using the vxassist Command
Problem
The vxassist relayout operation requires all mirrors in the volume to have the same
layout
Workaround
If the volume contains mirrors with different layouts, then you need to relayout the mirror
plexes to the same layout before performing the volume relayout operation.
• Free Space Reported Differently
Problem
vxdg free reports free space differently than vxprint-ht.
Workaround
None. The vxdg free report is the correct one.
• Subdisks are not Aligned on Cylinder Boundaries After a Relayout
Problem
When relayout is performed on a volume, VxVM 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.
Workaround
To ensure that the subdisks in a volume are grown using contiguous disk space, specify the
attribute layout=nodiskalign to vxassist, as follows:
# vxassist growby volume length layout=nodiskalign
NOTE: Specifying layout=nodiskalign permanently enforces this layout policy on the
volume.
• Stopping and Starting Layered Volumes
Problem
If a layered volume is open that is in use, and a vxvol stop command is issued, then the
sub-volumes get disabled. The layered volume however remains enabled.
Workaround
As of now there is no workaround for this problem. Users are required to check whether a
layered volume is open before issuing a vxvol stop command on it.
• VxVM Commands do not Show Current Status of VxVM Disks
Problem
The VEA and frequently used VxVM commands, such as vxdisk and vxprint, sometimes
do not show the current status of disks managed by VxVM. VxVM builds and maintains a
configuration database in system memory. This configuration database also includes Disk
Access (DA) records with information about the disk devices obtained by the vxconfigd
scan pass. VxVM relies on the operating system kernel to notify the disk status changes. The
HP-UX kernel does not currently notify VxVM of disk status changes.
Workaround
Use either of the following commands to force an update of the VxVM configuration database:
# vxdisk online diskname
This command updates the status of the disk identified by diskname.
Known Problems And Workaround 13