From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: How to enable bitmap on IMSM?
Date: Tue, 14 Jun 2022 16:45:31 +0200 [thread overview]
Message-ID: <20220614164531.0000654e@linux.intel.com> (raw)
In-Reply-To: <20220614141442.1971c876@nvm>
On Tue, 14 Jun 2022 14:14:42 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> Hello,
>
> I upgraded mdadm to 4.2 to get the bitmap support in IMSM.
>
> I run: "mdadm --update-subarray=0 -U bitmap /dev/md127"
> However the array details stay the same, with "Consistency Policy : resync".
> No error is reported, and nothing in dmesg.
>
> How to actually use it?
>
Hi Roman,
There is a bug in mdadm (will be fixed soon) which allows you to update
subarray on active volume. Update is successful but mdmon will overwrite
it.
To enable bitmap, you need to stop member array first:
# mdadm -S /dev/md126
then run update command:
# mdadm --update-subarray=0 -U bitmap /dev/md127
mdadm will set bitmap in metadata:
#mdadm -E /dev/md127
At the end, start member volume:
# mdadm -As
Now, you can verify array details:
# mdadm -D /dev/md126.
Hope it helps,
Mariusz
> Thanks
>
>
> # mdadm --detail /dev/md127
> /dev/md127:
> Version : imsm
> Raid Level : container
> Total Devices : 4
>
> Working Devices : 4
>
>
> UUID : d07837ca:804cf5e3:01c52352:f64b0524
> Member Arrays : /dev/md/Volume0
>
> Number Major Minor RaidDevice
>
> - 8 32 - /dev/sdc
> - 8 0 - /dev/sda
> - 8 48 - /dev/sdd
> - 8 16 - /dev/sdb
>
> # mdadm --detail /dev/md126
> /dev/md126:
> Container : /dev/md/imsm0, member 0
> Raid Level : raid10
> Array Size : 1953519616 (1863.02 GiB 2000.40 GB)
> Used Dev Size : 976759808 (931.51 GiB 1000.20 GB)
> Raid Devices : 4
> Total Devices : 4
>
> State : active
> Active Devices : 4
> Working Devices : 4
> Failed Devices : 0
>
> Layout : near=2
> Chunk Size : 64K
>
> Consistency Policy : resync
>
>
> UUID : xxx
> Number Major Minor RaidDevice State
> 3 8 0 0 active sync set-A /dev/sda
> 2 8 16 1 active sync set-B /dev/sdb
> 1 8 32 2 active sync set-A /dev/sdc
> 0 8 48 3 active sync set-B /dev/sdd
>
> # mdadm --update-subarray=0 -U bitmap /dev/md127
>
> # mdadm --detail /dev/md127
> /dev/md127:
> Version : imsm
> Raid Level : container
> Total Devices : 4
>
> Working Devices : 4
>
>
> UUID : d07837ca:804cf5e3:01c52352:f64b0524
> Member Arrays : /dev/md/Volume0
>
> Number Major Minor RaidDevice
>
> - 8 32 - /dev/sdc
> - 8 0 - /dev/sda
> - 8 48 - /dev/sdd
> - 8 16 - /dev/sdb
>
> # mdadm --detail /dev/md126
> /dev/md126:
> Container : /dev/md/imsm0, member 0
> Raid Level : raid10
> Array Size : 1953519616 (1863.02 GiB 2000.40 GB)
> Used Dev Size : 976759808 (931.51 GiB 1000.20 GB)
> Raid Devices : 4
> Total Devices : 4
>
> State : active
> Active Devices : 4
> Working Devices : 4
> Failed Devices : 0
>
> Layout : near=2
> Chunk Size : 64K
>
> Consistency Policy : resync
>
>
> UUID : xxx
> Number Major Minor RaidDevice State
> 3 8 0 0 active sync set-A /dev/sda
> 2 8 16 1 active sync set-B /dev/sdb
> 1 8 32 2 active sync set-A /dev/sdc
> 0 8 48 3 active sync set-B /dev/sdd
>
>
>
prev parent reply other threads:[~2022-06-14 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 9:14 How to enable bitmap on IMSM? Roman Mamedov
2022-06-14 14:45 ` Mariusz Tkaczyk [this message]
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=20220614164531.0000654e@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
/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).