From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: jes@trained-monkey.org
Cc: linux-raid@vger.kernel.org, colyli@suse.de
Subject: [PATCH 0/6] imsm: expand improvements
Date: Mon, 29 May 2023 15:52:32 +0200 [thread overview]
Message-ID: <20230529135238.18602-1-mariusz.tkaczyk@linux.intel.com> (raw)
merge_extents() was initially designed to support creation only. Expand
feature was added later and the current code was not updated properly.
Now, we can see two issues:
1. --size=max used with expand and create result in different array size.
2. In scenarios, where volume were deleted an recreated it may not be
possible to expand the volume.
The patchset addresses listed issues and removes limitation to the last
volume for expand.
Mariusz Tkaczyk (6):
imsm: move sum_extents calculations to merge_extents()
imsm: imsm_get_free_size() refactor.
imsm: introduce round_member_size_to_mb()
imsm: move expand verification code into new function
imsm: return free space after volume for expand
imsm: fix free space calculations
super-intel.c | 363 ++++++++++++++++++++++++++++----------------------
1 file changed, 202 insertions(+), 161 deletions(-)
--
2.26.2
next reply other threads:[~2023-05-29 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 13:52 Mariusz Tkaczyk [this message]
2023-05-29 13:52 ` [PATCH 1/6] imsm: move sum_extents calculations to merge_extents() Mariusz Tkaczyk
2023-05-29 13:52 ` [PATCH 2/6] imsm: imsm_get_free_size() refactor Mariusz Tkaczyk
2023-05-29 13:52 ` [PATCH 3/6] imsm: introduce round_member_size_to_mb() Mariusz Tkaczyk
2023-05-29 13:52 ` [PATCH 4/6] imsm: move expand verification code into new function Mariusz Tkaczyk
2023-05-29 13:52 ` [PATCH 5/6] imsm: return free space after volume for expand Mariusz Tkaczyk
2023-05-29 13:52 ` [PATCH 6/6] imsm: fix free space calculations Mariusz Tkaczyk
2023-09-01 15:37 ` [PATCH 0/6] imsm: expand improvements Jes Sorensen
2023-05-31 15:21 Mariusz Tkaczyk
2023-05-31 15:30 ` Mariusz Tkaczyk
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=20230529135238.18602-1-mariusz.tkaczyk@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=colyli@suse.de \
--cc=jes@trained-monkey.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).