From: Nigel Croxon <ncroxon@redhat.com>
To: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
Cc: Jes Sorensen <jes@trained-monkey.org>,
linux-raid@vger.kernel.org, xni@redhat.com
Subject: Re: [PATCH] mdadm: fix reshape from RAID5 to RAID6 with backup file
Date: Tue, 16 Mar 2021 11:51:25 -0400 [thread overview]
Message-ID: <3CE6CB00-853C-4CB3-89CD-308D9DAE9CAC@redhat.com> (raw)
In-Reply-To: <eb0060d3-756d-c6f9-66d7-bcd7b0468bf7@linux.intel.com>
I’m trying your situation without my patch (its reverted) and I’m not seeing success.
[root@fedora33 mdadmupstream]# mdadm -CR volume -l0 --chunk 64 --raid-devices=1 /dev/nvme0n1 --force
mdadm: /dev/nvme0n1 appears to be part of a raid array:
level=container devices=0 ctime=Wed Dec 31 19:00:00 1969
mdadm: Creating array inside imsm container md127
mdadm: array /dev/md/volume started.
[root@fedora33 mdadmupstream]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid0]
md126 : active raid0 nvme0n1[0]
500102144 blocks super external:/md127/0 64k chunks
md127 : inactive nvme3n1[3](S) nvme2n1[2](S) nvme1n1[1](S) nvme0n1[0](S)
4420 blocks super external:imsm
unused devices: <none>
[root@fedora33 mdadmupstream]# mdadm -G /dev/md/imsm0 -n2
[root@fedora33 mdadmupstream]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid0]
md126 : active raid4 nvme3n1[2] nvme0n1[0]
500102144 blocks super external:-md127/0 level 4, 64k chunk, algorithm 5 [2/1] [U_]
md127 : inactive nvme3n1[3](S) nvme2n1[2](S) nvme1n1[1](S) nvme0n1[0](S)
4420 blocks super external:imsm
unused devices: <none>
dmesg says:
[Mar16 11:46] md/raid:md126: device nvme0n1 operational as raid disk 0
[ +0.011147] md/raid:md126: raid level 4 active with 1 out of 2 devices, algorithm 5
[ +0.044605] md/raid0:md126: raid5 must have missing parity disk!
[ +0.000002] md: md126: raid0 would not accept array
> On Mar 16, 2021, at 10:54 AM, Tkaczyk, Mariusz <mariusz.tkaczyk@linux.intel.com> wrote:
>
> Hello Nigel,
>
> Blame told us, that yours patch introduce regression in following
> scenario:
>
> #mdadm -CR imsm0 -e imsm -n4 /dev/nvme[0125]n1
> #mdadm -CR volume -l0 --chunk 64 --raid-devices=1 /dev/nvme0n1 --force
> #mdadm -G /dev/md/imsm0 -n2
>
> At the end of reshape, level doesn't back to RAID0.
> Could you look into it?
> Let me know, if you need support.
>
> Thanks,
> Mariusz
>
next prev parent reply other threads:[~2021-03-16 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 20:05 [PATCH] mdadm: fix reshape from RAID5 to RAID6 with backup file Nigel Croxon
2021-02-16 14:28 ` Nigel Croxon
2021-02-26 22:06 ` Jes Sorensen
2021-03-16 14:54 ` Tkaczyk, Mariusz
2021-03-16 15:21 ` Nigel Croxon
2021-03-16 15:51 ` Nigel Croxon [this message]
2021-03-16 15:59 ` Nigel Croxon
2021-03-17 8:34 ` Tkaczyk, Mariusz
[not found] <764426808.38181143.1615910368475.JavaMail.zimbra () redhat ! com>
2021-03-22 16:21 ` Oleksandr Shchirskyi
2021-03-22 16:47 ` Nigel Croxon
2021-03-22 17:16 ` Nigel Croxon
2021-03-22 17:41 ` Oleksandr Shchirskyi
2021-03-23 16:36 ` Nigel Croxon
2021-03-23 20:58 ` Oleksandr Shchirskyi
2021-03-26 11:59 ` Nigel Croxon
2021-04-01 20:49 ` Jes Sorensen
2021-04-02 9:40 ` Oleksandr Shchirskyi
2021-04-06 18:31 ` Jes Sorensen
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=3CE6CB00-853C-4CB3-89CD-308D9DAE9CAC@redhat.com \
--to=ncroxon@redhat.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=xni@redhat.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).