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

• Using vxdiskadm to Replace a Failed Disk
Problem
The vxdiskadm command requires two attempts to replace a failed disk. The first attempt
can fail with a message of the form:
/usr/lib/vxvm/voladm.d/bin/disk.repl: test: argument expected
Workaround
The command is not completed and the disk is not replaced. If you rerun the command,
using Option 5 of the vxdiskadm command, the replacement successfully completes.
• Replacement of the old_layout Attribute
Problem
The vxdisksetup command displays the following error message:
Attribute unrecognized
when the old_layout attribute is used to make a disk into a VxVM controlled disk.
Workaround
The old_layout attribute is no longer supported. Use the -noreserve attribute instead.
• Using vxvol and vxmend with Layered Volumes
Problem
When vxmend is executed on the top level volume to change the state of a volume, it is
executed only on the top level volume and the change is not propagated to the lower level
volumes. As a result, the volume states can become inconsistent and a subsequent vxvol
init command might fail.
The vxvol command also exhibits the same problem. When a vxvol init command is
executed on the top level volume, the change is not propagated to the volumes corresponding
subvolumes.
Workaround
When executing the vxvol or vxmend command on a layered volume, first issue the
command to the lower level volumes in a bottom-up fashion and then execute the commands
on the top-level volume.
In this example, a volume, vol, has two subvolumes, vol-L01 and vol-L02. The state of
the volumes is first set to empty, and then the initialization commands are executed:
# vxmend -o force -g mydg fix empty vol
# vxmend -o force -g mydg fix empty vol-L01
# vxmend -o force -g mydg fix empty vol-L02
# vxvol -g mydg init zero vol
# vxvol -g mydg init zero vol-L01
# vxvol -g mydg init zero vol-L02
• Growing or Shrinking Layered Volumes
Problem
Resize of layered volumes, does not work during resynchronization. This limitation does
not apply to ISP layered volumes.
Workaround
Internally, VxVM converts the layout of layered volumes and updates the configuration
database before the actual resize operation. 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.
12 Veritas Volume Manager 4.1 Release Notes