From: Phil Turmel <philip@turmel.org>
To: David Waite <david@alkaline-solutions.com>, linux-raid@vger.kernel.org
Subject: Re: Unable to (un)-grow raid6
Date: Sun, 6 Dec 2015 15:35:16 -0500 [thread overview]
Message-ID: <56649C04.9000601@turmel.org> (raw)
In-Reply-To: <465BF0F5-B5C7-4C02-8EB5-552B959B8D29@alkaline-solutions.com>
On 12/05/2015 10:04 PM, David Waite wrote:
> I’m having difficulty shrinking down a RAID6 array (md2) on a Sinology NAS. I wish to go from 13 drives to 11, and believe I need to go to 12 first to maintain operation and redundancy through the resizing process.
No, you can go straight to 11 if you've set array-size properly. --grow
operations maintain redundancy throughout.
> The -array-size has already been shrunk to account for the two drives I wish to remove, and one of the devices has been removed and the machine restarted before the command output below was generated.
You might need to set array-size again. It is a temporary setting that
only becomes permanent when --grow successfully starts.
> # cat /proc/mdstat
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
> md2 : active raid6 sda3[0] sdia3[14] sdib3[9] sdic3[10] sdid3[11] sdie3[12] sdg3[17] sdf3[5] sde3[16] sdd3[3] sdc3[13] sdb3[15]
> 26329895935 blocks super 1.2 level 6, 64k chunk, algorithm 2 [13/12] [UUUUUUU_UUUUU]
>
> md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] sdf2[5] sdg2[6]
> 2097088 blocks [8/7] [UUUUUUU_]
>
> md0 : active raid1 sda1[0] sdb1[1] sdc1[2] sdd1[3] sde1[4] sdf1[5] sdg1[6]
> 2490176 blocks [8/7] [UUUUUUU_]
>
> unused devices: <none>
> When running
> # mdadm --grow -n 12 /dev/md2 --backup-file=/mnt/backup-file3
> mdadm: max_devs [384] of [/dev/md2]
> mdadm: Need to backup 7040K of critical section..
> mdadm: Cannot set device shape for /dev/md2: Invalid argument
>
> ---
>
> dmesg just reports:
> [87908.606245] md: couldn't update array info. -22
Error code 22 is "Invalid Argument", corresponding to the mdadm output.
Try setting array size again, then try again. Feel free to go straight
to 11 devices -- it'll save you much time.
Also, for completeness, show --detail and --examine for the array and it
members.
Phil
--
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:[~2015-12-06 20:35 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 [this message]
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
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=56649C04.9000601@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 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).