Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
omv6:omv6_plugins:mergerfs [2023/02/06 23:47] – [A Closing Note] crashtest | omv6:omv6_plugins:mergerfs [2023/11/11 04:54] – [Most Free Space] crashtest |
---|
| {{indexmenu_n>5}} |
\\ | \\ |
<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> |
| |
---- | ---- |
- The **Label** is **Merger1**\\ | - The **Label** is **Merger1**\\ |
- Note that the **Device Name** and the **Mount Point** are the same.\\ | - 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.\\ | - 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.\\ |
\\ | \\ |
<html><center>The result of file redistribution is as follows:</center></html> | <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>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 |}} | {{ ::mergerfs-14.jpg?800 |}} |
---- | ---- |
| |
==== 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. | * 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 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.\\ | - 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.\\ | - 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.\\ |
| \\ |
| |
| |
| |
| |