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

gwaitsi · May 2nd 2020

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

Code

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 Sat 2020-05-02 17:16:48 CEST; 3min 30s ago
  Process: 26691 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS)
 Main PID: 26692 (blkmapd)
    Tasks: 1 (limit: 4915)
   Memory: 580.0K
   CGroup: /system.slice/nfs-blkmap.service
           └─26692 /usr/sbin/blkmapd

May 02 17:16:48 nas.net.lan systemd[1]: Starting pNFS block layout mapping daemon...
May 02 17:16:48 nas.net.lan blkmapd[26692]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
May 02 17:16:48 nas.net.lan systemd[1]: Started pNFS block layout mapping daemon.

Display More

odinb · May 18th 2020

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:~#

Das Glubschi · May 20th 2020

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.

zevleu · Jul 25th 2020

I'm facing exactly the same problem: I got it after migration from OMV4 to OMV5 and it generated erratic reboot of my NAS.

Yesterday, I decided to do a fresh install of OMV5: still exactly the same issue, causing multiple reboot every day.

May you please tell me if you solved it and how did you do?

I'm really wondering why all OMV5 users are not facing the same problem...

zevleu · Jul 26th 2020

I've remvod nfs-blkmap.service and my system is now stable.

There is something weird with this service indeed.

m4tt0 · Oct 25th 2020

Encountered the same issue after an OMV4 -> 5 update.

Removing both, nfs-blkmap.service and nfs-utils.service, resulted in a "broken pipe" error after reboot. However, keeping nfs-utils.service and just removing nfs-blkmap.service, as you've suggested, fixed the syslog error for me, too.

Participate now!