From: Coly Li <colyli@suse.de>
To: linux-raid@vger.kernel.org
Subject: [BUG REPORT] md raid5 with write log does not start
Date: Fri, 17 Apr 2020 00:30:25 +0800 [thread overview]
Message-ID: <4ad57f1f-a00f-3bc6-33d2-f30ca8e18c0d@suse.de> (raw)
Hi folks,
When I try to create md raid5 array with 4 NVMe SSD (3 for raid array
component disks, 1 for write log), the kernel is Linux v5.6 (not Linux
v5.7-rc), I find the md raid5 array cannot start.
I use this command to create md raid5 with writelog,
mdadm -C /dev/md0 -l 5 -n 3 /dev/nvme{0,1,2}n1 --write-journal /dev/nvme3n1
From terminal I have the following 2 lines information,
mdadm: Defaulting to version 1.2 metadata
mdadm: RUN_ARRAY failed: Invalid argument
From kernel message, I have the following dmesg lines,
[13624.897066] md/raid:md0: array cannot have both journal and bitmap
[13624.897068] md: pers->run() failed ...
[13624.897105] md: md0 stopped.
But from /proc/mdstat, it seems an inactive array is still created,
/proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : inactive nvme2n1[4](S) nvme0n1[0](S) nvme3n1[3](S)
11251818504 blocks super 1.2
unused devices: <none>
From all the information it seems when initialize raid5 cache the bitmap
information is not cleared, so an error message shows up and raid5_run()
fails.
I don't have clear idea who to handle bitmap, journal and ppl properly,
so I firstly report the problem here.
So far I am not sure whether this is a bug or I do something wrong. Hope
other people may reproduce the above failure too.
Thanks.
Coly Li
next reply other threads:[~2020-04-16 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 16:30 Coly Li [this message]
2020-04-17 10:28 ` [BUG REPORT] md raid5 with write log does not start Artur Paszkiewicz
2020-04-20 2:47 ` Xiao Ni
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=4ad57f1f-a00f-3bc6-33d2-f30ca8e18c0d@suse.de \
--to=colyli@suse.de \
--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).