From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: "Jeffrey W. Baker" <jwbaker@acm.org>
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: very slow RAID-1 resync
Date: Tue, 16 Oct 2001 07:07:41 +0200 (MET DST) [thread overview]
Message-ID: <200110160507.f9G57f509413@oboe.it.uc3m.es> (raw)
In-Reply-To: <Pine.LNX.4.33.0110151653120.13462-100000@windmill.gghcwest.com> from "Jeffrey W. Baker" at "Oct 15, 2001 05:02:21 pm"
"A month of sundays ago Jeffrey W. Baker wrote:"
> I just plugged in a new RAID-1(+0, 2 2-disk stripe sets mirrored) to a
> 2.4.12-ac3 machine. The md code decided it was going to resync the mirror
> at between 100KB/sec and 100000KB/sec. The actual rate was 100KB/sec,
> while the device was otherwise idle. By increasing
> /proc/.../speed_limit_min, I was able to crank the resync rate up to
> 20MB/sec, which is slightly more reasonable but still short of the
> ~60MB/sec this RAID is capable of.
>
> So, two things: there is something wrong with the resync code that makes
> it run at the minimum rate even when the device is idle, and why is the
> resync proceeding so slowly?
This has been the trend throughout the 2.4 series. 2.4.0 was quite
snappish at resyncs and speed has generally dropped from version to
version. I recall seeing a speed halving somewhere early in the series
(2.4.2?).
> raid1d and raid1syncd are barely getting any CPU time on this otherwise
> idle SMP system.
>
> There must be some optimization to mostly skip the sync on an array of new
> drives, ja?
Not that I have seen. Raid resyncs are throttled via a braking mechanism
in the generic md code (I think it's called fooresyncbar). It attempts
to guage the current resync speed and compares with the min and max values
and either calls for more resyncs or schedules. But even removing this
brake from the code doesnt't spped things up, so I am mystified as to
where the throttling effect comes from. It must be somewhere else in
the structire of the code.
Another problem is that there seem sto be some kind of state .. if the
raid resync starts while the machine is under load, then it runs slowly
and continues at that rate even when the other load is removed.
Peter
prev parent reply other threads:[~2001-10-16 5:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 0:02 Jeffrey W. Baker
2001-10-16 1:58 ` Mark Hahn
2001-10-16 3:44 ` Neil Brown
2001-10-16 3:53 ` Jeffrey W. Baker
2001-10-16 11:40 ` Neil Brown
2001-10-19 4:21 ` Neil Brown
2001-10-16 3:43 ` Neil Brown
2001-10-16 3:52 ` Jeffrey W. Baker
2001-10-16 4:14 ` Neil Brown
2001-10-16 5:07 ` Peter T. Breuer [this message]
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=200110160507.f9G57f509413@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=jwbaker@acm.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®