linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: David F <raid@meta-dynamic.com>, linux-raid@vger.kernel.org
Subject: Re: "mdadm -n": component device selection when delta_disks<0
Date: Thu, 7 May 2020 21:36:38 +0100	[thread overview]
Message-ID: <5EB47156.9050902@youngman.org.uk> (raw)
In-Reply-To: <20200507193636.5B4FE53E95@mail.meta-dynamic.com>

On 07/05/20 20:36, David F wrote:
> I'm planning to use use three mdadm commands to accomplish the
> reshape, as follows:
> 
> mdadm --grow --size=6000G --assume-clean /dev/md0
> mdadm --grow --array-size=12000G /dev/md0
> mdadm --grow --raid-devices=3 --backup-file=/root/md-backup /dev/md0
> 
> 
> Ideally, I'd prefer a single command,
> mdadm --grow --size=6000G --raid-devices=3 /dev/md0
> ... but that seems not possible [1].
> 
> 
> In either case, my question still applies: when reshaping to
> reduce the number of devices in the array (--raid-devices), is
> there any way to specify exactly which device(s) are to be
> removed from active sync (I suppose they become spares) and which
> ones kept? 

You should be able to stick --remove /dev/sdX on the command line ...

BUT. Before you start, what version of mdadm are you running? The
latest? What version of linux? An old LTS with a heavily patched
frankenkernel? You really want to be running both a recent kernel and
recent mdadm.

The other point, if you don't need --backup, DON'T USE IT. It doesn't do
any real harm provided you use it right, but it shouldn't be necessary
and it causes needless confusion and trouble.

Cheers,
Wol

      reply	other threads:[~2020-05-07 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 19:36 "mdadm -n": component device selection when delta_disks<0 David F
2020-05-07 20:36 ` Wols Lists [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=5EB47156.9050902@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=raid@meta-dynamic.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).