public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] lvm2: Update to version 2.03.22
Date: Mon, 07 Aug 2023 18:45:40 +0200	[thread overview]
Message-ID: <20230807164542.3448886-3-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230807164542.3448886-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2352 bytes --]

- Update from version 2.03.21 to 2.03.22
- Update of rootfile not required
- Changelog
    2.03.22 - 02nd August 2023
	  Fix pv_major/pv_minor report field types so they are integers, not strings.
	  Add lvmdevices --delnotfound to delete entries for missing devices.
	  Always use cachepool name for metadata backup LV for lvconvert --repair.
	  Make metadata backup LVs read-only after pool's lvconvert --repair.
	  Improve VDO and Thin support with lvmlockd.
	  Handle 'lvextend --usepolicies' for pools for all activation variants.
	  Fix memleak in vgchange autoactivation setup.
	  Update py-compile building script.
	  Support conversion from thick to fully provisioned thin LV.
	  Cache/Thin-pool can use error and zero volumes for testing.
	  Individual thin volume can be cached, but cannot take snapshot.
	  Better internal support for handling error and zero target (for testing).
	  Resize COW above trimmed maximal size is does not return error.
	  Support parsing of vdo geometry format version 4.
	  Add lvm.conf thin_restore and cache_restore settings.
	  Handle multiple mounts while resizing volume with a FS.
	  Handle leading/trailing spaces in sys_wwid and sys_serial used by deivce_id.
	  Enhance lvm_import_vdo and use snapshot when converting VDO volume.
	  Fix parsing of VDO metadata.
	  Fix failing -S|--select for non-reporting cmds if using LV info/status fields.
	  Allow snapshots of raid+integrity LV.
	  Fix multisegment RAID1 allocator to prevent using single disk for more legs.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/lvm2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lfs/lvm2 b/lfs/lvm2
index 4e2bd6235..7dedadcac 100644
--- a/lfs/lvm2
+++ b/lfs/lvm2
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2.03.21
+VER        = 2.03.22
 
 THISAPP    = LVM2.$(VER)
 DL_FILE    = $(THISAPP).tgz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 529bc01b3d1ba6207c9ddc95309b39e6293fcd0286334240b9fdc076da0b7bc7e026338ec0243564ec153f2fb5009014149c3f8e0db0cd47a29418af62068728
+$(DL_FILE)_BLAKE2 = 79bbea84bd82f111c1bb5de336e6a9f1368b2c9e43f075dccaa90c7746a364259ad278adf650379eca75f2803ed74e74dd372be2cca8518462182657f96a0033
 
 install : $(TARGET)
 
-- 
2.41.0


  parent reply	other threads:[~2023-08-07 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 16:45 [PATCH] gmp: Update to version 6.3.0 Adolf Belka
2023-08-07 16:45 ` [PATCH] harfbuzz: Update to version 8.1.1 Adolf Belka
2023-08-07 16:45 ` Adolf Belka [this message]
2023-08-07 16:45 ` [PATCH] smartmontools: Update to version 7.4 Adolf Belka
2023-08-07 16:45 ` [PATCH] xz: Update to version 5.4.4 Adolf Belka

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=20230807164542.3448886-3-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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