From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id EF3291FF0B7 for ; Fri, 13 Nov 2026 13:34:44 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 8BDC2216B0; Fri, 13 Nov 2026 13:34:39 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com, Thomas Lamprecht Subject: applied: [PATCH storage 3/3] lvm: qcow2: reserve LV space for persistent dirty bitmaps Date: Fri, 13 Nov 2026 13:33:40 +0100 Message-ID: <179457321563.216195.9337538545049273850.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261113012702.864671-4-t.lamprecht@proxmox.com> References: <20261113012702.864671-1-t.lamprecht@proxmox.com> <20261113012702.864671-4-t.lamprecht@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: 1794573274357 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.255 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: T5KNKZHQ75DQF2SGPFKZMKYUKWN2SVZD X-Message-ID-Hash: T5KNKZHQ75DQF2SGPFKZMKYUKWN2SVZD X-MailFrom: f.ebner@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 Fri, 13 Nov 2026 02:17:25 +0100, Thomas Lamprecht wrote: > Backup solutions like Veeam add persistent dirty bitmaps to qcow2 > images to track changed blocks. QEMU stores them inside the image when > the VM is stopped or migrated, in addition to what 'qemu-img measure' > reports and what the LV size is based on. So only the space from > rounding up to full extents was left for them, which depends on the > image size and can be close to nothing. As QEMU writes all new bitmap > clusters before freeing the old ones, a store needs room for two > copies, almost 4 MiB for one bitmap on a 900 GiB image. If that space > is missing, storing fails with ENOSPC and the bitmap is lost. > > [...] Applied this one too now, adapting the commit message slightly to state that this for Veeam's original integration, thanks! [3/3] lvm: qcow2: reserve LV space for persistent dirty bitmaps commit: d796f956ac990ded1c1b5e0ca50a451650dc807c