On Tuesday August 8, [email protected] wrote:
> Michael Tokarev <[email protected]> writes:
>
> > Why we're updating it BACKWARD in the first place?
>
> Another scenario: 1 disk (of 2) is removed, another is added, RAID-1
> is rebuilt, then the disk added last is removed and replaced by
> the disk which was removed first. Would it trigger this problem?
>
No. The removing and the adding will all move the event count clearly
forward and the removed drive will have an old event count and so will
not be considered for easy inclusion.
> > Also, why, when we adding something to the array, the event counter is
> > checked -- should it resync regardless?
>
> I think it's a full start, not a hot add. For hot add contents of
> the new disk should be ignored.
See my other post for why I want to sometimes not do a recovery on a
hot-add.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
