Am 28.06.2012 17:56, schrieb Stefan G. Weichinger:
> md0 : active raid6 sdb3[4](S) sda3[5] sdc3[2] sdd3[3]
> 3903891200 blocks level 6, 64k chunk, algorithm 2 [4/2] [__UU]
> [================>....] recovery = 83.0%
> (1621636224/1951945600) finish=81.5min speed=67477K/sec
>
> I assume it is OK in this state of things that sdb3 is marked as
> (S)pare ...
It seems so, as now it has entered the next stage:
md0 : active raid6 sdb3[4] sda3[0] sdc3[2] sdd3[3]
3903891200 blocks level 6, 64k chunk, algorithm 2 [4/3] [U_UU]
[=>...................] recovery = 6.2% (122751744/1951945600)
finish=784.6min speed=38854K/sec
Somewhat slower, but no (S)pare there anymore.
What is the logic behind that?
What does it do exactly when it re-adds the first disk, what in the
second round?
Should I have added sd[ab]3 in one command?
To me it also seems that I now have good redundancy again already, correct?
Sorry for all my questions ;-)
I just like to understand things, at least on my user-level.
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
