From: Phil Turmel <philip@turmel.org>
To: Alexander Shenkin <al@shenkin.org>,
Wols Lists <antlists@youngman.org.uk>,
Roger Heflin <rogerheflin@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Raid-6 cannot reshape
Date: Tue, 7 Apr 2020 08:31:37 -0400 [thread overview]
Message-ID: <44069d88-f838-2b8b-1002-a1fff5502d2d@turmel.org> (raw)
In-Reply-To: <38852671-9c5a-3807-0284-41f902e5f81b@turmel.org>
On 4/7/20 8:28 AM, Phil Turmel wrote:
>>
>> Thanks Phil,
>>
>> The --invalid-backup parameter was necessary to get this up and running.
>> It's now up with the 7th disk as a spare. Shall I run fsck now, or can
>> I just try to grow again?
>>
>> proposed grow operation:
>>> mdadm --grow -raid-devices=7 --backup-file=/dev/usb/grow_md127.bak
>> /dev/md127
>>> mdadm --stop /dev/md127
>>> umount /dev/md127 # not sure if this is necessary
>>> resize2fs /dev/md127
>
> An fsck could help, if any blocks did get moved.
>
> I would not attempt a grow again until you find out why the previous
> attempt didn't make progress. Check if mdmon is running, and/or compile
> a fresh copy of mdadm from source. If you don't figure it out, you'll
> just end up in the same spot again.
Oh, one more point: Don't use a backup file. Let mdadm shift the data
offsets to get the temporary space needed. (It'll run faster, too.)
(I don't see any mdadm --examine reports in the list thread. Did you do
them and keep the complete output?)
Phil
next prev parent reply other threads:[~2020-04-07 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 10:16 Raid-6 cannot reshape Alexander Shenkin
[not found] ` <6b9b6d37-6325-6515-f693-0ff3b641a67a@shenkin.org>
2020-04-06 15:27 ` Alexander Shenkin
2020-04-06 16:12 ` Roger Heflin
2020-04-06 16:27 ` Wols Lists
2020-04-06 20:34 ` Phil Turmel
2020-04-07 10:25 ` Alexander Shenkin
2020-04-07 11:28 ` Phil Turmel
2020-04-07 11:46 ` Alexander Shenkin
2020-04-07 12:28 ` Phil Turmel
2020-04-07 12:31 ` Phil Turmel [this message]
2020-04-07 13:19 ` Alexander Shenkin
2020-04-07 15:08 ` antlists
2020-04-07 17:04 ` Alexander Shenkin
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=44069d88-f838-2b8b-1002-a1fff5502d2d@turmel.org \
--to=philip@turmel.org \
--cc=al@shenkin.org \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rogerheflin@gmail.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 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.