From: Marc MERLIN <marc@merlins.org>
To: linux-raid@vger.kernel.org
Subject: Is it correct that raid5 cannot be converted from Consistency Policy: bitmap to ppl?
Date: Sun, 3 Jul 2022 13:07:41 -0700 [thread overview]
Message-ID: <20220703200741.GA3138296@merlins.org> (raw)
Is there any way around this, or not without a full reformat/rebuild?
gargamel:~# mdadm --query --detail /dev/md5
/dev/md5:
Version : 1.2
Creation Time : Tue Jan 21 10:35:52 2014
Raid Level : raid5
Array Size : 15627542528 (14903.59 GiB 16002.60 GB)
Used Dev Size : 3906885632 (3725.90 GiB 4000.65 GB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sun Jul 3 03:02:01 2022
State : active, checking
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Check Status : 99% complete
Name : gargamel.svh.merlins.org:5 (local to host gargamel.svh.merlins.org)
UUID : ec672af7:a66d9557:2f00d76c:38c9f705
Events : 642977
Number Major Minor RaidDevice State
0 8 193 0 active sync /dev/sdm1
6 8 177 1 active sync /dev/sdl1
2 8 209 2 active sync /dev/sdn1
3 8 1 3 active sync /dev/sda1
5 8 17 4 active sync /dev/sdb1
gargamel:~# mdadm --grow --consistency-policy=ppl /dev/md5
mdadm: Current consistency policy is bitmap, cannot change to ppl
Kernel 5.16.
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
next reply other threads:[~2022-07-03 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 20:07 Marc MERLIN [this message]
2022-07-03 21:20 ` Is it correct that raid5 cannot be converted from Consistency Policy: bitmap to ppl? Wols Lists
2022-07-04 8:43 ` Lukasz Florczak
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=20220703200741.GA3138296@merlins.org \
--to=marc@merlins.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).