Differences

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

--- omv6:omv6_plugins:mergerfs [2023/05/09 01:21] – [Setup] crashtest
+++ omv6:omv6_plugins:mergerfs [2023/06/24 03:50] – [Setup] crashtest
@@ Line 180: / Line 180: @@
 ----
-==== 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 196: @@
 - 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.\\
+\\