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="Now Playing" data-source="post: 671202" data-attributes="member: 2381"><p>Think of mergerfs etc. as a means of presenting separate file systems as a unified whole whilst in reality they're still independent drives each containing their own filesystem. If a drive fails that drive's contents is no longer presented in the unified whole. What I don't like about these tools is that if you write to the "pool" your files will be placed wherever the tool determines is most appropriate...so whilst presented as organised files, the reality is folder structures get duplicated across various drives over time, with files belonging in one folder being distributed in a folder by that name across the various drives. So... if a drive fails you don't really know what you've lost...until you try access a particular file and find it's no longer in the folder you stored it in. This is where snapraid is crucial in being able to reconstruct what was.</p><p></p><p>Basically I've used mhddfs to present a single storage pool to say my music library, but for all file copy/move operations I bypass it and write directly to the drives/ folders in question.</p></blockquote><p></p>
[QUOTE="Now Playing, post: 671202, member: 2381"] Think of mergerfs etc. as a means of presenting separate file systems as a unified whole whilst in reality they're still independent drives each containing their own filesystem. If a drive fails that drive's contents is no longer presented in the unified whole. What I don't like about these tools is that if you write to the "pool" your files will be placed wherever the tool determines is most appropriate...so whilst presented as organised files, the reality is folder structures get duplicated across various drives over time, with files belonging in one folder being distributed in a folder by that name across the various drives. So... if a drive fails you don't really know what you've lost...until you try access a particular file and find it's no longer in the folder you stored it in. This is where snapraid is crucial in being able to reconstruct what was. Basically I've used mhddfs to present a single storage pool to say my music library, but for all file copy/move operations I bypass it and write directly to the drives/ folders in question. [/QUOTE]
Insert quotes…
Verification
Post reply
Audio and Video Talk
Computers & Networking
mergerfs - pooling of disks in linux (JBOD)
Top