Linux Server / Filesystems, LVM & Recovery
Check LVM snapshot consumption during a backup window
A snapshot can become unusable when its allocated change-tracking space fills while the origin continues receiving writes.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
lvs -a -o lv_name,origin,lv_attr,lv_size,data_percentRead the result
The output helps identify snapshot relationships and utilization where supported. Classic and thin snapshots have different capacity and failure behavior.
Resolve and verify
Compare snapshot growth with backup duration and origin write rate. Plan supported capacity or schedule changes and validate that the backup used a valid snapshot.
Before changing production
Do not merge or remove a production snapshot without confirming its purpose, dependencies and rollback implications.