From: Michael Evans <mjevans1983@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: grow fails with 2.6.34 git
Date: Wed, 14 Apr 2010 19:22:48 -0700 [thread overview]
Message-ID: <r2x4877c76c1004141922y7f8ef8d6h3ae35ce261a45735@mail.gmail.com> (raw)
In-Reply-To: <20100415110401.22c7a6bf@notabene.brown>
On Wed, Apr 14, 2010 at 6:04 PM, Neil Brown <neilb@suse.de> wrote:
> What is happening here is that the spare (sdh) is getting the Q blocks
> written to it. When this completes you will have full 2-disk redundancy but
> the layout will not be optimal and the array wont be any bigger.
> To fix this you would:
>
> mdadm --grow --backup-file=/root/backup.md4 --raid-devices=6 \
> --layout=normalise /dev/md4
>
Is there some way of telling if the layout is proper, or is that what
'level 6' indicates?
Also is it safe to run something like...
mdadm --grow --back-file=/some/never/used/file --layout=normalize /dev/mdX
on any raid 5/6 device that isn't undergoing an active reshape? (would
it be a null-op if not required)
--
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
next prev parent reply other threads:[~2010-04-15 2:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 22:10 grow fails with 2.6.34 git James Braid
2010-04-14 22:48 ` Michael Evans
2010-04-14 23:27 ` James Braid
2010-04-14 23:38 ` Michael Evans
2010-04-15 1:04 ` Neil Brown
2010-04-15 2:22 ` Michael Evans [this message]
2010-04-15 2:55 ` Neil Brown
2010-04-15 15:09 ` James Braid
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=r2x4877c76c1004141922y7f8ef8d6h3ae35ce261a45735@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).