From: Phil Turmel <philip@turmel.org>
To: David Waite <david@alkaline-solutions.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Unable to (un)-grow raid6
Date: Tue, 8 Dec 2015 22:12:30 -0500 [thread overview]
Message-ID: <56679C1E.1040908@turmel.org> (raw)
In-Reply-To: <10980501-F73B-4A63-AF7D-D7100C9C6B72@alkaline-solutions.com>
On 12/08/2015 06:42 PM, David Waite wrote:
> Thanks for your help - it is now reshaping the array with sdia3 and
> sdib3 as hot spares.
>
> It appears the version of mdadm on the NAS (3.1.4) is pretty old, and
> does not have a replace command - just marking disks as faulty. I
> will build and load in a newer version of mdadm. I assume there is no
> issue in doing this while a reshaping is going on?
No issue. You don't even have to install it. However, like most
features, there's a kernel part and a userspace part. If the new mdadm
that supports --replace can't talk to the matching kernel part, it won't
work.
Either way, you can't actually do the --replace until the reshape finishes.
{Convention on kernel.org lists is to reply-to-all, trim replies, and
bottom post. Please do.}
Phil
prev parent reply other threads:[~2015-12-09 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E26C335-DEDB-489E-B54E-A285273569A1@alkaline-solutions.com>
2015-12-06 3:04 ` Unable to (un)-grow raid6 David Waite
2015-12-06 20:35 ` Phil Turmel
2015-12-06 21:13 ` David Waite
2015-12-06 21:21 ` Phil Turmel
[not found] ` <BACF203A-3817-4F24-88B0-38713D9459D9@alkaline-solutions.com>
[not found] ` <5664D042.9080401@turmel.org>
[not found] ` <10980501-F73B-4A63-AF7D-D7100C9C6B72@alkaline-solutions.com>
2015-12-09 3:12 ` Phil Turmel [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=56679C1E.1040908@turmel.org \
--to=philip@turmel.org \
--cc=david@alkaline-solutions.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.