Btrfsmaintenance vs e4defrag

Btrfsmaintenance is a free set of scripts for automating maintenance on Btrfs filesystems. It can run scrub, balance, trim, and defragmentation, with separate settings to enable, disable, and configure each task. Scrub reads filesystem data and metadata to check checksums, which can reveal hardware problems or bit rot; when a good redundant copy exists, it can repair data automatically. Periodic jobs can be scheduled with cron or systemd timers, though only one scheduling method can be active on a system. The project supports widely used distributions, provides installation guidance for Debian-based systems, and describes manual installation for others. On SUSE-based distributions, a zypper plugin can defragment RPM database files after package installation. Settings are designed for a default installation with Btrfs on the root filesystem and can be changed in the sysconfig file. Scrub may create intense read activity, and balance can use substantial read and write resources; task concurrency can be serialized to manage impact. Directory defragmentation does not descend into other mount points, nested subvolumes, or snapshots, which need separate paths listed. It is licensed under GPL-2.0 and available for Linux and self-hosted use.

e4defrag is a Linux utility for defragmenting extent-based files on ext4 filesystems. It accepts an individual file, a directory and its files, or a device mounted as ext4. The utility aims to place targeted data in more contiguous blocks, which the manual says can improve file access speed. Its -c option reports current and ideal fragmentation counts and a fragmentation score without making changes; the score appears only when the check runs as root. With -v, it prints error messages and each file’s fragmentation count before and after defragmentation. e4defrag checks for ext4 and reports an error for other filesystem types. It does not support swap files, files in lost+found, or files allocated in indirect blocks. A target device or mount point excludes files belonging to another device’s mount point, and fragmented or insufficient free space can prevent improvement. The manual says it is safe to run while another application uses a file, though shared memory and disk bandwidth can slow both. It is free at free.