| Both sides previous revision Previous revision Next revision | Previous revision |
| omv6:omv6_plugins:mergerfs [2023/11/11 04:54] – [Most Free Space] crashtest | omv6:omv6_plugins:mergerfs [2024/04/22 04:02] (current) – crashtest |
|---|
| {{indexmenu_n>5}} | {{indexmenu_n>8}} |
| \\ | \\ |
| <html><center><b>The MergerFS Plugin For OMV6</b></center></html> | <html><center><b>The MergerFS Plugin For OMV6</b></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>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> |
| | \\ |
| ---- | ---- |
| |
| Note, in the following, the distribution of paths among member drives. Once a new folder is created, on a drive with the **Most Free Space**, a path is established. According to the first directive all subsequently saved files will go to the **Existing Path**. | Note, in the following, the distribution of paths among member drives. Once a new folder is created, on a drive with the **Most Free Space**, a path is established. According to the first directive all subsequently saved files will go to the **Existing Path**. |
| |
| {{ ::mergerfs-06.jpg?600 |}} | ---- |
| |
| The issue that this 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. This issue can be corrected using the **Balance Pool** Tool {{::mergerfs-07-balance_pool.jpg?30|}} which will spread data among the array's member drives.\\ | 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.\\ |
| |
| | {{ ::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.\\ |
| | \\ |
| ---- | ---- |
| |