On 22/06/2026 3:04 pm, Paul Leiber wrote:
my main suspect for the root cause of the dual-head database
I read about rollback to earlier state of filesystem when a device supporting snapshots (LVM or filesystem) was mounted using FS UUID instead of volume identifier. Snapshots have the same UUID as the real device, so it is undefined what is found firs on boot. Just ignore this remark if snapshots are not supported on all stack levels of your storage for the DB.
