SharedLvmThin RC5.2

SharedLvmThin 0.9.0~rc5.2 release notes

Build date: 2026-09-07

RC5.2 adds a conservative, side-effect-free post-incident recovery
qualification. It does not add automatic storage recovery.

This release candidate is intended exclusively for Proxmox VE 9. It was
qualified on the PVE 9.2.x release line with Storage API 14 and 15. Proxmox VE
8 and earlier, Storage API 13 and Storage API 16+ are unsupported by RC5.2.

New command

sharedlvmthin recovery-check <storage-id>

The result is SAFE_FOR_MUTATION=YES only after exact path and storage
identity, owned thin-pool health, bounded LVM/PVE probes, PVE storage health,
quorum and scoped D-state evidence all pass. Any failure or ambiguity returns
STATE=RECOVERY_REQUIRED and SAFE_FOR_MUTATION=NO.

The checker never activates storage, rescans SCSI, reloads multipath, restarts
services, clears recovery state, initializes devices, repairs metadata or
runs an LVM mutation.

Qualification

• 64 public Python tests PASS; the complete qualification suite passed before
  the public source export.
• 87/87 Perl tests PASS.
• Real API14 and API15 read-only iSCSI/FCoE checks passed with redundant paths
  and exact WWID/PV/VG identity.
• Two package builds were byte-for-byte identical and passed package
  security/content validation. DEB SHA256:
  fd0e9b1ce0fc8a49261668bc19a1fba35ee3a772c64409e4894ffaf23cc9cf10.
• Sequential upgrade from RC5 and same-version reinstall passed on all three
  qualification nodes. Each of the six dpkg -i runs completed successfully.
• After the three-node deployment, both configured SharedLvmThin storages
  remained active everywhere, all six per-storage recovery checks returned
  SAFE_FOR_MUTATION=YES, quorum remained healthy and no D-state task was
  present. Configured dashboards remained active; the intentionally
  unconfigured node remained unconfigured and inactive.

RC5.2 remains a release candidate. Hardware FC, late physical SAN discovery
and host dm-thin recovery following complete path loss remain external gates.