|
|
|
|
|
vxdmproot - administer support of LVM bootability over DMP
/usr/sbin/vxdmproot add dmp_node | subpath
/usr/sbin/vxdmproot remove dmp_node | subpath
The 1 Logical Volume Manager (LVM) is not capable of switching between multiple paths that may exist to the boot disk. If the path that it selects becomes unavailable at boot time, the root file system is disabled, and the boot fails. The Dynamic Multipathing (DMP) feature of Veritas Volume Manager can be configured to overcome this problem by ensuring that an alternate path is available at boot time.
Support for LVM bootability over DMP is enabled or disabled by running vxdmproot command with the install and uninstall keywords. Individual DMP nodes or subpaths can be added or removed from those supported by using the command with the add and remove keywords, and specifying a DMP node name or operating system native device name as an argument.
LVM bootability over DMP can be verified as being enabled on a system if the following commands show the same major number for the DMP driver and for the boot disk:
Adds support for LVM bootability over DMP for all subpaths of the boot disk. The argument can either be the name of the parent DMP node, or the operating system native device name of the boot disk.
Enables support for LVM bootability over DMP for the current boot disk and all of its subpaths. This allows the system to be booted from any of these subpaths.
Removes support for LVM bootability over DMP for all subpaths of the boot disk. The argument can either be the name of the parent DMP node, or the operating system native device name of the boot disk.
Disables support for LVM bootability over DMP for the current boot disk and all of its subpaths.
The LVM bootability over DMP feature currently does not support operations on:
To avoid data corruption that may render your system unbootable, disable the LVM bootability over DMP feature before performing any operation (for example, Dynamic Reconfiguration (DR)) that shuffles device numbers or device names. The LVM bootability over DMP feature can be re-enabled after completing the reconfiguration and rebooting the system.
If the LVM bootability over DMP feature cannot be enabled by executing vxdmproot install or vxdmproot add, this may be because the file that corresponds to the subpath from which the system has been bootstrapped may be corrupted or the corresponding key is invalid. To correct the problem, remove the directory /etc/vx/lvm-boot and the file /usr/lib/boot/protoext/disk.proto.ext.vxvm.disk.rte, and run the command again.
If the LVM bootability over DMP feature cannot be disabled by executing vxdmproot uninstall or vxdmproot remove, this may be because the bosboot command has failed for some reason, and vxdmproot cannot clean up the ODM database entries. To correct the problem, remove the directory /etc/vx/lvm-boot and the file /usr/lib/boot/protoext/disk.proto.ext.vxvm.disk.rte, and run the command again.
The vxdmproot add and remove commands cannot be used with boot disks that do not belong to an imported volume group. This is due to an 1 limitation, which does not allow you to write to external disks that do not belong to an imported volume group. The workaround is to boot from the disk, and then run vxdmproot install or vxdmproot uninstall to enable or disable the LVM bootability over DMP feature.
bootlist(1), bosboot(1), vxdmpadm(1M)