Gentoo Archives: gentoo-user

From: walt <w41ter@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: New wireless adapter breaks nfs exports
Date: Thu, 16 Oct 2014 23:23:45
Message-Id: m1pk0v$am2$1@ger.gmane.org
In Reply to: Re: [gentoo-user] Re: New wireless adapter breaks nfs exports by Tom H
1 On 10/15/2014 12:57 PM, Tom H wrote:
2 > On Tue, Oct 7, 2014 at 7:39 PM, walt <w41ter@×××××.com> wrote:
3 >> On 10/05/2014 08:31 PM, Tom H wrote:
4 >>> On Sat, Oct 4, 2014 at 2:52 PM, walt <w41ter@×××××.com> wrote:
5 >>>>
6 >>>> This machine (my nfsv3 file server) just got a new wireless adapter, which
7 >>>> works fine for everything except serving files :(
8 >>>>
9 >>>> mount.nfs: requested NFS version or transport protocol is not supported
10 >>>>
11 >>>> google shows me lots about slow nfs connections over wireless but nothing
12 >>>> about non-support. I'm using only nfs3 ATM because I've had so many problems
13 >>>> with nfs4 in the past. I thought I'd ask here if nfs4 might fix the problem
14 >>>> before changing everything.
15 >>>
16 >>> NFS works over wifi.
17 >>>
18 >>> Have you tried mounting with "-v" and/or "-o nfsvers=3"?
19 >>
20 >> Yes, about 30 seconds ago :)
21 >>
22 >> #mount -v -t nfs -o nfsvers=3 a6://usr/portage /mnt
23 >> mount.nfs: timeout set for Tue Oct 7 16:35:39 2014
24 >> mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.75'
25 >> mount.nfs: prog 100003, trying vers=3, prot=6
26 >> mount.nfs: trying 192.168.1.75 prog 100003 vers 3 prot TCP port 2049
27 >> mount.nfs: prog 100005, trying vers=3, prot=17
28 >> mount.nfs: trying 192.168.1.75 prog 100005 vers 3 prot UDP port 36168
29 >> mount.nfs: mount(2): Protocol not supported
30 >> mount.nfs: Protocol not supported
31 >>
32 >> I have nfsv4 working correctly so the urgency is gone but I'm still
33 >> curious if nfsv3 really should work over wifi as well as nfsv4.
34 >
35 > Both nfsv3 and nfsv4 work over wifi.
36 >
37 > Do both the client's and the server's kernels have nfsv3 enabled?
38 >
39 > From the output above I'd check the client's kernel config.
40
41 The problem turned out to be incorrect nfs useflags, not kernel config, and
42 nfsv3 is working now, thanks much.