Nigel J. Terry wrote:
> One comment - As I look at the rebuild, which is now over 20%, the time > till finish makes no sense. It did make sense when the first reshape > started. I guess your estimating / averaging algorithm doesn't work for > a restarted reshape. A minor cosmetic issue - see below > > Nigel > [EMAIL PROTECTED] ~]$ cat /proc/mdstat > Personalities : [raid5] [raid4] > md0 : active raid5 sdb1[1] sda1[0] hdc1[4](S) hdb1[2] > 490223104 blocks super 0.91 level 5, 128k chunk, algorithm 2 [4/3] > [UUU_] > [====>................] reshape = 22.7% (55742816/245111552) > finish=5.8min speed=542211K/sec Unless something has changed recently the parity-rebuild-interrupted / restarted-parity-rebuild case shows the same behavior. It's probably the same chunk of code (I haven't looked, bad hacker! bad!), but I thought I'd mention it in case Neil goes looking The "speed" is truly impressive though. I'll almost be sorry to see it fixed :-) -Mike - 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
