Debian 11 – LVM thin pool metadata or data reaches 100 percent – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Writes fail on thin-provisioned volumes, risking application downtime and data inconsistency.

Environment & Reproduction

Common on virtualization hosts and snapshot-heavy systems using thin pools.

Root Cause Analysis

Thin pool data or metadata space exhausted without autoextend policy headroom.

Quick Triage

Check Data% and Meta% usage immediately and stop nonessential writes.

Step-by-Step Diagnosis

Run: sudo lvs -a -o +seg_monitor,data_percent,metadata_percent,lv_size,vg_name; sudo vgs; sudo pvs.

Solution – Primary Fix

Extend pool: sudo lvextend -L +20G /; if metadata high run sudo lvextend –poolmetadatasize +1G /; then fstrim where appropriate.

Solution – Alternative Approaches

Delete old snapshots and implement lvm.conf thin_pool_autoextend_threshold settings.

Verification & Acceptance Criteria

Data% and Meta% return below alert thresholds and writes proceed normally.

Rollback Plan

Restore from snapshot/backup if volume remains read-only or metadata corruption is detected.

Prevention & Hardening

Track thin pool growth and enforce snapshot lifecycle cleanup automation.

Related Errors & Cross-Refs

Related to dm-thin no free space warnings and failed writeback cache commits.

Related tutorial: View the step-by-step tutorial for Debian 11.

View all Debian 11 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

LVM thin provisioning docs and Debian device-mapper operational notes.