> i think it's a bug but only happens with such massive mirror. very few
>people do more than 2-way mirrors that's probably it wasn't catched.
>
>please do report the bug - it's critical.
In fact I just confirmed that if we reduce our mirror to just two members the
problem does not occur. The
> By "kicked out" you mean "overwritten"?
>
>You should definitely look at "gmirror list" before and after.
Sorry for the confusion. By "kicked out", what I meant was as gmirror started
up it took ad4 as the principal member, saw that it was previously part of a
mirror with three other drives
2009/4/24 Peter Steele :
>> This definitely looks like a bug. Try asking again on the freebsd-geom@
>> list. Provide output of "gmirror list".
>
> I'll try that list...
>
>>So, your steps were:
>
>>1. ad4, ad6, ad8 and ad10 in a 4-way mirror
>>2. ad4 fails. At this point did you do a "gmirror list"
i think it's a bug but only happens with such massive mirror. very few
people do more than 2-way mirrors that's probably it wasn't catched.
please do report the bug - it's critical.
On Fri, 24 Apr 2009, Peter Steele wrote:
This only happens with ad4. If ad6 for example goes offline in the sam
> This only happens with ad4. If ad6 for example goes offline in the same way,
> when it is reinserted
> it does not become the dominant drive and resync its data with the other
> drives. Rather its data
> is overwritten with the data from the 3 member mirror, as you'd expect.
> looks like ver
> This definitely looks like a bug. Try asking again on the freebsd-geom@
> list. Provide output of "gmirror list".
I'll try that list...
>So, your steps were:
>1. ad4, ad6, ad8 and ad10 in a 4-way mirror
>2. ad4 fails. At this point did you do a "gmirror list"? I.e. did
>gmirror detect it
This only happens with ad4. If ad6 for example goes offline in the same way,
when it is reinserted it does not become the dominant drive and resync its data
with the other drives. Rather its data is overwritten with the data from the 3
member mirror, as you'd expect.
looks like very strange bug
Ivan Voras wrote:
> Peter Steele wrote:
>> We had a somewhat startling scenario occur with gmirror. We have systems
>> with four drives ad4, ad6, ad8, and ad10, with the OS setup on a mirrored
>> slice across all four drives. The ad4 drive failed at one point, due to a
>> simple bad connection i
Peter Steele wrote:
> We had a somewhat startling scenario occur with gmirror. We have systems with
> four drives ad4, ad6, ad8, and ad10, with the OS setup on a mirrored slice
> across all four drives. The ad4 drive failed at one point, due to a simple
> bad connection in its drive bay. While i
