📖 ~1 min read
Table of contents
Symptom & Impact
`df -h /` shows 100% used but `btrfs filesystem df /` indicates unallocated bytes remain.
Environment & Reproduction
Common on SLES 16 hosts that have run many zypper transactions over time.
Root Cause Analysis
Btrfs metadata chunks fill before data chunks, blocking new writes.
Quick Triage
Run `btrfs filesystem usage /` to see metadata vs data allocation.
Step-by-Step Diagnosis
Identify large snapshots via `snapper list` and `btrfs subvolume list /`.

Solution – Primary Fix
Run `btrfs balance start -dusage=50 -musage=50 /` during a maintenance window.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Remove old kernel packages with `purge-kernels` to free metadata.
Verification & Acceptance Criteria
Post-balance `btrfs filesystem df /` shows reclaimed unallocated space.
Rollback Plan
Pause the balance with `btrfs balance cancel /` and re-evaluate if I/O suffers.
Prevention & Hardening
Schedule periodic `btrfs-balance.timer` units to keep metadata healthy.
Related Errors & Cross-Refs
Often triggers `transactional-update` failures and full Snapper queues.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Btrfs storage administration on SLES 16 documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.