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

# vxdctl enable
This command updates the status of all the VxVM disks.
NOTE: The vxdctl enable command initiates an entire disk device scan. Therefore the
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 vxdisk online <diskname> to update that disk only.
• VxVM does not Show Status Changes for LVM Disks
Problem
VxVM output do not reflect status change for LVM disks until vxdctl (1M) is run. For example,
if you clear an LVM disk with pvremove (1M), the vxdisk list command still lists the status of
that disk as LVM. This is holds true for VEA output and the output from other VxVM
commands.
Workaround
Run vxdctl enable 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 VxVM kernel. Since vxconfigd is hanging inside the kernel, VxVM
utilities will not work.
Workaround
None. Contact HP Technical Support for help.
Device Issues
Following device issues are identified:
• Business Copy (BC) Limitation on XP Disk Arrays
Problem
VxVM does not allow import of the volumes from one BC on a node where volumes have
the same disk and group identification. If the Primary (P-Vol) volume is accessible, then this
volume will be used. The Secondary (S-Vol) volume is imported only if the P-Vol is
inaccessible at the time of import.
Workaround
None. There is no support available for changing the disk group identification (group id)
on XP BC volumes.
NOTE: In cases where VxVM and XP512 BCs are being used together; if the BCs are split,
you cannot then import the split BC to the machine on which P-Vol is currently being used.
The reason for this is that the split BC and the P-Vol will have the same private region, and
VxVM allows you to import only one of them. By default, it only chooses P-Vol. However,
you can import the split BC (S-Vol) onto a secondary host.
• Enclosure-based Naming on Persistent Simple or Nopriv Disks
Problem
On systems that have persistent simple or nopriv disks, these disks may be put into an
error state if you change to enclosure-based naming.
Workaround
14 Veritas Volume Manager 4.1 Release Notes