From: Mike Hardy <mhardy@h3c.com>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm source rpm build error + command-line parsing error + resync reporting problem
Date: Thu, 08 Dec 2005 21:16:16 -0800 [thread overview]
Message-ID: <43991320.5080509@h3c.com> (raw)
In-Reply-To: <4399121F.9060906@h3c.com>
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:
>
> [root@istanbul 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
next prev parent reply other threads:[~2005-12-09 5:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 5:11 mdadm source rpm build error + command-line parsing error + resync reporting problem Mike Hardy
2005-12-09 5:16 ` Mike Hardy [this message]
2005-12-09 5:33 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2005-12-09 5:43 Mike Hardy
2005-12-09 5:55 ` Neil Brown
2005-12-09 6:31 ` Mike Hardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43991320.5080509@h3c.com \
--to=mhardy@h3c.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.