Differences

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

--- omv6:omv6_plugins:mergerfs [2024/07/08 23:40] – [Existing Path - Most Free Space] crashtest
+++ omv6:omv6_plugins:mergerfs [2024/07/09 01:38] (current) – [Existing Path - Most Free Space] crashtest
@@ Line 79: / Line 79: @@
 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.\\
+<html>
+<body>
+  <table width="100%" border="0">
+    <tr>
+      <td colspan="2" style="background-color:#69A5FF;height:30px;">
+        <strong><span style="color:#FFFFFF;font-size:110%;">&#160; Note For users who may test MergerFS using small virtual drives:</span></strong>
+      </td>
+    </tr>
+    <tr>
+      <td style="background-color:#E6FEFF;height:25px;width:380px;">
+        MergerFS balances drives to within 2% fill of all member drives. Populating tiny 8 to 10GB virtual drives with video files that may be as large
+as 1 or 2GB each (which is roughly 10 to 20% of a member drive) may trigger "ping pong" file copying between drives.  Filling tiny drives with huge files makes the "within 2%" balance goal, of the algorithm, unachievable.  When testing MergerFS using small virtual drives, use small files such as documents, pictures, or small audio files.
+    </tr>
+  </table>
+</body>
+</html>
 \\
 ----