On Mon, 27 Apr 2020 17:23:39 +0200, Markus Schaaf via arch-general
wrote:
> Am 27.04.20 um 16:51 schrieb Hauke Fath:
>
>> NFSV4: Unsupported transport protocol udp
>
> Have you tried vers=3 in mount options?
Thanks for the reply. I'll give some of the configuration.
(1) autofs config is distributed through nis:
% grep '^[/]' /etc/automount/auto.master
/home auto.home
-udp,nfsvers=3,resvport,nolock,noacl,grpid,retrans=5,rsize=16384,wsize=16384,rw,hard,intr
/misc auto.misc
-udp,nfsvers=3,resvport,grpid,local_lock=none,retrans=5,rw,hard,intr
%
(2) The client autofs setup:
% grep -v '^#' /etc/autofs/autofs.conf
[ autofs ]
timeout = 300
browse_mode = no
[ amd ]
dismount_interval = 300
%
This setup has worked for years, and continues to work after rolling
back to the 2020-03-09 state. There is no nfsv4 anywhere in sight: The
server setup disables it, and wherever I can specify nfsv3 on the
client, I have.
>From the journal:
[...]
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de automount[567]:
attempting to mount entry /home/XXX
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered named UNIX socket transport module.
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered udp transport module.
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered tcp transport module.
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered tcp NFSv4.1 backchannel transport module.
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: FS-Cache:
Netfs 'nfs' registered for caching
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: ***
VALIDATE nfs ***
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: ***
VALIDATE nfs4 ***
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de kernel: NFSv4:
Unsupported transport protocol udp
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de automount[567]: >>
mount.nfs: an incorrect mount option was specified
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de automount[567]:
mount(nfs): nfs: mount failure NFSSERVER:/u/homes/XXX on /home/XXX
Apr 27 16:27:20 Ankogel.nt.e-technik.tu-darmstadt.de automount[567]:
failed to mount /home/XXX
[...]
AFAICS, the kernel has no business "validating" an nfsv4 mount, because
none has been asked for.
The 2020-03-09 setup:
[...]
Apr 27 18:57:11 Ankogel.nt.e-technik.tu-darmstadt.de automount[546]:
attempting to mount entry /home/XXX
Apr 27 18:57:11 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered named UNIX socket transport module.
Apr 27 18:57:11 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered udp transport module.
Apr 27 18:57:11 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered tcp transport module.
Apr 27 18:57:11 Ankogel.nt.e-technik.tu-darmstadt.de kernel: RPC:
Registered tcp NFSv4.1 backchannel transport module.
Apr 27 18:57:11 Ankogel.nt.e-technik.tu-darmstadt.de kernel: FS-Cache:
Netfs 'nfs' registered for caching
Apr 27 18:57:11 Ankogel.nt.e-technik.tu-darmstadt.de automount[546]:
mounted /home/XXX
[...]
>From what I can see, either I missed some obscure new configuration
that overrides the automounter's explicit mount options. Or, I hit a
kernel bug.
Cheerio,
Hauke
--
The ASCII Ribbon Campaign Hauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
Respect for open standards Ruf +49-6151-16-21344
