omv7:omv7_plugins:mergerfs

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
omv7:omv7_plugins:mergerfs [2025/02/22 01:12] – [Notes] crashtestomv7:omv7_plugins:mergerfs [2025/09/29 14:56] (current) – [File Systems:] ryecoaaron
Line 135: Line 135:
 ---- ----
  
-When considering which of the two set up options to use, read over the information in Notes and File Systems. +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]].\\ 
 +\\ 
 +\\
  
 ---- ----
Line 249: Line 251:
 \\ \\
 \\ \\
-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]].
 \\ \\
 \\ \\
Line 393: Line 395:
  
 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=omv7:omv7_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=omv7:omv7_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=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.     * Shared Folders, for data storage, should always be added using the merged filesystem mount point.  
Line 404: Line 406:
 === File Systems: === === 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.\\+  * Supported MergerFS filesystems - https://trapexit.github.io/mergerfs/latest/faq/compatibility_and_integration/#what-filesystems-can-be-used-as-branches\\
   * 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.\\ 
 \\ \\
  • omv7/omv7_plugins/mergerfs.1740186757.txt.gz
  • Last modified: 2025/02/22 01:12
  • by crashtest