| Both sides previous revision Previous revision Next revision | Previous revision |
| omv7:omv7_plugins:mergerfs [2025/02/22 00:38] – crashtest | omv7:omv7_plugins:mergerfs [2025/02/22 01:21] (current) – [Notes] crashtest |
|---|
| ====== The MergerFS Plugin For OMV7 ====== | ====== The MergerFS Plugin For OMV7 ====== |
| \\ | \\ |
| \ | \\ |
| <html><center><b>February 21rst, 2025 - Rev 1.0</b></center></html> | <html><center><b>February 21rst, 2025 - Rev 1.0</b></center></html> |
| \\ | \\ |
| \\ | \\ |
| {{ :omv7:mergerfs-method-02.1.jpg?nolink&450 |}} | {{ :omv7:mergerfs-method-02.1.jpg?nolink&450 |}} |
| | \\ |
| | ---- |
| | |
| | When considering which of the two set up options to use, read over the information in [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:mergerfs#notes|Notes]] and [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:mergerfs#file_systems|File Systems]].\\ |
| | \\ |
| \\ | \\ |
| |
| |
| For users interested in **Option 1**, see Option 1 following.\\ | For users interested in **Option 1**, see Option 1 following.\\ |
| For those who are interested in **Option 2**, follow this link -> [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:mergerfs#setting_up_option_2|Setting up Option 2]]. $$$$ Fix doc link.\\ | For those who are interested in **Option 2**, follow this link -> [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:mergerfs#setting_up_option_2|Setting up Option 2]].\\ |
| \\ | \\ |
| \\ | \\ |
| \\ | \\ |
| \\ | \\ |
| With the MergerFS array set up, continue on to -> [[https://wiki.omv-extras.org/doku.php?id=docs_in_draft:mergerfs#additional_tools|additional tools]]. | With the MergerFS array set up, continue on to -> [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:mergerfs#additional_tools|additional tools]]. |
| \\ | \\ |
| \\ | \\ |
| ===== 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=omv7:utilities_maint_backup#backing_up_data|full data backup]] is recommended for recovery from data disasters. |
| | |
| | * Shared Folders, for data storage, should always be added using the merged filesystem mount point. |
| | * If relational database files are added directly to a member drive, to get past the latency issue, use [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:mergerfs#option_2|Option 2]] - MergerFS with root folders. The relational database should be installed using the mount point of a physical drive. This will install the database outside of MergerFS' folder. |
| | * Dockers use a form of overlayfs that is not compatible with MergerFS. If Docker containers and image storage are required, again, [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:mergerfs#option_2| Option 2]] - MergerFS with root folders should be used. Docker images and containers should be installed using the mount point of a physical drive. This will install the Docker related files outside of MergerFS' folder. |
| | * If users are already committed to [[https://wiki.omv-extras.org/doku.php?id=omv7:omv7_plugins:mergerfs#option_1|Option 1]]; for relational database files and/or docker storage, a small SSD or hard drive outside of a merged pool is recommended. |
| |
| * Shared Folders should always be added using the merged filesystem mount point. | === File Systems: === |
| * If a Shared Folder is added directly to a member drive (this is possible), thereafter, the Balance Pool tool can not be used. | |
| * If relational database files are added directly to a member drive, to get past the latency issue, the Balance Pool tool can not be used. | |
| * Docker containers and image storage should not be added to a mergerfs pool. Dockers use a form of overlayfs that is not compatible with MergerFS. | |
| * For relational database files and/or docker storage, a small SSD or hard drive outside of a merged pool is recommended. | |
| |
| * File Systems: | * 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.\\ | |
| \\ | \\ |
| |