Differences

This shows you the differences between two versions of the page.

--- omv6:omv6_plugins:mergerfs [2023/01/26 19:29] – [Setup] crashtest
+++ omv6:omv6_plugins:mergerfs [2024/04/22 04:02] (current) – crashtest
@@ Line 1: / Line 1: @@
+{{indexmenu_n>8}}
 \\
 <html><center><b>The MergerFS Plugin For OMV6</b></center></html>
@@ Line 53: / Line 53: @@
 <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 |}}
 ----
-<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 |}}
+<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>
+\\
 ----
@@ Line 69: / Line 71: @@
 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.\\
+\\
 ----
@@ Line 96: / Line 102: @@
 <html><center>In the following, the mount point was named <b>Merger1</b>.</center></html>
 <html><center>The three previously noted drives (<b>/dev/sdc1</b>, <b>/dev/sdd1</b>, <b>/dev/sde1</b>) were selected.</center></html>
-<html><center>The storage policy was changed from the default to (<b>Most Free Space</b>.</center></html>
+<html><center>The storage policy was changed from the default to <b>Most free space</b>.</center></html>
 <html><center>The remaining settings were left at the defaults.</center></html>
@@ Line 115: / Line 121: @@
 - The **Label** is **Merger1**\\
 - Note that the **Device Name** and the **Mount Point** are the same.\\
-- Under **Type** which ordinarily displays the format of a Block Device, the **Type** is **FUSE.MERGERFS**.\\
+- Under **Type**, which ordinarily displays the file format type of a Block Device, the **Type** is **FUSE.MERGERFS**.\\
 - Note the "**copy icon**" next to the Mount Point.  The copy icon copies the exact Mount Point path to the client workstation's clip board.  This may be useful for command line operations.\\
 \\
@@ Line 167: / Line 173: @@
 <html><center>The result of file redistribution is as follows:</center></html>
 <html><center>While the total data under <b>Merger1</b> has not changed, note that data has been distributed among member drives.</center></html>
-<html><center>(There are minor differences because MergerFS will not "split" very large files.)</center></html>
+<html><center>(There are minor differences between drives because MergerFS balances to within 2%, by default, and it will not "split" very large files.)</center></html>
 {{ ::mergerfs-14.jpg?800 |}}
@@ Line 180: / Line 186: @@
 ----
-==== Notes ====
+===== 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]].
+===== 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.
@@ Line 193: / Line 202: @@
 - MergerFS does not fully support COW (Copy on Write) filesystems like ZFS or BTRFS.  When creating a MergerFS array, simple filesystems like EXT4 or XFS are recommended.\\
 - While MergerFS may work with NTFS or FAT (Windows filesystems) when using a package like ntfs-3g, they are non-POSIX file systems.  File and folder permission issues may result in MergerFS and in OMV.  For the best use experience, Linux native filesystems like EXT4 or XFS are recommended.\\
+\\
@@ Line 209: / Line 221: @@
 -> [[https://github.com/OpenMediaVault-Plugin-Developers/openmediavault-mergerfs|Source Code]]
+----
+===== A Closing Note =====
+We, who support the openmediavault project, hope you’ve found this guide to be useful and that you’ll find your openmediavault server to be efficient, easy to use, and enjoyable.\\
+\\
+If you found this plugin guide to be helpful, please consider a modest donation to support the hosting costs of this server.\\
+\\
+**OMV-Extras.org**
+\\
+<html>
+<form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top">
+<input type="hidden" name="cmd" value="_s-xclick">
+<input type="hidden" name="hosted_button_id" value="2BQNGSC8HQJME">
+<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_SM.gif" name="submit" title="PayPal - The safer, easier way to pay online!" alt="Donate with PayPal button" border="0">
+<img alt="" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1" border="0">
+</form>
+</html>
+\\
+\\
+**Venmo: ryecoaaron** \\