Bug 30142 - nfs 4 mount doesn't work after kernel update
Summary: nfs 4 mount doesn't work after kernel update
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-09 08:57 CET by Dieter Schütze
Modified: 2022-03-10 16:14 CET (History)
1 user (show)

See Also:
Source RPM: nfs-utils-2.5.2-2.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Dieter Schütze 2022-03-09 08:57:16 CET
Description of problem:
after upgrade to kernel
kernel-server-5.15.25-1.mga8-1-1.mga8.x86_64
nfs 4 mount doesn't work anymore only version 3 is working.

Version-Release number of selected component (if applicable):
Name        : nfs-utils
Epoch       : 1
Version     : 2.5.2
Release     : 2.mga8
Architecture: x86_64

How reproducible:


Steps to Reproduce:
1. boot with kernel-server-5.15.25-1.mga8-1-1
2. mount your nfs export with 
  /sbin/mount.nfs someserver.somedomain.de:/somedata /data -o rw,hard,tcp,rsize=8192,wsize=8192
or 
/sbin/mount.nfs someserver.somedomain.de:/somedata /data -o vers=4,rw,hard,tcp,rsize=8192,wsize=8192
or
/sbin/mount.nfs someserver.somedomain.de:/somedata /data -o nfsvers=4,rw,hard,tcp,rsize=8192,wsize=8192
or
/sbin/mount.nfs4 someserver.somedomain.de:/somedata /data -o rw,hard,tcp,rsize=8192,wsize=8192

doesn't work but 
/sbin/mount.nfs someserver.somedomain.de:/somedata /data -o vers=3,rw,hard,tcp,rsize=8192,wsize=8192
work

boot with kernel-server-5.15.23-1.mga8-1-1.mga8 will work
is anything changed with nfs 4 and the new kernel ?
sorry i don't know if this is a nfs 4 bug or a kernel bug.
Comment 1 Thomas Backlund 2022-03-09 15:50:54 CET
do you get any errors in dmesg when the mount fails ?
Comment 2 Dieter Schütze 2022-03-10 11:09:19 CET
Sorry, no errors neither with -v

/sbin/mount.nfs -v someserver.somedomain.de:/somedata /data
mount.nfs: timeout set for Thu Mar 10 11:03:21 2022
mount.nfs: trying text-based options 'vers=4.2,addr=xxx.xxx.x.xxx,clientaddr=xxx.xxx.x.xxx'

thats all i got.

But if you do this:

/sbin/mount.nfs -v -o vers=3 someserver.somedomain.de:/somedata /data
you got
mount.nfs: timeout set for Thu Mar 10 11:08:39 2022
mount.nfs: trying text-based options 'vers=3,addr=xxx.xxx.x.xxx'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying xxx.xxx.x.xxx prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying xxx.xxx.x.xxx prog 100005 vers 3 prot UDP port 30000

and it works, but only with version 3 since the new kernel.
Marja Van Waes 2022-03-10 16:14:39 CET

CC: (none) => marja11
Assignee: bugsquad => kernel


Note You need to log in before you can comment on or make changes to this bug.