Re: Sid: NFSv3 mounting problem (again!)
Hi.
On Mon, Aug 20, 2018 at 04:04:01PM +0200, Grzegorz Sójka wrote:
> On 08/20/18 15:12, Reco wrote:
> > Hi.
> >
> > On Mon, Aug 20, 2018 at 12:42:14PM +0200, Grzegorz Sójka wrote:
> > > I added /etc/services /etc/rpc and now rpcbind is starting but:
> > >
> > > #rpcinfo -p localhist
> > > program vers proto port service
> > > 100000 4 tcp 111 portmapper
> > > 100000 3 tcp 111 portmapper
> > > 100000 2 tcp 111 portmapper
> > > 100000 4 udp 111 portmapper
> > > 100000 3 udp 111 portmapper
> > > 100000 2 udp 111 portmapper
> > > 100024 1 udp 49035 status
> > > 100024 1 tcp 58571 status
> > >
> > > there is no nlockmgr.
> >
> > I always said that part of the result is better that none at all.
> > This one is suitable for the client, and it advertizes NFS support from
> > version 2 to version 4 inclusive.
> > For NFS server I'd expect to see 'nfs' (v3 or v4).
>
> If I'm getting this right nlockmgr is needed only on the server side?
And only if you're using NFSv3 and your mount options does not include
'nolock'. The question is - what's on the server?
> Anyway, I still get the following error:
> # mount -v /mnt/users
> mount.nfs: timeout set for Sat Aug 18 18:55:52 2018
> mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.0.129'
> mount.nfs: prog 100003, trying vers=3, prot=6
> mount.nfs: trying 192.168.0.129 prog 100003 vers 3 prot TCP port 2049
A client tries NFSv3 via tcp:2049 and presumably meets TCP RST.
> mount.nfs: prog 100005, trying vers=3, prot=17
> mount.nfs: trying 192.168.0.129 prog 100005 vers 3 prot UDP port 37385
> mount.nfs: Protocol not supported
A server says to the client that NFSv3 over udp is not supported here.
But without rpcinfo from the server it's impossble to tell what's really
supported.
> On all the working clients I do have:
>
> # rpcinfo -p
> program vers proto port service
> 100000 4 tcp 111 portmapper
> 100000 3 tcp 111 portmapper
> 100000 2 tcp 111 portmapper
> 100000 4 udp 111 portmapper
> 100000 3 udp 111 portmapper
> 100000 2 udp 111 portmapper
> 100021 1 udp 44149 nlockmgr
> 100021 3 udp 44149 nlockmgr
> 100021 4 udp 44149 nlockmgr
> 100021 1 tcp 37814 nlockmgr
> 100021 3 tcp 37814 nlockmgr
> 100021 4 tcp 37814 nlockmgr
> 100024 1 udp 52987 status
> 100024 1 tcp 55392 status
>
> So, nlockmgr is missing only on the broken client.
Note that your client advertizes NFSv4 support. Maybe that's what they
really use?
Reco
Reply to: