gmirror does not initialize properally

[Holger Kipp]

On Mon, Mar 02, 2009 at 07:18:07PM -0500, Aryeh M. Friedman wrote:
> Andrew Snow wrote:
> >
> >Sorry, I meant "label -h" instead of just plain "label"... was getting 
> >confused with gstripe.
> >
> No matter what I attempt to do with the source drive (ad8) I get 
> oprtation not permitted... it lets me install the slave drive (ad14) 
> just fine:
> 
> 
> 
> flosoft# gmirror label -h -vb round-robin gm0 /dev/ad14
> Metadata value stored on ad14.
> Done.
> flosoft# gmirror status
>      Name    Status  Components
> mirror/gm0  COMPLETE  ad14
> flosoft# gmirror insert gm0 /dev/ad8
> gmirror: Cannot access provider ad8.
> flosoft# gmirror insert gm0 /dev/ad8s2
> gmirror: Provider ad8s2 too small.
> flosoft# gmirror insert gm0 /dev/ad8s2a
> gmirror: Provider ad8s2a too small.
> flosoft# gmirror label -vb round-robin gm0 /dev/da0
> gmirror: Can't get informations about /dev/da0: No such file or directory.
> flosoft# gmirror label -vb round-robin gm0 /dev/ad8
> gmirror: Can't store metadata on /dev/ad8: Operation not permitted.

was ad8 part of gmirror once? in that case you might want to try
gmirror forget 
such that gmirror will forget about not connected components first.
Only then storing new metadata on /dev/ad8 might be permitted again.
I experienced such a problem once when I played with gmirror setup
during new server installation...

Best regards,
Holger