Estimated reading time: 2 minutes

When we decide to expand our digital archive, perhaps purchasing a two-bay external enclosure or assembling a small home server, we always come up against the same problem: how to physically join disks to see a single large folder? There are two most common routes: the classic JBOD and the most modern mergerFS. But, as we shall see, the difference between the two can determine whether your data survives a failure.

JBOD (Spanning): The physical union

The JBOD (Just a Bunch Of Disks), in the mode “spanning”, concatenates disks at the block level. If you connect a 4TB and a 2TB drive, the operating system will see a single 6TB logical volume. Data is written sequentially: filled the first disk, the controller switches to second.

Pro

• Extreme simplicity: Once configured, the system sees only one standard volume.
• Space efficiency: Take advantage of the 100% the capacity of each disk, even if they are of different sizes.

Counter

• Catastrophic risk: If one of the two disks dies, il File System (NTFS, EXT4, etc.) becomes corrupted on a structural level. Recovering files from the surviving disk becomes a complex and often unsuccessful technical operation, as files can be fragmented between the two drives.

mergerFS: The logical union

Unlike the JBOD, mergerFS works at the file system level via FUSE (Filesystem in Userspace). Not “based” disk sectors, but it creates a sort of “together” virtual that shows the contents of multiple disks as if they were in a single folder.

Pro

• Fault tolerance: Be a record if it breaks, you only lose the files that were physically on that disk. The other data on the other disk remains intact, readable and ready to use simply by connecting the drive to another PC.
• Total flexibility: You can add or remove disks of any size at any time without having to format anything.

Counter

• Performance: Being based on FUSE, has a light load on the CPU (negligible on modern PCs, but relevant on extremely dated systems).
• Configuration: Requires a minimum of familiarity with Linux to edit the file /etc/fstab.

Because consumer products don't use mergerFS?

You will have noticed that the two-bay external garages sold in shops (WD, LaCie, Seagate) they almost always use JBOD or RAID. The reason is not technical, but commercial:

1. Cross-Platform Compatibility: A hardware JBOD box is seen as a standard disk by Windows, macOS and Linux without the need for additional software. mergerFS is not native on Windows and would require the user to install third-party drivers.
2. Hardware costs: Managing the JBOD requires a very cheap controller chip. Running a software merge like mergerFS would require a more powerful CPU inside the box, increasing the final price.

Best Practice: What to check before purchasing

If you're looking for a two-disc enclosure, don't just look at the price. Here's what you need to check so you don't regret your purchase:

Characteristic	What to look for	Why?
Independent mode	Support “Clear RAID” the “Non-RAID”	It allows you to see separate disks and use software like mergerFS to safely merge them.
S.M.A.R.T. Passthrough	Check in the specifications or reviews	Indispensable for monitoring the health of disks. Lots of cheap controllers “they hide” the status of the disks.
Ventilation	Aluminum case or active fan	Two discs closed in a plastic box without air circulation are destined for a short life.

Conclusion: If you care about your data, avoid hardware JBOD solutions “all in one”. The best choice for an aware user is to buy a box that displays the discs separately and manage the union via software. You will have total control and the certainty that a controller or single disk failure does not turn into a total disaster.