mergerfs not working as expected

  • I have a raspberrypi where I have OMV installed and 4 - 8TB HDDs connected via USB to the pi. My hope was to combine the 4 - 8TB HDDs as one share to my network. Everything appears to be working, however, when one of the 8TB HDDs fills up, it does not allow me to copy any more data to the mergerfs pool.... says the disk is full.


    Ideally, I would love for it to be configured as a RAID in case of a failure of one of the HDDs.


    Plugins I have installed and configured are SNAPRAID, mergerfs and Multiple Device (I believe).


    Any assistance or direction would be greatly appreciated! Thank you!

  • KM0201

    Approved the thread.
  • The most frequent cause of your problem is misunderstanding the available choices of creation policies for your pool. Typically, choosing a creation policy that includes "existing path" and not having that path already existing on each hard drive in the pool will lead to exactly what you are seeing.


    You may want to read the mergerfs documentation that deals with this.


    GitHub - trapexit/mergerfs: a featureful union filesystem
    a featureful union filesystem. Contribute to trapexit/mergerfs development by creating an account on GitHub.
    github.com

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • Thank you for your reply gderf! I will give it a read. Do you think I will need to start from scratch where the existing data on the 1 full hard drive is concerned?

  • Thank you for your reply gderf! I will give it a read. Do you think I will need to start from scratch where the existing data on the 1 full hard drive is concerned?

    You can move some of the data from the full drive to the other drives yourself, or use the "balance" tool.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!