SerpApi.Org
After years of using Windows, I assumed the trade-off of its Storage Spaces feature was universal. It usually entailed backing up everything on the required drives, wiping the drives, building a new pool, and then moving the files back to the drives.
I was surprised when I used mergerfs on Linux and was able to pull in existing drives without touching any of the files already on them. The process required no formatting, no migration, and no starting over. It's become the only way I combine drives.
My drives didn't need to change
mergerfs pools what's already there — nothing gets rebuilt
When I first used Windows Storage Spaces, the one part of the entire process I hated the most was wiping my drives. It meant I was forced to have a backup plan in place before using Storage Spaces. Not everyone has the luxury of an extra drive large enough to back up the data on all the drives they plan to add to a pool.
Mergerfs on Linux doesn't require this. It's a FUSE-based union filesystem. This is just a fancy way of saying that it shows you the drives you have mounted in a single folder. It doesn't change the actual drives; they retain the filesystems already on them. When I use it, my ext4, XFS, Btrfs, or NTFS drives mounted through ntfs3 driver stay the same before and after the process.
Also, it doesn't move files on the drives during the process. It avoids copying or reformatting and doesn't lock any data into a new pool format that would require mergerfs before it can be read again. Since nothing about the drives changes, they remain readable even if you remove them later.
Mergerfs uses a placement policy (a simple rule for deciding where a file lands) to distribute new files across the drives. I typically direct it to favor the drive with the most available space, but there are other options, and from personal experience, it's not something I have to think about daily.
It feels like a far better implementation compared to Storage Spaces on Windows, where the first step is creating a new virtual disk and formatting it before any data goes in. This time, rather than building new storage, you're only asking the existing drives to behave as a single unit.
It felt surprisingly simple
Pooling existing drives took less than a minute
On my home server, I run Linux Mint, and when I first decided to merge my files, I was expecting some fiddling. But it was surprisingly easy. After installing mergerfs, I wrote a little mount configuration to point to my existing drives, and in under a minute, all of them were showing up as one folder.
The speed of the process was surprising and very different from Windows Storage Spaces, which would've taken me several minutes, since I'd first have had to back up terabytes of media to an external drive, wipe everything, and copy it all back. Without doing much or spending much time, I ended up with one folder instead of three.
I needed confirmation that it actually worked, so I dropped my first files into the pool, and when I checked, they had spread out across the physical drives where the placement policy directed, with the old files staying put on their original drives.
I encountered a mount order problem. Any drives that aren't mounted before mergerfs starts don't show up in the pool. This is probably the problem if one of your drives seems to have disappeared from the pool. However, the fix is simple: you only have to adjust when things load at boot by establishing a strict mount order.
The main reason I'd recommend mergerfs to anyone who needs to consolidate a pile of drives is that it takes just a single config change to add an extra drive; nothing has to be rebuilt.
They solve different problems
The better choice depends on what you're protecting
It's important to say that while mergerfs and Storage Spaces seem like similar tools, they're not always competing for the same job, making it hard to say one is always the better option.
Redundancy is an interesting element that stands out on the table. Since mergerfs isn't striping or mirroring any data, a failed drive means the pooled namespace remains available, but files residing on the failed drive are lost. With mirroring or parity enabled, Storage Spaces can survive a failed drive without data loss. This makes Storage Spaces the preferred option for protection against failed drives without the need for extra third-party configurations.
You can pair mergerfs with SnapRAID to add parity protection while keeping mergerfs' flexibility.
For the right setup, it's hard to beat
Mergerfs isn't the tool everyone should use. But I run a media server with Jellyfin, and I have a collection that keeps growing. Since it periodically needs upgrading, a full rebuild occasionally is too much to ask, so mergerfs fits perfectly. If I were expecting RAID-like protection, maybe because I keep critical data, I'd pair mergerfs with SnapRAID.
Linux has an interesting reputation that made me honestly expect its design to be more complicated. I came away pleasantly surprised.
