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


  • 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 6.0.30-1 Shaitan | 64 bit | 5.15 proxmox kernel | plugins :: omvextrasorg 6.0.9 | kvm 6.1.19 | mergerfs 6.1.1 | zfs 6.0.9
    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.
    Please don't PM for support... Too many PMs!

  • 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 6.0.30-1 Shaitan | 64 bit | 5.15 proxmox kernel | plugins :: omvextrasorg 6.0.9 | kvm 6.1.19 | mergerfs 6.1.1 | zfs 6.0.9
    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Quote from 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.


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

    omv 6.0.30-1 Shaitan | 64 bit | 5.15 proxmox kernel | plugins :: omvextrasorg 6.0.9 | kvm 6.1.19 | mergerfs 6.1.1 | zfs 6.0.9
    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.
    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?

  • 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 6.0.30-1 Shaitan | 64 bit | 5.15 proxmox kernel | plugins :: omvextrasorg 6.0.9 | kvm 6.1.19 | mergerfs 6.1.1 | zfs 6.0.9
    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.
    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.


  • niemer

    Added the Label resolved
  • That seemed to have fixed it

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

    omv 6.0.30-1 Shaitan | 64 bit | 5.15 proxmox kernel | plugins :: omvextrasorg 6.0.9 | kvm 6.1.19 | mergerfs 6.1.1 | zfs 6.0.9
    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

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