Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #198994 > unrolled thread

Sid: NFSv3 mounting problem

Started byGrzegorz Sójka <pld@sojka.co>
First post2018-08-18 22:10 +0200
Last post2018-08-20 23:10 +0200
Articles 17 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Sid: NFSv3 mounting problem Grzegorz Sójka <pld@sojka.co> - 2018-08-18 22:10 +0200
    Re: Sid: NFSv3 mounting problem deloptes <deloptes@gmail.com> - 2018-08-19 00:10 +0200
      Re: Sid: NFSv3 mounting problem Grzegorz Sójka <pld@sojka.co> - 2018-08-19 16:30 +0200
        Re: Sid: NFSv3 mounting problem deloptes <deloptes@gmail.com> - 2018-08-19 17:00 +0200
          Re: Sid: NFSv3 mounting problem Grzegorz Sójka <pld@sojka.co> - 2018-08-19 17:20 +0200
            Re: Sid: NFSv3 mounting problem Reco <recoverym4n@gmail.com> - 2018-08-19 20:00 +0200
            Re: Sid: NFSv3 mounting problem deloptes <deloptes@gmail.com> - 2018-08-20 08:40 +0200
              Sid: rpcbind not starting (was NFSv3 mounting problem) Grzegorz Sójka <pld@sojka.co> - 2018-08-20 11:40 +0200
              Re: Sid: NFSv3 mounting problem (again!) Grzegorz Sójka <pld@sojka.co> - 2018-08-20 12:50 +0200
                Re: Sid: NFSv3 mounting problem (again!) Reco <recoverym4n@gmail.com> - 2018-08-20 15:20 +0200
                  Re: Sid: NFSv3 mounting problem (again!) Grzegorz Sójka <pld@sojka.co> - 2018-08-20 16:10 +0200
                    Re: Sid: NFSv3 mounting problem (again!) Reco <recoverym4n@gmail.com> - 2018-08-20 16:30 +0200
                      Re: Sid: NFSv3 mounting problem (again!) Michael Stone <mstone@debian.org> - 2018-08-20 16:40 +0200
                        Re: Sid: NFSv3 mounting problem (again!) Grzegorz Sójka <pld@sojka.co> - 2018-08-20 17:20 +0200
                Re: Sid: NFSv3 mounting problem (again!) Michael Stone <mstone@debian.org> - 2018-08-20 16:30 +0200
                  Re: Sid: NFSv3 mounting problem (again!) deloptes <deloptes@gmail.com> - 2018-08-20 22:30 +0200
                    Re: Sid: NFSv3 mounting problem (again!) Grzegorz Sójka <pld@sojka.co> - 2018-08-20 23:10 +0200

#198994 — Sid: NFSv3 mounting problem

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-18 22:10 +0200
SubjectSid: NFSv3 mounting problem
Message-ID<wofHP-Fv-1@gated-at.bofh.it>
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 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.0.129 prog 100003 vers 3 prot TCP port 2049
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

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


-- 
Pozdrawiam
Grzesiek

Wysłane z kompa wolnego od wirusów Billa Gatesa.

[toc] | [next] | [standalone]

#198997

Fromdeloptes <deloptes@gmail.com>
Date2018-08-19 00:10 +0200
Message-ID<wohzX-1Qi-3@gated-at.bofh.it>
In reply to#198994
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 100003, trying vers=3, prot=6
> mount.nfs: trying 192.168.0.129 prog 100003 vers 3 prot TCP port 2049
> 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
> 
> 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?

[toc] | [prev] | [next] | [standalone]

#199017

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-19 16:30 +0200
Message-ID<wowSm-2pb-5@gated-at.bofh.it>
In reply to#198997
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 100003, trying vers=3, prot=6
>> mount.nfs: trying 192.168.0.129 prog 100003 vers 3 prot TCP port 2049
>> 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
>>
>> 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.

[toc] | [prev] | [next] | [standalone]

#199019

Fromdeloptes <deloptes@gmail.com>
Date2018-08-19 17:00 +0200
Message-ID<woxln-2yj-3@gated-at.bofh.it>
In reply to#199017
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?

[toc] | [prev] | [next] | [standalone]

#199021

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-19 17:20 +0200
Message-ID<woxEJ-2U4-1@gated-at.bofh.it>
In reply to#199019
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.

[toc] | [prev] | [next] | [standalone]

#199026

FromReco <recoverym4n@gmail.com>
Date2018-08-19 20:00 +0200
Message-ID<woA9z-4ck-1@gated-at.bofh.it>
In reply to#199021
	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

[toc] | [prev] | [next] | [standalone]

#199055

Fromdeloptes <deloptes@gmail.com>
Date2018-08-20 08:40 +0200
Message-ID<woM14-2Rp-3@gated-at.bofh.it>
In reply to#199021
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

[toc] | [prev] | [next] | [standalone]

#199059 — Sid: rpcbind not starting (was NFSv3 mounting problem)

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-20 11:40 +0200
SubjectSid: rpcbind not starting (was NFSv3 mounting problem)
Message-ID<woOPg-4vN-13@gated-at.bofh.it>
In reply to#199055
Hi there,

When I try to start rpc.bimd I get the following error in the log:

Aug 20 11:20:56 Zeus daemon.err rpcbind[2924]: cannot get local address 
for udp: Servname not supported for ai_socktype
Aug 20 11:20:56 Zeus daemon.err rpcbind[2924]: cannot get local address 
for tcp: Servname not supported for ai_socktype
Aug 20 11:20:56 Zeus daemon.err rpcbind[2924]: cannot get local address 
for udp6: Servname not supported for ai_socktype
Aug 20 11:20:56 Zeus daemon.err rpcbind[2924]: cannot get local address 
for tcp6: Servname not supported for ai_socktype

It's surprising because DNS is working fine:

$ host Zeus
Zeus.olimp has address 192.168.0.130

# host www.debian.org
www.debian.org has address 5.153.231.4
www.debian.org has address 130.89.148.14
www.debian.org has IPv6 address 2001:41c8:1000:21::21:4
www.debian.org has IPv6 address 2001:67c:2564:a119::148:14

# cat /etc/hosts
127.0.0.1	localhost
::1		localhost ip6-localhost ip6-loopback
ff02::1		ip6-allnodes
ff02::2		ip6-allrouters
192.168.0.130	Zeus.olimp Zeus

PS. System was installed using debootstrap with variant=minbase, missing 
packages or configuration files??

-- 
Pozdrawiam
Grzesiek

Wysłane z kompa wolnego od wirusów Billa Gatesa.

[toc] | [prev] | [next] | [standalone]

#199063 — Re: Sid: NFSv3 mounting problem (again!)

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-20 12:50 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woPUZ-57e-5@gated-at.bofh.it>
In reply to#199055
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.

-- 
Pozdrawiam
Grzesiek

Wysłane z kompa wolnego od wirusów Billa Gatesa.

[toc] | [prev] | [next] | [standalone]

#199071 — Re: Sid: NFSv3 mounting problem (again!)

FromReco <recoverym4n@gmail.com>
Date2018-08-20 15:20 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woSga-6D1-7@gated-at.bofh.it>
In reply to#199063
	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).

Reco

[toc] | [prev] | [next] | [standalone]

#199078 — Re: Sid: NFSv3 mounting problem (again!)

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-20 16:10 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woT2x-78l-1@gated-at.bofh.it>
In reply to#199071
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?

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
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

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.


-- 
Pozdrawiam
Grzesiek

Wysłane z kompa wolnego od wirusów Billa Gatesa.

[toc] | [prev] | [next] | [standalone]

#199080 — Re: Sid: NFSv3 mounting problem (again!)

FromReco <recoverym4n@gmail.com>
Date2018-08-20 16:30 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woTlV-7eo-25@gated-at.bofh.it>
In reply to#199078
	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

[toc] | [prev] | [next] | [standalone]

#199082 — Re: Sid: NFSv3 mounting problem (again!)

FromMichael Stone <mstone@debian.org>
Date2018-08-20 16:40 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woTvz-7hj-1@gated-at.bofh.it>
In reply to#199080
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

[toc] | [prev] | [next] | [standalone]

#199087 — Re: Sid: NFSv3 mounting problem (again!)

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-20 17:20 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woU8j-7JF-23@gated-at.bofh.it>
In reply to#199082
The package netbase was missing.

Thanks for your help

-- 
Pozdrawiam
Grzesiek

Wysłane z kompa wolnego od wirusów Billa Gatesa.

[toc] | [prev] | [next] | [standalone]

#199079 — Re: Sid: NFSv3 mounting problem (again!)

FromMichael Stone <mstone@debian.org>
Date2018-08-20 16:30 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woTlV-7eo-17@gated-at.bofh.it>
In reply to#199063
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

[toc] | [prev] | [next] | [standalone]

#199109 — Re: Sid: NFSv3 mounting problem (again!)

Fromdeloptes <deloptes@gmail.com>
Date2018-08-20 22:30 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woYYh-27m-11@gated-at.bofh.it>
In reply to#199079
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

[toc] | [prev] | [next] | [standalone]

#199113 — Re: Sid: NFSv3 mounting problem (again!)

FromGrzegorz Sójka <pld@sojka.co>
Date2018-08-20 23:10 +0200
SubjectRe: Sid: NFSv3 mounting problem (again!)
Message-ID<woZAZ-2zu-5@gated-at.bofh.it>
In reply to#199109
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.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web