| Both sides previous revision Previous revision Next revision | Previous revision |
| omv6:omv6_plugins:mergerfs [2023/06/24 03:49] – [Setup] 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><b>Most Free Space</b> is a single directive that performs exactly what it suggests.</center></html> | <html><center><b>Most Free Space</b> is a single directive that performs exactly what it suggests.</center></html> |
| <html><center>If dissimilar drive sizes are used, <b>Most Free Space</b> will direct more data toward the largest drive when compared to smaller member drives.</center></html> | <html><center>If dissimilar drive sizes are used, <b>Most Free Space</b> will direct data toward the largest drive.</center></html> |
| {{ ::mergerfs-04.jpg?600 |}} | {{ ::mergerfs-04.jpg?600 |}} |
| ---- | ---- |
| <html><center>Drives are filled by "percentage used" which will distribute files among all drives in an even manner.</center></html> | |
| <html><center>With the added advantage of being able to use different sized drives, this storage policy roughly mimics the storage distribution attribute of RAID5.</center></html> | <html><center>When the space remaining between all drives is roughly the same, data will be distributed equally among all member drives.</center></html> |
| |
| {{ ::mergerfs-05.jpg?600 |}} | {{ ::mergerfs-05.jpg?600 |}} |
| |
| | <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.\\ |
| | \\ |
| ---- | ---- |
| |
| * **Docs** (Links to the MergerFS support pages for MergerFS and MergerFS tools.) While the MergerFS plugin supports **Restart**, **Balance Pool** and **Deduplicate** in the GUI, note that there are several additional MergerFS tools that can be used from the command line. | * **Docs** (Links to the MergerFS support pages for MergerFS and MergerFS tools.) While the MergerFS plugin supports **Restart**, **Balance Pool** and **Deduplicate** in the GUI, note that there are several additional MergerFS tools that can be used from the command line. |
| |
| | ---- |
| |
| ==== Replacing a Failed MergerFS Drive ==== | ===== Replacing a Failed MergerFS Drive ===== |
| |
| Since MergerFS is frequently used with SnapRAID, replacing a failed MergerFS Drive is part of the final step in recovering a MergerFS / SnapRAID array, as detailed -> [[https://wiki.omv-extras.org/doku.php?id=omv6:omv6_plugins:snapraid#replacing_a_failed_drive_in_mergerfs|here]]. | Since MergerFS is frequently used with SnapRAID, replacing a failed MergerFS Drive is part of the final step in recovering a MergerFS / SnapRAID array, as detailed -> [[https://wiki.omv-extras.org/doku.php?id=omv6:omv6_plugins:snapraid#replacing_a_failed_drive_in_mergerfs|here]]. |
| ==== Notes ==== | ===== Notes ===== |
| |
| * MergerFS, by design, distributes folders and files between multiple hard drives. Accordingly, to gain the ability to recover a hard drive along with other recovery features, users are strongly encouraged to consider the addition of **SNAPRAID** to protect a MergerFS array. Further, -> [[https://wiki.omv-extras.org/doku.php?id=omv6:utilities_maint_backup#backing_up_data|full data backup]] is recommended for recovery from data disasters. | * MergerFS, by design, distributes folders and files between multiple hard drives. Accordingly, to gain the ability to recover a hard drive along with other recovery features, users are strongly encouraged to consider the addition of **SNAPRAID** to protect a MergerFS array. Further, -> [[https://wiki.omv-extras.org/doku.php?id=omv6:utilities_maint_backup#backing_up_data|full data backup]] is recommended for recovery from data disasters. |