mergerfs not distribute data evenly

    • OMV 5.x (beta)
    • mergerfs not distribute data evenly

      Hi,

      My data2 and data3 drives have more free space than the other data drive.
      My UFS current option is : Existing Path, Most Free Space.

      Any idea ?
      Images
      • Screen Shot 2019-12-11 at 8.41.52 PM.png

        53.77 kB, 799×366, viewed 57 times
      OMV v5.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
    • EPMFS will use the existing path FIRST. Paths will be preserved if possible.

      And only then, if the same relative path happen to exist on more than one filesystem, the filesystem with the most free space (MFS) will be used.

      So if a folder didn't exist on any drive, it is added to the drive with the most free space. After that the path exists on one drive only and all subsequent files in that folder end up there.

      If you want files to be added to the filesystem with the most free space, and paths created as needed, then you should use just MFS, not EPMFS. That will spread the files all over your drives.
      OMV 4: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4
    • Yes. I think so. I haven't tried it yet.
      No. Not if you have good verified backups.

      But if you don't have good verified backups then all your files will be toast. Any change you make is almost guaranteed to cause catastrophic data loss. I almost promise 100%!
      OMV 4: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4
    • What about using the mergerfs.balance script to even the spread of data across the drives?

      When I started with UFS/Snapraid I noticed uneven spread and this script ran for a few hours and evened disk usage up. Since then the disk use has been pretty even. My setup is MFS. This was on OMV v4.

      Naturally I had backups before I did this.

      John
    • I assume that new files will cause the same folders to be created on more drives, as new files are added and spread. The existing folders and files should remain where they are, unless you run the mergerfs.balance script.

      Changing from epmfs to mfs should be no different from creating a new mfs mergerfs pool from existing filesystems.

      Be sure to let us know how it works. I have not a lot of experience with mergerfs, but see a lot of potential in it.
      OMV 4: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4

      The post was edited 1 time, last by Adoby ().

    • The thread subject should be changed because SnapRAID has nothing to do with it.
      --
      Google is your friend and Bob's your uncle!

      RAID - Its ability to disappoint is inversely proportional to the user's understanding of it.

      ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380

      The post was edited 1 time, last by gderf ().

    • gderf wrote:

      The thread subject should be changed because SnapRAID has nothing to do with it.
      Done.
      omv 5.2.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.2
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!