From: Andrew Burgess <aab@cichlid.com>
To: linux raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: grow raid 6: different errors with mdadm 3.0.3 and 3.1
Date: Thu, 26 Nov 2009 07:02:03 -0800 [thread overview]
Message-ID: <1259247723.23899.0@athlon> (raw)
In-Reply-To: <20091126142227.496da980@notabene.brown> (from neilb@suse.de on Wed Nov 25 19:22:27 2009)
On 11/25/2009 07:22:27 PM, Neil Brown wrote:
> On Tue, 24 Nov 2009 10:21:39 -0800 Andrew Burgess <aab@cichlid.com>
> wrote:
> > mdadm 3.1:
> >
> > sudo ./mdadm -G /dev/md1 --raid-devices=15
> > mdadm: this change will reduce the size of the array.
> > use --grow --array-size first to truncate array.
> > e.g. mdadm --grow /dev/md1 --array-size 928142080
> Thanks for the report.
Thanks for the fix. I grabbed the git head version and the
resize is grinding away now.
next prev parent reply other threads:[~2009-11-26 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 18:21 grow raid 6: different errors with mdadm 3.0.3 and 3.1 Andrew Burgess
2009-11-26 3:22 ` Neil Brown
2009-11-26 15:02 ` Andrew Burgess [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-24 18:46 Andrew Burgess
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=1259247723.23899.0@athlon \
--to=aab@cichlid.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 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).