Home > Veritas Storage Foundation™ Volume Manager Manual Pages
/usr/sbin/vxdmproot remove dmp_node | subpath
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 command shows the same major number for the DMP driver and for the boot disk:
ls -l /dev/`bootinfo -b` /dev/vx/dmpconfig
To migrate a root disk from LVM to DMP control:
chdev -l hdisk373 -a pv=clear
If the SAN disk is already multipathed by DMP, this command needs to be run for all of the paths to the disk.
alt_disk_install -C hdisk373
To configure DMP, follow the steps in "Configuring DMP support for booting over a SAN."
To migrate a SAN root disk from MPIO to DMP control:
To configure DMP support for booting over a SAN:
# lspv | grep rootvg hdisk374 00cbf5ce56def54d rootvg active hdisk375 00cbf5ce56def54d rootvg hdisk376 00cbf5ce56def54d rootvg hdisk377 00cbf5ce56def54d rootvg
The PVID and volume group entries in the second and third columns should be identical for all the paths.
# chdev -l hdisk377 -a pv=yes hdisk377 changed
# bootlist -m normal -o hdisk374 blv=hd5 hdisk375 blv=hd5 hdisk376 blv=hd5 hdisk377 blv=hd5
In this example, the default boot volume, hd5, should be shown for each path.
bootlist -m normal hdisk377 blv=hd5
# ls -l /dev/`bootinfo -b` /dev/vx/dmpconfig brw------- 1 root system 42, 1 Sep 07 16:16 /dev/hdisk374 crw------- 1 root system 42,65535 Nov 24 14:25 /dev/vx/dmpconfig
- Adds support for LVM bootability over DMP for all subpaths of the specified 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 specified 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.
- Root volume groups that span multiple disks. In this case, DMP is enabled only on the disk which has the boot volume, and not for any other disks in the root volume group.
- LVM boot disk mirrors
- Disk arrays other than A/A arrays.
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 a reconfiguration is performed while the LVM bootability over DMP feature is enabled, use the following commands to reconfigure DMP before the system is next rebooted:
cfgmgr vxdmproot install
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 a 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.
Last updated: 1 June 2005
Copyright ©2009 Symantec Corporation
All rights reserved.