OMV4->5 residue cleanup blkmapd[275]: open pipe file /run/rpc_pipefs/nfs/blocklayout

  • Not sure if this problem existed when i was on OMV4, but i notice it when reviewing logs after OMV5 migration.


  • See the same thing on mine, and it is a fresh OMV5 install!


    root@NAS-OMV:~# systemctl status nfs-blkmap

    ● nfs-blkmap.service - pNFS block layout mapping daemon

    Loaded: loaded (/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: enabled)

    Active: active (running) since Mon 2020-05-18 14:41:21 CDT; 40min ago

    Process: 341 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS)

    Main PID: 346 (blkmapd)

    Tasks: 1 (limit: 4915)

    Memory: 600.0K

    CGroup: /system.slice/nfs-blkmap.service

    └─346 /usr/sbin/blkmapd


    May 18 14:41:21 NAS-OMV.kingsville.lan blkmapd[346]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory

    root@NAS-OMV:~#

  • If it is a fresh installation, the following could help:

    there are still two old service units in /lib/systemd/system/

    nfs-blkmap.service

    nfs-utils.service


    Rename or move them, reboot the server and try again.

    If all is fine, you won. In any other case: rename/move them back and reboot again.


    Or just switch to SMB if you are able to.

Participate now!

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