VERITAS Volume Manager 4.1 Release Notes (5900-0591, March 2010)

VERITAS Volume Manager 4.1 Release Notes
Known Problems and Workarounds
Chapter 1 27
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 it of 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 diskname disk.
# vxdctl enable
This command updates the status of all the VxVM disks.
NOTE The vxdctlenable command initiates an entire disk device scan. Therefore the
length of time VxVM takes to scan all of the devices in the environment of that
particular host will increase as the number of devices increases. If you know
which disk’s state has been changed, it is faster to use vxdiskonline diskname
to update that disk only.
Run vxdctl enable to Show Status Changes for LVM Disks
• Problem: Base-VXVM output will not reflect status changes for LVM disks until
vxdctl(1M) is run. For example, if you clear an LVM disk with pvremove(1M), the
vxdisklist command will still list the status of that disk as LVM, until you run the
vxdctlenable command. This is also true for VEA output and the output from other
VxVM commands.
• Workaround: Run vxdctlenable after making any changes to LVM disks to update VxVM
database.
Possible Incorrect I/O Counts On Objects
• Problem: The VxVM configuration daemon may hang inside the kernel while processing a
configuration change, because of incorrect object I/O counts. The I/O count could become
incorrect due to a race condition in the Base-VXVM kernel. Since vxconfigd is hanging
inside the kernel, VxVM utilities will not work.
• Workaround: None. Contact VERITAS Technical Support for help in analyzing this
problem.
Configuration Issues
vxconfigd daemon hangs while configuring VxVM