On Fri, 08 Aug 2025 16:03:22 +0200, Fiona Ebner wrote:
> Quoting the commit message from [0] verbatim:
>
> > thin_check v1.0.x reveals data block ref count issue that is not being
> > detected by previous versions, which blocks the pool from activation if
> > there are any leaked blocks. To reduce potential user complaints on
> > inactive pools after upgrading and also maintain backward compatibility
> > between LVM and older thin_check, we decided to adopt the 'auto-repair'
> > functionality in the --clear-needs-check-flag option, rather than
> > passing --auto-repair from lvm.conf.
>
> [...]
Applied, thanks!
[1/2] 8 to 9: lvm config: check that --clear-needs-check-flag is set if there
is a thin_check_options override
commit: d038d7d07e0edea6259a17dc7a952e761746c02d
[2/2] d/postinst: lvm config: check that --clear-needs-check-flag is set if
there is a thin_check_options override
commit: adcc7b208321062f8dc56402f1bfe35844d24392
Best regards,
--
Fabian Grünbichler <f.gruenbich...@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
