How to Resolve a Disk-Path Status Error

If the following events occur, DPM might not update the status of a failed path when it comes back online:

• A monitored-path failure causes a node reboot.

• The device under the monitored DID path does not come back online until after the rebooted node is back online.

The incorrect disk-path status is reported because the monitored DID device is unavailable at boot time, and therefore the DID instance is not uploaded to the DID driver. When this situation occurs, manually update the DID information.

1. From one node, update the global-devices namespace.

   # cldevice populate

2. On each node, verify that command processing has completed before you proceed to the next step.

   The command executes remotely on all nodes, even though the command is run from just one node. To determine whether the command has completed processing, run the following command on each node of the cluster.

   # ps -ef | grep scgdevs

3. Verify that, within the DPM polling time frame, the status of the faulted disk path is now Ok.

   # cldevice status disk-device Device Instance Node Status --------------- ---- ------ dev/did/dsk/dN phys-schost-1 Ok