VERITAS Volume Manager 3.1 Administrator's Guide

Volume Manager Operations
Common Volume Manager Commands
Chapter 3 139
starting at system startup time.
You can stop hot-relocation at any time by killing the vxrelocd process
(this should not be done while a hot-relocation attempt is in progress).
You can make some minor changes to the way the vxrelocd program
behaves by either editing the vxrelocd line in the startup file that
invokes the vxrelocd program (/sbin/rc2.d/S095vxvm-recover) or
killing the existing vxrelocd process and restarting it with different
options. After making changes to the way the vxrelocd program is
invoked in the startup file, reboot the system so that the changes take
effect. If you kill and restart the daemon instead, make sure that
hot-relocation is not in progress when you kill the vxrelocd process. You
should also restart the daemon immediately so that hot-relocation can
take effect if a failure occurs.
Thevxrelocd command can be altered as follows:
• By default, the vxrelocd command sends electronic mail to root
when failures are detected and relocation actions are performed. You
can instruct the vxrelocd program to notify additional users by
adding the appropriate user names and invoking the vxrelocd
program, as follows:
# vxrelocd root user_name1 user_name2 &
• To reduce the impact of recovery on system performance, you can
instruct the vxrelocd command to increase the delay between the
recovery of each region of the volume, as follows:
# vxrelocd -o slow[= IOdelay ] root &
where the optional IOdelay indicates the desired delay (in milliseconds).
The default value for the delay is 250 milliseconds. For more
information, see the vxrelocd(1M) manual page.
Options
Command options include:
•-O
This option is used to revert to an older version. Specifying
VxVM_version -O tells the vxrelocd command to use the relocation
scheme in that version.
•-s