gmirror start bug?

[Dmitry Morozovsky]

Dear Pawel,

it seems thet gmirror is entering the endless loop if one inserted disk with 
previously configured mirror part in syncronyzing state:

root at moose:/media/sata# gmirror list m0g
Geom name: m0g
State: STARTING
Components: 2
Balance: split
Slice: 4096
Flags: NONE
GenID: 0
SyncID: 0
ID: 2992987948
Consumers:
1. Name: ad22g
   Mediasize: 272441875968 (254G)
   Sectorsize: 512
   Mode: r1w1e1
   State: NEW
   Priority: 0
   Flags: SYNCHRONIZING
   GenID: 0
   SyncID: 2
   ID: 3619189671

root at moose:/media/sata# gmirror stop m0g ; gmirror clear ad22g
Can't clear metadata on ad22g: Operation not permitted.
gmirror: Not fully done.

from kernel log:

Mar 10 21:04:31 <kern.crit> moose kernel: GEOM_MIRROR: Force device m0g start 
due to timeout.
Mar 10 21:04:31 <kern.crit> moose kernel: GEOM_MIRROR: Device m0g destroyed.
Mar 10 21:04:35 <kern.crit> moose kernel: GEOM_MIRROR: Force device m0g start 
due to timeout.
Mar 10 21:04:35 <kern.crit> moose kernel: GEOM_MIRROR: Device m0g destroyed.
Mar 10 21:04:39 <kern.crit> moose kernel: GEOM_MIRROR: Force device m0g start 
due to timeout.
Mar 10 21:04:39 <kern.crit> moose kernel: GEOM_MIRROR: Device m0g destroyed.

...

In my case, a workaround was: detach broken disk, configure mirror with the 
same name (I did it over md), then gmirror clear ad22g -- but I suppose this 
situation should be somehow detected and loop broken.

Thanks!



-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck at FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
------------------------------------------------------------------------