Troubleshooting DID Driver Problems

In previous releases, Solstice DiskSuite depended on the major number and instance number of the low-level disk device being the same on the two nodes connected to the disk. With this release of Sun Cluster, Solstice DiskSuite requires that the DID major number be the same on all nodes and that the instance number of the DID device be the same on all nodes. The scdidadm(1M) command checks the DID major number on all nodes. The value recorded in the /etc/name_to_major file must be the same on all nodes.

If the scdidadm(1M) command finds that the major number is different, it will report this and ask you to fix the problem and re-run the scdidadm(1M) command. The DID driver uses major number 149; if there is a numbering conflict, you must choose another number for the DID driver. The following procedure enables you to make the necessary changes.

How to Resolve Conflicts With the DID Major Number

1. Choose a number that does not conflict with any other entry in the /etc/name_to_major file.

2. Edit the /etc/name_to_major file on each node and change the DID entry to the number you chose.

3. On each node where the /etc/name_to_major file was updated, execute the following commands.

   phys-hahost1# rm -rf /devices/pseudo/did* /dev/did phys-hahost1# reboot -- -r ...

4. On the node used to run the scdidadm(1M) command, execute the following commands.

   phys-hahost3# rm -f /etc/did.conf phys-hahost3# scdidadm -r

   This procedure resolves mapping conflicts and reconfigures the cluster with the new mappings.