From: Roman Mamedov <rm@romanrm.net>
To: Eli Ben-Shoshan <eli@benshoshan.com>
Cc: linux-raid@vger.kernel.org, John Stoffel <john@stoffel.org>
Subject: Re: Accidentally resized array to 9
Date: Fri, 29 Sep 2017 17:55:24 +0500 [thread overview]
Message-ID: <20170929175524.57fea3b5@natsu> (raw)
In-Reply-To: <0e59cefd-662f-bf77-0c32-49424d504c77@benshoshan.com>
On Fri, 29 Sep 2017 00:23:28 -0400
Eli Ben-Shoshan <eli@benshoshan.com> wrote:
> This was a RAID6 with 8 devices. Instead of using --grow with
> --raid-devices set to 9, I did the following:
>
> mdadm --grow /dev/md128 --size 9
>
> This happily returned without any errors so I went to go look at
> /proc/mdstat and did not see a resize operation going. So I shook my
> head and read the output of --grow --help and did the right thing which is:
>
> mdadm --grow /dev/md128 --raid-devices=9
The output of the first command is:
# mdadm --grow /dev/md0 --size 9
mdadm: component size of /dev/md0 has been set to 9K
unfreeze
It didn't occur to you that you FIRST need to restore the "component size" back
to what it was previously?...
And yes as John says there should be a confirmation request on reducing the
array size. In fact I couldn't believe there isn't one already, that's why I
went checking. But nope, there are no warnings or confirmation requests
neither for reducing --size, nor --array-size. I might be remembering that
there were some, from LVM, not MD.
--
With respect,
Roman
next prev parent reply other threads:[~2017-09-29 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 4:23 Accidentally resized array to 9 Eli Ben-Shoshan
2017-09-29 12:38 ` John Stoffel
2017-09-29 14:47 ` Eli Ben-Shoshan
2017-09-29 19:33 ` John Stoffel
2017-09-29 21:04 ` Eli Ben-Shoshan
2017-09-29 21:17 ` John Stoffel
2017-09-29 21:49 ` Eli Ben-Shoshan
2017-09-29 12:55 ` Roman Mamedov [this message]
2017-09-29 14:53 ` Eli Ben-Shoshan
2017-09-29 19:50 ` Roman Mamedov
2017-09-30 16:21 ` Phil Turmel
2017-09-30 16:29 ` Roman Mamedov
2017-09-30 23:30 ` John Stoffel
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=20170929175524.57fea3b5@natsu \
--to=rm@romanrm.net \
--cc=eli@benshoshan.com \
--cc=john@stoffel.org \
--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).