From: Heinz Mauelshagen <heinzm@redhat.com>
To: heinzm@redhat.com, dm-devel@redhat.com, snitzer@redhat.com
Subject: [PATCH 0/4] dm raid: fix raid set extensions not being synchronized
Date: Tue, 1 Oct 2019 17:47:51 +0200 [thread overview]
Message-ID: <cover.1569888100.git.heinzm@redhat.com> (raw)
This patch series fixes flaws causing raid set extensions not to be
synchronized in case a grown MD bitmap has to allocate additional pages.
When a raid set's grown, additional pages in the MD write-intent bitmap
may have to be allocated as a result. Because so far no md_bitmap_resize()
occurs in that process, additional new regions (aka MD bitmap chunks) aren't
set dirty during creation, thus they fail to be synchronized. Solve by
using md_bitmap_resize() in raid set size extensions to ensure dirtying
of additional, new regions.
Also address another flaw causing new regions not to be synchronized
after a raid set size reduction followed by an extension and streamline
recovery setup and progress status functions.
Passes all lvm2 test suite RAID tests.
Heinz Mauelshagen (4):
dm raid: change rs_set_dev_and_array_sectors API and callers
dm raid: to ensure resynchronization, perform raid set grow in preresume
dm raid: simplify rs_setup_recovery call chain
dm raid: streamline rs_get_progress() and its raid_status() caller side
.../admin-guide/device-mapper/dm-raid.rst | 2 +
drivers/md/dm-raid.c | 168 ++++++++++--------
2 files changed, 91 insertions(+), 79 deletions(-)
--
2.21.0
next reply other threads:[~2019-10-01 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 15:47 Heinz Mauelshagen [this message]
2019-10-01 15:47 ` [PATCH 1/4] dm raid: change rs_set_dev_and_array_sectors API and callers Heinz Mauelshagen
2019-10-01 15:47 ` [PATCH 2/4] dm raid: to ensure resynchronization, perform raid set grow in preresume Heinz Mauelshagen
2019-10-01 15:47 ` [PATCH 3/4] dm raid: simplify rs_setup_recovery call chain Heinz Mauelshagen
2019-10-01 15:47 ` [PATCH 4/4] dm raid: streamline rs_get_progress() and its raid_status() caller side Heinz Mauelshagen
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=cover.1569888100.git.heinzm@redhat.com \
--to=heinzm@redhat.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@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 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.