On Thursday February 2, [EMAIL PROTECTED] wrote:
> On Thursday February 2, [EMAIL PROTECTED] wrote:
> >
> > In any case, I have included the relevant dmesgs and a --examine and
> > --detail for all drives as soon as the second (2.6.15.1) weird rebuild
> > started. If you need any more info I'll do my best to provide it, but I
> > thought I should at least report this.
>
>
> Thanks for all the details. I can see what is happening.
>
> sdj1 (the failed drive) is claiming the same slot in the array as sdo1
> (the spare drive that has been rebuilt), so sdo1 gets rejected.
> sdj1 should be rejected before that because of the old 'event' count,
> but the 'autorun' code isn't doing that check.
>
> I'll see what I can do about fixing this.
I should have added:
If you
mdadm --zero-superblock /dev/sdj1
the problem will go away.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
