Odd behavior with multiple insances of UnionFS with same drives

  • To me it sounds like you are trying to create an ambiguous configuration.

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


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

  • I wouldn't call them ambiguous, they have different policies and min free space limits. One will be used for relatively large infrequently changing files and the other for smaller more often changing files.

    OMV7 | Xeon W-1250 | 48 GB | Linux 6.5 PVE

  • By ambiguous, I mean that the target branches are the same. The names of the pools being different doesn't change that.


    Let's see what @trapexit sez.

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


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

    • Offizieller Beitrag

    I have no problem creating multiple pools with the same branches with slightly different options.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    when you create a shared folder do your pools show up with the same name?

    Yep. Probably hard for the OS and/or plugin to differentiate between them. I changed the plugin to allow disks to be used in multiple pools but it was never intended to create identical pools (never tested until now). This isn't something that I will try to fix either (if it is even possible).

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Yep. Probably hard for the OS and/or plugin to differentiate between them. I changed the plugin to allow disks to be used in multiple pools but it was never intended to create identical pools (never tested until now). This isn't something that I will try to fix either (if it is even possible).

    Huh... So the OS doesn't use the pool name to differentiate? Just the drives in the pool?

    OMV7 | Xeon W-1250 | 48 GB | Linux 6.5 PVE

    • Offizieller Beitrag

    Huh... So the OS doesn't use the pool name to differentiate? Just the drives in the pool?

    The OS sees different mount points but the branches are identical. Linux can mount the same filesystem multiple times. When I mentioned the OS, I really meant OMV.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • The OS sees different mount points but the branches are identical. Linux can mount the same filesystem multiple times. When I mentioned the OS, I really meant OMV.

    they have different mount points so they should be able to be identified as unique instances by OMV when adding a new shared folder, right?


    /srv/dev-disk-by-label-5QD5GJQ1:/srv/dev-disk-by-label-5QD47DFQ /srv/643b2a45-44a4-4368-a43d-e9fbc30292f3 fuse.mergerfs defaults,allow_other,direct_io,use_ino,category.create=mfs,minfreespace=4G 0 0
    /srv/dev-disk-by-label-JEH73UM1:/srv/dev-disk-by-label-2YHY6W8D /srv/de2cbcb9-492c-472f-bbe3-d33e735f108f fuse.mergerfs defaults,allow_other,direct_io,use_ino,func.getattr=newest,category.create=mfs,minfreespace=4G 0 0
    /srv/dev-disk-by-label-JEH73UM1:/srv/dev-disk-by-label-2YHY6W8D /srv/4d0cc6bd-6e1d-4e45-a04f-03555cda6b9b fuse.mergerfs defaults,allow_other,direct_io,use_ino,category.create=mfs,minfreespace=12G 0 0

    OMV7 | Xeon W-1250 | 48 GB | Linux 6.5 PVE

    • Offizieller Beitrag

    they have different mount points so they should be able to be identified as unique instances by OMV when adding a new shared folder, right?

    OMV doesn't differentiate between drives by mountpoint. So, after spending more time looking into this than I wanted to, I don't think the plugin is at fault. OMV uses standard tools (findfs, blkid, etc) that work with true devices but don't work quite right with fuse filesystems especially when there are almost identical setups. All I can say is don't use identical pools.


    One partial solution is to select the drives in a different order when creating the pool since the plugin does know which drives you select first. So:


    pool 1 -> select drive 1 then drive 2 then drive 3
    pool 2 -> select drive 2 then drive 3 then drive 1
    pool 3 -> select drive 3 then drive 1 then drive 2


    I confirmed the above method gets the labels correct when creating a sharedfolder. If you only have two drives in the pool, you can only have two identical pools. This is the best I can offer.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!