Mike Hardy wrote:
> Finally, and I think was reported once before, but I don't recall a > resolution for it, I got this once I specified that it grow to maximum size: > > [EMAIL PROTECTED] mdadm-2.1]# cat /proc/mdstat > Personalities : [raid1] > md2 : active raid1 sdb1[0] sda1[1] > 98176 blocks [2/2] [UU] > > md1 : active raid1 sdb3[0] sda3[1] > 70573440 blocks [2/2] [UU] > [=========>...........] resync = 49.9% (35220224/70573440) > finish=0.2min speed=2515730K/sec > > md0 : active raid1 sdb2[0] sda2[1] > 977856 blocks [2/2] [UU] > > unused devices: <none> > > This is a dual Xeon (so it looks like a 4-CPU machine). Not sure what's > causing that though... Sorry to reply to myself, but I just did the same thing on a different machine (with an older mdadm) and I also got an..."optimistic" resync speed reading on it after the grow, when it 'resumed from checkpoint'. Oddly, these machines reported normal speeds during the resyncs that occurred when I rotated larger drives into the machines. Perhaps it has something to do with resumption from checkpoints? Anyway, I hope all the reports help. -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
