VERITAS Storage Foundation 4.1 Release Notes

Software Issues
30 VERITAS Storage Foundation Release Notes
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
[i134932]
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, 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.
Maximum Size of a VxVM Volume
VxVM supports volume lengths up to 2^63-1 disk sectors when using VERITAS-specific ioctl
calls. However, system calls such as seek, lseek, read and write are limited to a maximum
offset that is determined by the operating system. For a system that supports large files, this is
usually 2^63-1 bytes. Otherwise, the maximum offset value is usually 2^31-1 bytes (1 byte less
than 2 terabytes). [i141024]
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, is performing I/O from/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.