| Both sides previous revision Previous revision Next revision | Previous revision |
| omv6:omv6_plugins:mergerfs [2024/04/22 04:02] – crashtest | omv6:omv6_plugins:mergerfs [2024/07/09 01:38] (current) – [Existing Path - Most Free Space] crashtest |
|---|
| |
| <html><center>With the added advantage of being able to use different sized drives, the <b>Most Free Space</b> storage policy roughly mimics the storage distribution attribute of RAID5.</center></html> | <html><center>With the added advantage of being able to use different sized drives, the <b>Most Free Space</b> storage policy roughly mimics the storage distribution attribute of RAID5.</center></html> |
| | <html><center>Typically, the <b>Most Free Space</b> storage policy is a good choice when merged drives will be populated with libraries of large video and music files.</center></html> |
| \\ | \\ |
| ---- | ---- |
| ---- | ---- |
| |
| The issue that the **Existing Path** directive can create is due to the difference in files sizes. When compared to documents or even picture files, video files can be massive, ranging from 100's of megabytes to several gigabytes. If users increasingly add large video files to a MergerFS array, the **Existing Path** directive can easily fill one drive of the array completely. At that point, the array will stop accepting files destined for the full drive.\\ | The issue that the **Existing Path** directive can create is due to the difference in files sizes. When compared to documents or even picture files, music and video files can be massive, ranging from 100's of megabytes to several gigabytes. If users increasingly add large video files to a MergerFS array, the **Existing Path** directive can easily fill one drive of the array completely. At that point, the array will stop accepting files destined for the full drive.\\ |
| |
| {{ ::mergerfs-06.jpg?600 |}} | {{ ::mergerfs-06.jpg?600 |}} |
| |
| This issue can be corrected using the **Balance Pool** Tool {{::mergerfs-07-balance_pool.jpg?30|}} which will redistribute data among the array's member drives.\\ | This issue can be corrected using the **Balance Pool** Tool {{::mergerfs-07-balance_pool.jpg?30|}} which will redistribute data among the array's member drives.\\ |
| | |
| | <html> |
| | <body> |
| | <table width="100%" border="0"> |
| | <tr> |
| | <td colspan="2" style="background-color:#69A5FF;height:30px;"> |
| | <strong><span style="color:#FFFFFF;font-size:110%;">  Note For users who may test MergerFS using small virtual drives:</span></strong> |
| | </td> |
| | </tr> |
| | <tr> |
| | <td style="background-color:#E6FEFF;height:25px;width:380px;"> |
| | MergerFS balances drives to within 2% fill of all member drives. Populating tiny 8 to 10GB virtual drives with video files that may be as large |
| | as 1 or 2GB each (which is roughly 10 to 20% of a member drive) may trigger "ping pong" file copying between drives. Filling tiny drives with huge files makes the "within 2%" balance goal, of the algorithm, unachievable. When testing MergerFS using small virtual drives, use small files such as documents, pictures, or small audio files. |
| | </tr> |
| | </table> |
| | </body> |
| | </html> |
| \\ | \\ |
| ---- | ---- |