Comment 25 for bug 1979885

@anarchetic
> The blkmapd core dump might be down to https://www.spinics.net/lists/linux-nfs/msg87598.html ?
> I'm seeing it as well, for some reason I can't get apport to upload the crash file :(

I'm unable to reproduce the problem on jammy, blkmapd does complain about the missing blocklayout file, but stays running:

root@j-nfs-server:~# mount -t rpc_pipefs
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)

root@j-nfs-server:~# blkmapd -f
blkmapd: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory

^Cblkmapd: exit on signal(2) <== me pressing ctrl-c

And I tried multiple combinations of that mount point being there, elsewhere, or not mounted at all.

If you still get the error, or even a crash file in /var/crash, please upload it to this ticket.

If there is no core dump or crash file, then perhaps at least try to get an strace output:

strace -f -o blkmapd.strace -s 500 blkmapd -f

And attach (or inspect) blkmapd.strace

In comment #9 we can see it was using the "wrong" rpc_pipefs mount point:
 blkmapd: open pipe file /var/lib/nfs/rpc_pipefs/nfs/blocklayout failed: No such file or directory

So I still think this might be related to bug #1971935 where if you install nfs-common in combination with something else using rpc_pipefs (like autofs, in that particular case), you would get rpc_pipefs mounted in /var/lib/nfs/rpc_pipefs whereas all daemons will be expecting it to be in /run/rpc_pipefs. But again, even in that case, I couldn't reproduce the blkmapd crash.