omv6:omv6_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
omv6:omv6_plugins:mergerfs [2024/07/09 01:37] – [Existing Path - Most Free Space] crashtestomv6:omv6_plugins:mergerfs [2024/07/09 01:38] (current) – [Existing Path - Most Free Space] crashtest
Line 91: Line 91:
       <td style="background-color:#E6FEFF;height:25px;width:380px;">       <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         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 (which roughly 10 to 20% of a member drive) each 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 file.+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>     </tr>
   </table>   </table>
  • omv6/omv6_plugins/mergerfs.1720489047.txt.gz
  • Last modified: 2024/07/09 01:37
  • by crashtest