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 268751FF0AD for ; Sun, 04 Oct 2026 21:34:45 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id C9B6F21462; Sun, 04 Oct 2026 21:34:17 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Erik Fastermann Subject: applied: [PATCH storage] fix #6915: lvmthin: leave room for repair Date: Sun, 4 Oct 2026 21:33:27 +0200 Message-ID: <179114230665.2862530.8456258128363945260.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260806080208.41768-1-e.fastermann@proxmox.com> References: <20260806080208.41768-1-e.fastermann@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: 1791142438131 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.642 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: 33NL7HWWHMVMEOA6M2IE6CYFBL66QIUG X-Message-ID-Hash: 33NL7HWWHMVMEOA6M2IE6CYFBL66QIUG 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 Thu, 06 Aug 2026 10:02:08 +0200, Erik Fastermann wrote: > The pool is sized to fill the volume group, leaving a flat 128M free > regardless of device size. That is not enough to repair damaged pool > metadata. As described in lvmthin(7), `lvconvert --repair` writes the > recovered metadata into the VGs pmspare LV, promotes it to be the pool > metadata LV and keeps the damaged one as a visible ThinPool_metaN > backup, so a replacement spare has to be allocated afterwards. Without > free extents the repair is not possible. > > [...] Applied, thanks! [1/1] fix #6915: lvmthin: leave room for repair https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=f648eff9cd4ddcb00815c0637927fcc7039f5e3b