From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Erik Fastermann <e.fastermann@proxmox.com>
Subject: applied: [PATCH storage] fix #6915: lvmthin: leave room for repair
Date: Sun, 4 Oct 2026 21:33:27 +0200 [thread overview]
Message-ID: <179114230665.2862530.8456258128363945260.b4-ty@b4> (raw)
In-Reply-To: <20260806080208.41768-1-e.fastermann@proxmox.com>
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
prev parent reply other threads:[~2026-10-04 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:02 [PATCH storage] fix #6915: lvmthin: leave room for repair Erik Fastermann
2026-10-04 19:33 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179114230665.2862530.8456258128363945260.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=e.fastermann@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox