From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id C2D131FF136 for ; Mon, 18 May 2026 22:05:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 44C7119C77; Mon, 18 May 2026 22:05:51 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Subject: applied: [PATCH-SERIES storage/manager/container/qemu-server 0/8] fix #6819: lvm plugin: list images: use approximate size for inactive qcow2 volumes Date: Mon, 18 May 2026 22:05:26 +0200 Message-ID: <177913441449.4051941.2036116867145149179.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260513130548.143270-1-f.ebner@proxmox.com> References: <20260513130548.143270-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: 1779134732884 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: BW2WBHSRUI37VZ5FZHGXVCHVDFMOK3UK X-Message-ID-Hash: BW2WBHSRUI37VZ5FZHGXVCHVDFMOK3UK 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 Wed, 13 May 2026 15:05:32 +0200, Fiona Ebner wrote: > For qcow2 volumes on LVM, the exact size can only be queried when the > LV is active. For a shared LVM, an LV might already be active on > another node, so it must not be activated. Also, doing so for each > volume would be costly. Instead, return only the approximate size when > the LV is inactive. > > Adapt the list volumes API/CLI implementations as well as the UI and > volume rescan operations for guests to handle casees where the exact > size is not present, but only the new approximate size property. > > [...] Applied, thanks! [storage] [1/4] api: content: add missing imports and group/order according to style guide commit: 985fa74770c1ad774d37108cce3796265b45fe89 [2/4] pvesm: add missing imports and group/order according to style guide commit: ad21e1ce3f92237ccd7fa18fea6e723114aec511 [3/4] api/cli: list content: declare size optional and add approximate-size commit: 7ce747e3a365bcea664246b711f522ca29ddec74 [4/4] fix #6819: lvm plugin: list images: use approximate size for inactive qcow2 volumes commit: 225a87225383b6da9d3baaf307207c24de5bd074 [manager] [1/1] fix #6819: storage: content view: fallback to approximate size commit: 4882f0f49d9d1eceb3a4282d9a1357c7609c474e [container] [1/2] volume rescan: also consider zero-sized volumes commit: 6bb0bbdf4221e1e168b3e6f63155bccacb42bf5f [2/2] volume rescan: also consider volumes listed only with an approximate size commit: f7af8082aea6088644f9778d169534e96eafc146 [qemu-server] [1/1] volume rescan: also consider volumes listed only with an approximate size commit: cfbe86c2b73846fe91a1e22dbf8f79e70a41f996