|
|
|
|
|
Hot-relocation is turned on as long as the vxrelocd process is running. You should normally leave hot-relocation turned on so that you can take advantage of this feature if a failure occurs. However, if you choose to disable hot-relocation (perhaps because you do not want the free space on your disks to be used for relocation), you can prevent vxrelocd from starting at system startup time by editing the startup file that invokes vxrelocd. This file is /lib/svc/method/vxvm-recover in Solaris 10, or /etc/init.d/vxvm-recover in previous releases of the Solaris OS.
You can alter the behavior of vxrelocd as follows:
vxrelocd starting, comment out the entry that invokes it in the startup file:
vxrelocd sends electronic mail to root when failures are detected and relocation actions are performed. You can instruct vxrelocd to notify additional users by adding the appropriate user names as shown here:
vxrelocd to increase the delay between the recovery of each region of the volume, as shown in the following example:
nohup vxrelocd -o slow[=IOdelay] root &
where the optional IOdelay value indicates the desired delay in milliseconds. The default value for the delay is 250 milliseconds.
On a Solaris 10 system, after making changes to the way vxrelocd is invoked in the startup file, run the following command to notify that the service configuration has changed:
# svcadm refresh vxvm/vxvm-recover
For previous releases of the Solaris OS, reboot the system.
You can also stop hot-relocation at any time by killing the vxrelocd process (this should not be done while a hot-relocation attempt is in progress).
When executing vxrelocd manually, either include /etc/vx/bin in your PATH or specify vxrelocd's absolute pathname, for example:
Alternatively, you can use the following command:
# nohup /etc/vx/bin/vxrelocd root user1 user2 &
See the vxrelocd(1M) manual page.