From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: very slow RAID-1 resync
Date: Mon, 15 Oct 2001 20:52:41 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0110152050120.415-100000@desktop> (raw)
In-Reply-To: <15307.44268.700557.852375@notabene.cse.unsw.edu.au>
On Tue, 16 Oct 2001, Neil Brown wrote:
> On Monday October 15, jwbaker@acm.org 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?
>
> The way that it works out where there is other activity on the drives
There wasn't any activity at all.
> is a bit fragile. It works particularly badly when the underlying
> devices are md devices.
Bummer.
> I would recommend that instead of mirroring 2 stipe sets, you stripe
> two mirrored pairs. The resync should be faster and the resilience to
> failure is much better.
I did eventually do it that way, but the sync speed was the same. I'm
very curious to know why you think striping mirrors is more reliable than
mirroring stripes. Either way, you can lose any one drive and some
combinations of two drives. Either way you can hot-swap the bad disk.
-jwb
next prev parent reply other threads:[~2001-10-16 3:51 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 [this message]
2001-10-16 4:14 ` Neil Brown
2001-10-16 5:07 ` Peter T. Breuer
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=Pine.LNX.4.33.0110152050120.415-100000@desktop \
--to=jwbaker@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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®