Systems with the same hostid in /etc/vx/volboot will import disk group(s) imported on other systems

book

Article ID: 100030071

calendar_today

Updated On:

Resolution

Volume Manager uses the hostid contained in the/etc/vx/volboot file to identify the disk group host during bootup.  If the hostid is found written to a disk group that Volume Manager discovers during start up, it will automatically be imported, regardless of whether the disk group is flagged as imported or not.

If two systems share access to the same disk group and both system have the same hostid configured in their /etc/vx/volboot file, the systems will import that disk group at start up, possibly causing corruption as the disk group could already be imported on the other system.

To verify this condition execute the following commands on all affected systems:  

# cat /etc/vx/volboot | grephostid
hostid

# hostname


The hostname reported by the hostname command should be the same as the hostid contained in the /etc/vx/volboot file.

If the names do not match you need to reinitialize the volboot file using the following command.  Note: Do not edit the /etc/vx/volboot file by hand.

# vxdctl init  

The vxdctl init command does not interrupt any Volume Manager services and is safe to run in a production environment.
 

 

Issue/Introduction

Systems with the same hostid in /etc/vx/volboot will import disk group(s) imported on other systems