Bug 1468044 - kernel: NFS: nfs4_discover_server_trunking unhandled error -22. Exiting with error EIO
kernel: NFS: nfs4_discover_server_trunking unhandled error -22. Exiting with ...
Status: NEW
Product: Fedora
Classification: Fedora
Component: nfs-utils (Show other bugs)
25
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Steve Dickson
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-05 17:14 EDT by Tom Bouwman
Modified: 2017-07-12 03:55 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tom Bouwman 2017-07-05 17:14:41 EDT
Description of problem:
kernel: NFS: nfs4_discover_server_trunking unhandled error -22. Exiting with error EIO
when trying to mount a NFS-device with Defaultvers=4 in the [ Server "hostname" ] section of /etc/nfsmount.conf

Version-Release number of selected component (if applicable):
nfs-utils-1:2.1.1-5.rc4.fc25.x86_64

How reproducible:
nfs-utils was upgraded from nfs-utils-1:2.1.1-5.rc3.fc25.x86_64 to nfs-utils-1:2.1.1-5.rc4.fc25.x86_64 on June 30 2017

Steps to Reproduce:
1. upgrade nfs-utils-1:2.1.1-5.rc3.fc25.x86_64 to nfs-utils-1:2.1.1-5.rc4.fc25.x86_64
2. try to mount a NFS-device with Defaultvers=4
3.

Actual results:
kernel: NFS: nfs4_discover_server_trunking unhandled error -22. Exiting with error EIO

Expected results:
A mounted NFS-device

Additional info:
Changing Defaultvers=4 in the [ Server "hostname" ] section of /etc/nfsmount.conf to Defaultvers=3, will do the mount. But that results in errors when trying to open LibreOffice documents.
Comment 1 Tom Bouwman 2017-07-05 17:48:08 EDT
I downgraded to nfs-uils 1.3.4-1.rc2.fc25.
I downloaded that version from the base release of fc25.

Tis appears to be working for the moment.
Used dnf versionlock to make sure that I does not get updated to rc4.
Comment 2 J. Bruce Fields 2017-07-06 16:21:38 EDT
(In reply to Tom Bouwman from comment #1)
> I downgraded to nfs-uils 1.3.4-1.rc2.fc25.
> I downloaded that version from the base release of fc25.
> 
> Tis appears to be working for the moment.
> Used dnf versionlock to make sure that I does not get updated to rc4.

I assume you're talking about the NFS client here?  (What kind of NFS server are you using?)

Watching network traffic between client and server in wireshark might be enlightening.

> But that results in errors when trying to open LibreOffice documents.

Weird, what errors?  Off hand I can't think why an application would work over NFSv4 but not over NFSv3.  Maybe it's trying to do file locking and that's not working in the v3 case for some reason?
Comment 3 Tom Bouwman 2017-07-07 03:21:17 EDT
Yes, I downgraded the nfs-utils on the NFS-client. My NFS-server is Fedora 14.

LibreOffice will open the documents only as read-only, saying it is locked by me.
Comment 4 Nils 2017-07-11 04:26:28 EDT
Had the same issue with version nfs-utils-1:2.1.1-5.rc4.fc25.x86_64.

In fstab i had "vers=4.0" and got the same error. NFS-Mouting didn't work on reboot. Changing it to "vers=4.1" fixed this issue for me.
Comment 5 Steve Dickson 2017-07-11 11:35:41 EDT
(In reply to Tom Bouwman from comment #3)
> Yes, I downgraded the nfs-utils on the NFS-client. My NFS-server is Fedora
> 14.
What 'Defaultvers=4' means is use v4 with the default minor version.
So what's happening the 4.2 is tried. When the server does not support
that, which is the case with fc14, it should return 
NFSERR_MINOR_VERS_MISMATCH. Maybe f14 is mishandling that negation

Defaultvers=4.0 should work. 
 
> 
> LibreOffice will open the documents only as read-only, saying it is locked
> by me.
I have now idea what's going on here... Is the filesystem mount rw?
Comment 6 Steve Dickson 2017-07-11 11:43:13 EDT
(In reply to Nils from comment #4)
> Had the same issue with version nfs-utils-1:2.1.1-5.rc4.fc25.x86_64.
> 
> In fstab i had "vers=4.0" and got the same error. NFS-Mouting didn't work on
> reboot. Changing it to "vers=4.1" fixed this issue for me.

What is the server on this one?
Comment 7 J. Bruce Fields 2017-07-11 13:20:11 EDT
(In reply to Steve Dickson from comment #5)
> (In reply to Tom Bouwman from comment #3)
> > LibreOffice will open the documents only as read-only, saying it is locked
> > by me.
> I have now idea what's going on here... Is the filesystem mount rw?

My guess is it tried to get a file lock and fcntl returned ENOLCK--an strace could help confirm that.  I think there was an rpcbind bug that could cause that?
Comment 8 Nils 2017-07-12 03:23:34 EDT
(In reply to Nils from comment #4)
> Had the same issue with version nfs-utils-1:2.1.1-5.rc4.fc25.x86_64.
> 
> In fstab i had "vers=4.0" and got the same error. NFS-Mouting didn't work on
> reboot. Changing it to "vers=4.1" fixed this issue for me.

Sorry, it only worked for the next reboot. Now i got the same message again.
Comment 9 Tom Bouwman 2017-07-12 03:55:09 EDT
(In reply to Steve Dickson from comment #5)
> (In reply to Tom Bouwman from comment #3)
> > Yes, I downgraded the nfs-utils on the NFS-client. My NFS-server is Fedora
> > 14.
> What 'Defaultvers=4' means is use v4 with the default minor version.
> So what's happening the 4.2 is tried. When the server does not support
> that, which is the case with fc14, it should return 
> NFSERR_MINOR_VERS_MISMATCH. Maybe f14 is mishandling that negation
> 
> Defaultvers=4.0 should work. 
>  
> > 
> > LibreOffice will open the documents only as read-only, saying it is locked
> > by me.
> I have now idea what's going on here... Is the filesystem mount rw?

During one of my upgrades fc21-->fc22 or fc22-->fc23 or fc23-->fc24 I had to add Defaultvers=4 in /etc/nfsmount.conf, because my NFS-server is fc14.

The filesystem is mounted rw.

Output of the mount command:
jupiter:/data/home on /mnt/jupiter/data/home type nfs4 (rw,relatime,vers=4.0,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.34,local_lock=none,addr=192.168.1.31)

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