| Summary: | nfs 4 mount doesn't work after kernel update | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dieter Schütze <dieter> |
| Component: | RPM Packages | Assignee: | Kernel and Drivers maintainers <kernel> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | nfs-utils-2.5.2-2.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Dieter Schütze
2022-03-09 08:57:16 CET
do you get any errors in dmesg when the mount fails ? 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 |