Solaris Cluster metareplace Command for a Replaced cluster 'DID' Disk in SVM Metaset Return the Error "No such file or directory"
(Doc ID 1607179.1)
Last updated on JANUARY 22, 2018
Applies to:Solaris Cluster - Version 3.0 to OSC 4.3 [Release 3.0 to 4.3]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [Release 11.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
In a Solaris Cluster environment the cluster DID device is used in the Solaris Volume Manager (SVM) disksets. If one of the cluster DID disk got broken then the metastat output suggest the metareplace command to be used once the disk got physically replaced.
Example of metastat output when did d5 disk got broken:
dg-cluster/d100: Mirror Submirror 0: dg-cluster/d102 State: Okay Submirror 1: dg-cluster/d101 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 12597888 blocks (6.0 GB) dg-cluster/d102: Submirror of dg-cluster/d100 State: Okay Size: 12597888 blocks (6.0 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare d4s4 0 No Okay No dg-cluster/d101: Submirror of dg-cluster/d100 State: Needs maintenance Invoke: metareplace dg-cluster/d100 d5s4 <new device> Size: 12597888 blocks (6.0 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare d5s4 0 No Maintenance No
Running the suggested metareplace command once the disk has been replaced and the did device associated to it has been synced to the new disk devid, the following error has been reported
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!