Re: Sid: NFSv3 mounting problem (again!)
On 08/20/18 22:23, deloptes wrote: Michael Stone wrote: What on earth does this mean? How did the system get into such a state that these were missing? he wrote net-base was missing, but why was net-base missing? As I wrote in one of my posts, the system was installed using debootstrap --variant=minbase. So this is really minimal set of packages. Moreover, the netbase package is not in dependencies of the nfs-common. finally I think he solved the problem Yes, the problem is solved and it looks that nlockmgr is needed on both server and client sides. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFSv3 mounting problem (again!)
Michael Stone wrote: > What on earth does this mean? How did the system get into such a state > that these were missing? he wrote net-base was missing, but why was net-base missing? finally I think he solved the problem regards
Re: Sid: NFSv3 mounting problem (again!)
The package netbase was missing. Thanks for your help -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFSv3 mounting problem (again!)
On Mon, Aug 20, 2018 at 05:25:07PM +0300, Reco wrote: Note that your client advertizes NFSv4 support. Maybe that's what they really use? The output of `mount` or /proc/mounts will show what's actually in use. Mike Stone
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 > > > 104 tcp111 portmapper > > > 103 tcp111 portmapper > > > 102 tcp111 portmapper > > > 104 udp111 portmapper > > > 103 udp111 portmapper > > > 102 udp111 portmapper > > > 1000241 udp 49035 status > > > 1000241 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 13, trying vers=3, prot=6 > mount.nfs: trying 192.168.0.129 prog 13 vers 3 prot TCP port 2049 A client tries NFSv3 via tcp:2049 and presumably meets TCP RST. > mount.nfs: prog 15, trying vers=3, prot=17 > mount.nfs: trying 192.168.0.129 prog 15 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 > 104 tcp111 portmapper > 103 tcp111 portmapper > 102 tcp111 portmapper > 104 udp111 portmapper > 103 udp111 portmapper > 102 udp111 portmapper > 1000211 udp 44149 nlockmgr > 1000213 udp 44149 nlockmgr > 1000214 udp 44149 nlockmgr > 1000211 tcp 37814 nlockmgr > 1000213 tcp 37814 nlockmgr > 1000214 tcp 37814 nlockmgr > 1000241 udp 52987 status > 1000241 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
Re: Sid: NFSv3 mounting problem (again!)
On Mon, Aug 20, 2018 at 12:42:14PM +0200, Grzegorz Sójka wrote: I added /etc/services /etc/rpc What on earth does this mean? How did the system get into such a state that these were missing? Mike Stone
Re: Sid: NFSv3 mounting problem (again!)
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 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 49035 status 1000241 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? 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 13, trying vers=3, prot=6 mount.nfs: trying 192.168.0.129 prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 192.168.0.129 prog 15 vers 3 prot UDP port 37385 mount.nfs: Protocol not supported On all the working clients I do have: # rpcinfo -p program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000211 udp 44149 nlockmgr 1000213 udp 44149 nlockmgr 1000214 udp 44149 nlockmgr 1000211 tcp 37814 nlockmgr 1000213 tcp 37814 nlockmgr 1000214 tcp 37814 nlockmgr 1000241 udp 52987 status 1000241 tcp 55392 status So, nlockmgr is missing only on the broken client. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFSv3 mounting problem (again!)
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 > 104 tcp111 portmapper > 103 tcp111 portmapper > 102 tcp111 portmapper > 104 udp111 portmapper > 103 udp111 portmapper > 102 udp111 portmapper > 1000241 udp 49035 status > 1000241 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). Reco
Re: Sid: NFSv3 mounting problem (again!)
I added /etc/services /etc/rpc and now rpcbind is starting but: #rpcinfo -p localhist program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 49035 status 1000241 tcp 58571 status there is no nlockmgr. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFSv3 mounting problem
Grzegorz Sójka wrote: > On 08/19/18 16:52, deloptes wrote: >> Grzegorz Sójka wrote: >> >>> /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash) >> >> and you are 100% sure you are using nfs v3 and not nfs v4 on the not >> working client? you do not have firewalls enabled? > > Yes, here is appropriate line from fstab: > > Hermes:/home/trash /home/trash nfs vers=3,defaults,noatime,nodiratime 0 0 > > > you do not have firewalls enabled? > I do have firewall only on external interface. Moreover I have a dual > boot (the some network settings) and the other distro mounts fine. there could be difference in the default from other and this distro, so this does not count. what about /etc/default/nfs-common and possibly which modules are loaded - is rpc running etc
Re: Sid: NFSv3 mounting problem
Hi. On Sun, Aug 19, 2018 at 05:11:02PM +0200, Grzegorz Sójka wrote: > On 08/19/18 16:52, deloptes wrote: > > Grzegorz Sójka wrote: > > > > > /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash) > > > > and you are 100% sure you are using nfs v3 and not nfs v4 on the not working > > client? you do not have firewalls enabled? > > Yes, here is appropriate line from fstab: > > Hermes:/home/trash /home/trash nfs vers=3,defaults,noatime,nodiratime 0 0 Out of pure curiosity, can you provide the result of rpcinfo -p localhost from the NFS server, 'good' NFS client and a 'problematic' one? And, while we're at it anyway, the result of: rpcinfo -p hermes from both the clients? Reco
Re: Sid: NFSv3 mounting problem
On 08/19/18 16:52, deloptes wrote: Grzegorz Sójka wrote: /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash) and you are 100% sure you are using nfs v3 and not nfs v4 on the not working client? you do not have firewalls enabled? Yes, here is appropriate line from fstab: Hermes:/home/trash /home/trash nfs vers=3,defaults,noatime,nodiratime 0 0 > you do not have firewalls enabled? I do have firewall only on external interface. Moreover I have a dual boot (the some network settings) and the other distro mounts fine. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFSv3 mounting problem
Grzegorz Sójka wrote: > /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash) and you are 100% sure you are using nfs v3 and not nfs v4 on the not working client? you do not have firewalls enabled?
Re: Sid: NFSv3 mounting problem
On 08/19/18 00:08, deloptes wrote: Grzegorz Sójka wrote: Hi there I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop. When I try to mount any NFS share on the desktop I always get the following: # mount -v /home/trash 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 13, trying vers=3, prot=6 mount.nfs: trying 192.168.0.129 prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 192.168.0.129 prog 15 vers 3 prot UDP port 37385 mount.nfs: Protocol not supported I'm pretty convinced that the server is running fine. It's because I have Odroid-C2 client (and two other raspberry pi) using NFSv3 without any problems. Actually, I did copy-paste the following line: Hermes:/home/trash /home/trash nfs vers=3,defaults,noatime,nodiratime 0 0 from the odroid to pc fstab. Thanks in advance for any help Did you add the new client to the exportfs file on the server? I have a whole subnet in exports: /home/trash 192.168.0.0/24(no_subtree_check,async,rw,all_squash) -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFSv3 mounting problem
Grzegorz Sójka wrote: > > Hi there > > I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop. > When I try to mount any NFS share on the desktop I always get the > following: > > # mount -v /home/trash > 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 13, trying vers=3, prot=6 > mount.nfs: trying 192.168.0.129 prog 13 vers 3 prot TCP port 2049 > mount.nfs: prog 15, trying vers=3, prot=17 > mount.nfs: trying 192.168.0.129 prog 15 vers 3 prot UDP port 37385 > mount.nfs: Protocol not supported > > I'm pretty convinced that the server is running fine. It's because I > have Odroid-C2 client (and two other raspberry pi) using NFSv3 without > any problems. Actually, I did copy-paste the following line: > > Hermes:/home/trash /home/trash nfs vers=3,defaults,noatime,nodiratime 0 0 > > from the odroid to pc fstab. > > Thanks in advance for any help Did you add the new client to the exportfs file on the server?
Re: Sid: NFSv3 mounting problem
On Sat 18 Aug 2018 at 21:31:05 +0200, Grzegorz Sójka wrote: > Hi there > > I have stretch x86_64 home server running NFSv3 and Sid-x86-64 desktop. When > I try to mount any NFS share on the desktop I always get the following: > > # mount -v /home/trash > 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 13, trying vers=3, prot=6 > mount.nfs: trying 192.168.0.129 prog 13 vers 3 prot TCP port 2049 > mount.nfs: prog 15, trying vers=3, prot=17 > mount.nfs: trying 192.168.0.129 prog 15 vers 3 prot UDP port 37385 > mount.nfs: Protocol not supported > > I'm pretty convinced that the server is running fine. It's because I have > Odroid-C2 client (and two other raspberry pi) using NFSv3 without any > problems. Actually, I did copy-paste the following line: > > Hermes:/home/trash /home/trash nfs vers=3,defaults,noatime,nodiratime 0 0 > > from the odroid to pc fstab. > > Thanks in advance for any help You have put your post into an existing thread. That does help you or the people who are using this thread. Please post a completely new mail. -- Brian.
