linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Evans <mjevans1983@gmail.com>
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: "Majed B." <majedb@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: RAID5 / 6 Growth
Date: Wed, 16 Dec 2009 00:12:05 -0800	[thread overview]
Message-ID: <4877c76c0912160012t3796247dg4dcf79c66e404528@mail.gmail.com> (raw)
In-Reply-To: <8D.4A.01567.8F4982B4@cdptpa-omtalb.mail.rr.com>

On Wed, Dec 16, 2009 at 12:06 AM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
>> Have you made sure that the value of
>> /proc/sys/dev/raid/speed_limit_min is high enough? (200000 means 200
>
> High enough?  Wouldn't a higher speed limit mean more stress on the systems?
> Its value is 1000.
>
>> MB/s) along with /proc/sys/dev/raid/speed_limit_max?
>
> It's 200,000
>
>> I interrupted an array resyncing a couple of times without issues.
>> Only one time I interrupted an array during growth process and I had
>> an old version of mdadm (2.6.3) which didn't support resuming that. I
>> think Neil told me that 2.6.9 is the minimum requirement to resume.
>
> It's 2.6.7.2.  Debian does not admit new software into its distro until they
> are rock hard stable, unless it is a bug fix release.  I guess I'll have to
> wait a few more days.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

You could seek out a testing version or compile it your self.  mdadm
doesn't depend on that much...
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-12-16  8:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16  5:40 RAID5 / 6 Growth Leslie Rhorer
2009-12-16  6:37 ` Majed B.
2009-12-16  8:06   ` Leslie Rhorer
2009-12-16  8:12     ` Michael Evans [this message]
2009-12-16  8:38       ` Leslie Rhorer
2009-12-16 11:21     ` Majed B.
2009-12-17  1:36       ` Leslie Rhorer
2009-12-19  1:13       ` Leslie Rhorer
2009-12-19 18:21         ` Leslie Rhorer
2009-12-19 18:36           ` Majed B.
2009-12-19 19:02             ` Leslie Rhorer
2009-12-19 19:55               ` Majed B.
2009-12-19 20:19                 ` Leslie Rhorer
2009-12-19 23:39                   ` John Robinson
2009-12-19 23:49                     ` Leslie Rhorer
2009-12-19 23:59                     ` Majed B.
2009-12-16 13:25     ` Goswin von Brederlow
2009-12-17  1:51       ` Leslie Rhorer
2009-12-17  9:27         ` John Robinson
2009-12-18  1:33           ` Leslie Rhorer
2009-12-19  1:11           ` Leslie Rhorer
2009-12-18 12:27         ` Goswin von Brederlow
2009-12-17 17:53     ` Bill Davidsen
2009-12-18  1:46       ` Leslie Rhorer
2009-12-19  1:12       ` Leslie Rhorer
     [not found] <70ed7c3e0912191232k7deb3a3p40ddd6bc1bdfd3ae@mail.gmail.com>
2009-12-19 21:05 ` Leslie Rhorer
2009-12-21 12:33   ` Goswin von Brederlow

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=4877c76c0912160012t3796247dg4dcf79c66e404528@mail.gmail.com \
    --to=mjevans1983@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    --cc=majedb@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).