[SunHELP] Mirroring Setup After a hardware error on Boot Disk

[Michael Karl]

Hey,

I'm thinking, that you didn't clear with "metadb -d" the old replica-entries
for the fault old c0t0d0s3 and didn't create new on the actual c0t0d0s3.

1. metadb -d c0t0d0s3
2. metadb -a -c 3 -f c0t0d0s3

Maybe, this should help ... also with rebooting.

Michael

> Hello Administrators,
> There is a hardware problem with the Boot Disk (disk0, i.e.
> /dev/dsk/c0t0d0s2).  The disk is replaced.  metadb commands are executed
> to re-define the database.  After re-establishing the mirroring (metastat
> shows everything ok), metadb -i shows:
> 
>       flags           first blk       block count
>    a        u         16              1034            /dev/dsk/c0t0d0s3
>    a        u         1050            1034            /dev/dsk/c0t0d0s3
>    a        u         2084            1034            /dev/dsk/c0t0d0s3
>    a    p  luo        16              1034            /dev/dsk/c0t1d0s3
>    a    p  luo        1050            1034            /dev/dsk/c0t1d0s3
>    a    p  luo        2084            1034            /dev/dsk/c0t1d0s3
> o - replica active prior to last mddb configuration change
> u - replica is up to date
> l - locator for this replica was read successfully
> c - replica's location was in /etc/lvm/mddb.cf
> p - replica's location was patched in kernel
> m - replica is master, this is replica selected as input
> W - replica has device write errors
> a - replica is active, commits are occurring to this replica
> M - replica had problem with master blocks
> D - replica had problem with data blocks
> F - replica had format problems
> S - replica is too small to hold current data base
> R - replica had device read errors
> 
> Before the hardware problem, it was  like :
>  flags           first blk       block count
>    a m  p  luo        16              1034            /dev/dsk/c0t0d0s3
>    a    p  luo        1050            1034            /dev/dsk/c0t0d0s3
>    a    p  luo        2084            1034            /dev/dsk/c0t0d0s3
>    a    p  luo        16              1034            /dev/dsk/c0t1d0s3
>    a    p  luo        1050            1034            /dev/dsk/c0t1d0s3
>    a    p  luo        2084            1034            /dev/dsk/c0t1d0s3
> 
> As 'l' and 'm' are missing on /dev/dsk/c0t0d0s2, will a reboot cause
> failure ?
> 
> Much appreciated your valuable input.
> Y. M. 
> 
> --------------------------------------------------
> THIS EMAIL COMMUNICATION IS INTENDED ONLY FOR THE PERSON OR ENTITY TO WHICH IT
> IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL AND/OR PRIVILEGED INFORMATION. ANY
> USE OF THIS INFORMATION BY PERSONS OR ENTITIES OTHER THAN THE INTENDED
> RECIPIENT IS PROHIBITED.  IF YOU RECEIVED THIS IN ERROR, PLEASE CONTACT THE
> SENDER AND DELETE THE EMAIL AND ALL COPIES (ELECTRONIC OR OTHERWISE)
> IMMEDIATELY.
> 
> CE COURRIEL EST DESTINE UNIQUEMENT A LA PERSONNE OU A L'ENTITE A LAQUELLE IL
> EST ENVOYE ET PEUT CONTENIR DE L'INFORMATION CONFIDENTIELLE OU PRIVILEGIEE.
> TOUTE UTILISATION DE L'INFORMATION PAR UNE PERSONNE OU UNE ENTITE AUTRE QUE
> CELLE A LAQUELLE ELLE EST DESTINEE EST INTERDITE. SI VOUS RECEVEZ CE COURRIEL
> PAR ERREUR,  VEUILLEZ COMMUNIQUER AVEC SON EXPEDITEUR ET  SUPPRIMER CE
> COURRIEL ET TOUTE COPIE (ELECTRONIQUE OU AUTRE) IMMEDIATEMENT.
> _______________________________________________
> SunHELP maillist  -  SunHELP at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/sunhelp