mergerfs.balance error

  • I have four disk mergerfs setup :


    /srv/dev-disk-by-label-Disk1

    /srv/dev-disk-by-label-Disk1

    /srv/dev-disk-by-label-Disk3

    /srv/dev-disk-by-label-Disk4


    The array is /srv/144ab994-0e0f-4a42-a06b-f37e84454803


    I add 3TB external USB drive:


    /srv/dev-disk-by-uuid-a017c3b4-20f1-4ab5-a0de-e39565cfbf07


    Shows as added in file system pages.


    Policy is existing path, most free space.


    The new drive is not being added to with new files so I run mergerfs.balance with output as below - so something wrong with disk 3 - how can I fix?


    Any help appreciated.



    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Two port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive (32 GB partitioned for OS)

    4x4TB WD Red NAS drives - MergerFS pool

    Seagate 5TB USB drive - SnapRAID parity

    Two x 1TB HD

    Seagate 3TB USB drive

    300 GB USB drive

  • Thanks for your input.


    I created two directories that exist on the pool on the /srv/dev-disk-by-uuid-a017c3b4-20f1-4ab5-a0de-e39565cfbf07 drive (the new 3TB USB drive) and again ran :


    mergerfs.balance /srv/144ab994-0e0f-4a42-a06b-f37e84454803


    Same error message.



    Changed policy to most free space - same error message.


    Something isn't right with Disk 3 but can't work out what it is.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Two port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive (32 GB partitioned for OS)

    4x4TB WD Red NAS drives - MergerFS pool

    Seagate 5TB USB drive - SnapRAID parity

    Two x 1TB HD

    Seagate 3TB USB drive

    300 GB USB drive

  • 7. rsync: sender failed to remove aquota.group: Operation not permitted (1)

    If I don't get it wrong, that error informs that rsync wants to delete the aquota.group file

    This is an internal file of the system. I get the impression that mergerfs.balance shouldn't try to delete it. Maybe it's a mergerfs.tools bug. This should be confirmed by someone who knows more than me. Sorry, I can't help you anymore.

  • The aquota.* files are used by the quota system, even if quotas are not enabled. They can not be routinely deleted, even by the root user, because they have their immutable bit set.


    As for why files are not being written to the newly added disk, the most likely causes are an incorrect (for the intended use case) mergerfs create policy or incorrect permission/ownership on the target disk directory.

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • Thanks changed the policy to mfs, rebooted and the new drive is being added to. Still errors with mergerfs.balance but less need to use it now.


    Using the exclude option deals with the aquota* error but now some new errors to investigate today.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Two port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive (32 GB partitioned for OS)

    4x4TB WD Red NAS drives - MergerFS pool

    Seagate 5TB USB drive - SnapRAID parity

    Two x 1TB HD

    Seagate 3TB USB drive

    300 GB USB drive

Participate now!

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