mergerfs
Reddit take
Not enough linked mention summaries yet; the source excerpts below are the evidence.
Pros
- i recommend using Mergerfs for the drivepool and Snapraid as a disk failure backup and recovery solution.
- i just formatted them both to ext4, mounted them, and used mergerFS to combine them into a single filepath, and now i just dump random stuff i don't care about on there
- MergerFS is cool.
- I use mergerfs to logically merge the two hard drives into a single 2TB drive, which I named /storage.
- the long term was important to me which is why I went with MergerFS + SnapRAID.
Cons
- Parent context: I also considered using the MergerFS client-side. The problem with that would be that I have multiple machines that are going to access this share - starting with Linux machines for ML, through random devices like a TV fo...
- You can also try mergerfs inside WSL, but idk how well it would play with WSL
- IMO, mergerFS is much better as a convenient way of reading data from multiple sources, rather than writing to multiple sources. You should organize your data and write to multiple sources cleanly so that you know where data is/isn't in...
- If you don't like truenas you could still run full freebsd or Linux and have a lot more options but still run zfs underneath or btrfs, mergerfs and snapraid however you want.
- Im currently Running a mergerFS pool and use rsnapshot to backup to another disk.
Sentiment
23 positive (70%) · 7 mixed (21%) · 3 negative (9%)
Trust + time weighted score: +61% · raw score 61%
What redditors said (10 of 33)
i recommend using Mergerfs for the drivepool and Snapraid as a disk failure backup and recovery solution.
i just formatted them both to ext4, mounted them, and used mergerFS to combine them into a single filepath, and now i just dump random stuff i don't care about on there
MergerFS is cool.
Parent context: I also considered using the MergerFS client-side. The problem with that would be that I have multiple machines that are going to access this share - starting with Linux machines for ML, through random devices like a TV for media playback, or an old laptop I use with a 3D printer, ending on Windows machines for monitoring and work. Reply: Client-side MergerFS would not be the most convenient at best, and would be impossible at worst.
I use mergerfs to logically merge the two hard drives into a single 2TB drive, which I named /storage.
the long term was important to me which is why I went with MergerFS + SnapRAID.
You can also try mergerfs inside WSL, but idk how well it would play with WSL
I use mergerfs to pool those 4TB folders together so I see them as one folder. When I add new files to the pool they go into the newest 4TB folder so the older folders rarely change which makes running backups a bit faster.
IMO, mergerFS is much better as a convenient way of reading data from multiple sources, rather than writing to multiple sources. You should organize your data and write to multiple sources cleanly so that you know where data is/isn't in the event of a disk failure.
I have two DAS running mergerfs. A 5 bay DAS that is used for large media files and a 10 bay DAS that is used for two independent sets of versioned backups of the 5 bay DAS. If a drive on the 5 bay DAS fail I have two main options. ... Provided the pool has free storage enough, I can simply remove the failed HDD and immediately restore from backups.
Compare
mergerfs vs Tailscalemergerfs vs Home Assistantmergerfs vs ZFS