From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 077421FF136 for ; Mon, 18 May 2026 22:06:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BDCF719EC4; Mon, 18 May 2026 22:06:21 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Subject: applied: [PATCH-SERIES storage v2 0/7] lvm plugin: activation/renaming/tag improvements Date: Mon, 18 May 2026 22:05:27 +0200 Message-ID: <177913441445.4051941.13637547164119461705.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260331115011.102276-1-f.ebner@proxmox.com> References: <20260331115011.102276-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779134732947 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.121 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: K4OUPN46D2VIEFJEL4QOXNEHXWVFCUH2 X-Message-ID-Hash: K4OUPN46D2VIEFJEL4QOXNEHXWVFCUH2 X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 31 Mar 2026 13:49:48 +0200, Fiona Ebner wrote: > Changes in v2: > * Add more improvements, v1 was only the first two patches. > > Fix multiple issues related to volume activation, volume renaming and > LV tags. In particular fix bug #7143 to avoid issues when there are > multiple storages with disks with the same name and #7280 to fix > disk reassign for qcow2. Also fix handling tags when doing disk > reassing for both, raw and qcow2. > > [...] Applied, thanks! [1/7] fix #7280: lvm plugin: rename: activate qcow2 volume to read snapshot info commit: 3a7e0610c655665ec24ad3a7d2b2d8d37b31c33c [2/7] lvm plugin: rename: improve error message commit: 8f914ad5451505b085a3344aaf3b12fc252dd40d [3/7] lvm plugin: rename: update tags when renaming commit: f5a6f9b406dd9f08793a76af14a461d11881972d [4/7] lvm plugin: remove cryptic partial comment commit: d64a9c0060e997676b4891f46f31799a53ec308c [5/7] lvm plugin: activation: avoid extra variable commit: 828590057240a80bd7c8bfd29191fef352a30acb [6/7] fix #7143: ensure qcow2 volume (de)activation is limited to target volume chain commit: 5c586c0894d58fd5be714bac6c45862121bc831b [7/7] lvm plugin: schema: align description of 'tagged_only' with actual behavior commit: a9eab8c678c80afc595fb13396168b39e2eac970