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 EBF6D1FF146 for ; Tue, 26 May 2026 16:08:44 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 40B4E19DB; Tue, 26 May 2026 16:08:44 +0200 (CEST) Message-ID: Date: Tue, 26 May 2026 16:08:06 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH-SERIES storage/qemu-server v3 00/11] fix #7094: external snapshot delete: ensure commit target is large enough To: Lukas Sichert , pve-devel@lists.proxmox.com References: <20260519110646.25060-1-f.ebner@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779804465514 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.009 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 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: 7TJPIG23XG3W6YVOFHBVPYMXN4UHMSTP X-Message-ID-Hash: 7TJPIG23XG3W6YVOFHBVPYMXN4UHMSTP 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: Am 26.05.26 um 3:57 PM schrieb Lukas Sichert: > I also tested the live path with the old code using the same general > setup. I did not get the same No space left on device failure there; > instead the block job was cancelled in my environment, so I could not > reproduce the live failure cleanly. That is the failure for the live case ;) It gets canceled, because there is not enough space to commit everything. > > With the patch installed, the offline case succeeds as expected because > the target snapshot LV is resized before commit. I also checked lvmthin > for regressions, and normal qm snapshot, qm resize, and qm delsnapshot > behavior still works there. The live case should work with the patch too, could you test that too?