From: Zdenek Kabelac <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: stable-2.02 - thin: check for overprovisioning only once
Date: Tue, 9 Feb 2021 14:06:47 +0000 (GMT) [thread overview]
Message-ID: <20210209140647.B4F36383543D@sourceware.org> (raw)
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=6c99725261a53c6d984fa262980aab0df2ae6d62
Commit: 6c99725261a53c6d984fa262980aab0df2ae6d62
Parent: cfb9bf13c7073937591fa4dc4a0a93a975016bb1
Author: Zdenek Kabelac <zkabelac@redhat.com>
AuthorDate: Sun Feb 7 00:37:37 2021 +0100
Committer: Zdenek Kabelac <zkabelac@redhat.com>
CommitterDate: Tue Feb 9 14:45:29 2021 +0100
thin: check for overprovisioning only once
---
lib/metadata/lv_manip.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/lib/metadata/lv_manip.c b/lib/metadata/lv_manip.c
index 33624148c..c37757e9a 100644
--- a/lib/metadata/lv_manip.c
+++ b/lib/metadata/lv_manip.c
@@ -5449,10 +5449,6 @@ static int _lvresize_volume(struct logical_volume *lv,
lp->extents - lv->le_count,
pvh, alloc, lp->approx_alloc))
return_0;
- /* Check for over provisioning only when lv_extend() passed,
- * ATM this check does not fail */
- else if (!pool_check_overprovisioning(lv))
- return_0;
if (old_extents == lv->le_count)
log_print_unless_silent("Size of logical volume %s unchanged from %s (%" PRIu32 " extents).",
@@ -5705,6 +5701,11 @@ int lv_resize(struct logical_volume *lv,
backup(vg);
}
+
+ /* Check for over provisioning when extended */
+ if ((lp->resize == LV_EXTEND) && lv_is_thin_type(lv))
+ pool_check_overprovisioning(lv);
+
out:
log_print_unless_silent("Logical volume %s successfully resized.",
display_lvname(lv));
reply other threads:[~2021-02-09 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210209140647.B4F36383543D@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@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.