MergerFS legacy paths are still being mapped

  • I've completed my upgrade from OMV5 to OMV6, and in the process I've re-created all my MergerFS pools and added a few more. But two of them are still being mapped to the old paths of /srv/a205e1bf-5ee0-41ca-a578-c8ed4d798245 and /srv/fb803389-0bb8-46c5-92c6-e96a213e4c77 as well as the new paths of /srv/mergerfs/NVR and /srv/mergerfs/Media, so the same data is showing up in both places. I have three other pools that were created after upgrading to OMV6 that only show up in /srv/mergerfs/. Any idea how to get rid of the old mappings? Niether of the old uuids show up in /etc/openmediavault/config.xml and they are not mapped in fstab


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

    • Offizieller Beitrag

    But two of them are still being mapped to the old paths of /srv/a205e1bf-5ee0-41ca-a578-c8ed4d798245 and /srv/fb803389-0bb8-46c5-92c6-e96a213e4c77

    Where are you seeing these if they aren't in the database? Does sudo omv-salt deploy run fstab mergerfs fix it?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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

    They show up in /srv/.

    You mean there are leftover directories that weren't cleaned up? I didn't add directory cleanup to the migration because I forgot to but they don't hurt anything. Are they actually mounted?

    It does not.

    It won't remove old directories that the plugin doesn't know about.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

  • Zitat von ryecoaaron

    Are they actually mounted?

    Yes, they are mounted, not just left over empty directories. All the files within the pools are accessible in both locations.


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

    Einmal editiert, zuletzt von niemer ()

    • Offizieller Beitrag

    what is the output of: sudo grep -r 'fb803389-0bb8-46c5-92c6-e96a213e4c77' /etc/*

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

  • Could OMV be referencing the config backups I made while I was fixing disks that were mapped using disk-by-label instead of disk-by-uuid?

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

    • Offizieller Beitrag

    Not sure what made these mount files but I would delete them.


    umount the filesystem

    then remove the mount file and reload systemd daemon

    sudo rm /etc/systemd/system/srv-fb803389\x2d0bb8\x2d46c5\x2d92c6\x2de96a213e4c77.mount

    sudo systemctl daemon-reload

    then see if the plugin recreates it

    sudo omv-salt deploy run mergerfs fstab

    repeat if more than one filesystem


    what is the output of: dpkg -l | grep openme

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!

  • That seemed to have fixed it, here's the output you asked for. Thank you for the help.


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

  • niemer

    Hat das Label gelöst hinzugefügt.
    • Offizieller Beitrag

    That seemed to have fixed it

    Good. I guess the migration doesn't clean up well enough.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


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


    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!