Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Audio and Video Talk
Computers & Networking
mergerfs - pooling of disks in linux (JBOD)
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
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: 671827" data-attributes="member: 18399"><p>Why not use random? If your concern is distribution of files rather than data that's the easiest way to spread out files. Each drive will statistically get the same number of files. Percentage will not work that way. If you happen to put one big file on a small drive it's out of commission until the large drive fills up.</p><p></p><p>But whether "total loss of a folder" is good or bad is usually dependent on the content. Is it better to lose half your movies than all? Probably. Is it better to lose half your songs from an album? Probably not. It'd be more frustrating to repopulate the missing files than just replace the whole. If you have rsync'ed dupes it's less of an issue but if you have actual lose it does.</p><p></p><p>That's why ep{l,m}fs exist in part because then you can manually layout the core paths and then you kindof get to choose how it works. Not *exactly* but if I put "movies" on all drives and "music" on two drives and use epmfs then movies can end up anywhere, music on two drives, but anything created (assuming "all" isn't used for mkdir) will end up colocated in the same directory on the same drive.</p></blockquote><p></p>
[QUOTE="trapexit, post: 671827, member: 18399"] Why not use random? If your concern is distribution of files rather than data that's the easiest way to spread out files. Each drive will statistically get the same number of files. Percentage will not work that way. If you happen to put one big file on a small drive it's out of commission until the large drive fills up. But whether "total loss of a folder" is good or bad is usually dependent on the content. Is it better to lose half your movies than all? Probably. Is it better to lose half your songs from an album? Probably not. It'd be more frustrating to repopulate the missing files than just replace the whole. If you have rsync'ed dupes it's less of an issue but if you have actual lose it does. That's why ep{l,m}fs exist in part because then you can manually layout the core paths and then you kindof get to choose how it works. Not *exactly* but if I put "movies" on all drives and "music" on two drives and use epmfs then movies can end up anywhere, music on two drives, but anything created (assuming "all" isn't used for mkdir) will end up colocated in the same directory on the same drive. [/QUOTE]
Insert quotes…
Verification
Post reply
Audio and Video Talk
Computers & Networking
mergerfs - pooling of disks in linux (JBOD)
Top