Reply to thread

Help Support AVForums:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

Message: <blockquote data-quote="trapexit" data-source="post: 671478" data-attributes="member: 18399">Hi. Trapexit here. Author of mergerfs.mergerfs is a little smarter than you describe. It has different policies on where to create things. If you have a "movie" drive and a "music" drive it will respect those existing directories and not place files random if you don't want. However, your point is still generally true. You don't know, necessarily, what's gone when a drive dies.To work around this I do a few things. Some of them are described in my storage backup and recovery docs[0]. One is to use something like CrashPlan and backup both the merged location and the originals. You can easily recover a whole drive that way. SnapRaid provides similar. I also have jobs that run nightly which dump a listing of all files on each drive and back those up too. (need to write up a doc on metadata backup.)I'm also working on a very simple tool that would hash files so corruption can be detected but that's more for if you have CrashPlan or some other offsite backup and don't use ZFS or something like SnapRaid.I have misc tooling that work with mergerfs[1] and have considered creating something which would more formally document what files were where for better auditing when something fails. Instead of just those file listings I mentioned.I have in the mergerfs and backup docs FAQs one "why mergerfs" if you wish to compare. They aren't too detailed but give general reasons.-[0] https://github.com/trapexit/backup-and-recovery-howtos-[1] https://github.com/trapexit/mergerfs-tools</blockquote>

Verification