On Fri, 14 May 2021, Petr Vorel wrote:
>
> The failure has really something to do with rpcbind ("mount.nfs: portmap query
> failed:"):
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> write(2, "mount.nfs: trying 10.0.0.2 prog "..., 66) = 66
> socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) = 5
> fcntl(5, F_GETFL) = 0x2 (flags O_RDWR)
> fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK) = 0
> connect(5, {sa_family=AF_INET, sin_port=htons(37873), sin_addr=inet_addr("10.0.0.2")}, 16) = -1 EINPROGRESS (Operation now in progress)
> select(6, NULL, [5], NULL, {tv_sec=10, tv_usec=0}) = 1 (out [5], left {tv_sec=9, tv_usec=999998})
> getsockopt(5, SOL_SOCKET, SO_ERROR, [111], [4]) = 0
> fcntl(5, F_SETFL, O_RDWR) = 0
> close(5) = 0
> write(2, "mount.nfs: portmap query failed:"..., 79) = 79
The "111" from getsockopt...SO_ERROR is ECONNREFUSED. That suggests
that rpcbind wasn't even running.
This is different to the first strace you reported where mount.nfs
successfully connected to rpcbind, sent and request and got a response,
and then fail the mount. That would happen if, for example, rpc.mountd
wasn't running.
So I think these failures are caused by some problem with restarting the
services and aren't actually testing the code at all.
Could you try again and make sure rpcbind and rpc.mountd are running on
the server before attempting the mount?
Thanks,
NeilBrown
