Bug 1269042 - NFS V4 mounts of Solaris servers no longer work in FC22 RFS4_COMPOUND decode issue
Summary: NFS V4 mounts of Solaris servers no longer work in FC22 RFS4_COMPOUND decode...
Keywords:
Status: CLOSED DUPLICATE of bug 1226387
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: nfs-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-06 06:28 UTC by Ian Donaldson
Modified: 2015-10-06 14:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-06 14:53:54 UTC
Type: Bug


Attachments (Terms of Use)

Description Ian Donaldson 2015-10-06 06:28:49 UTC
Description of problem:

As of FC22 I can no longer mount my Solaris 10 NFS servers from Fedora
using the default mount options.

The Solaris NFS server complains of:

Oct  5 23:54:41 palms nfssrv: [ID 474727 kern.notice] NOTICE: Failed to decode arguments for NFS version 4 procedure RFS4_COMPOUND client hostname.domain (192.168.41.186)

This worked fine in FC21 and prior.


Version-Release number of selected component (if applicable):

kernel-4.1.6-100.fc21.x86_64 and prior works fine
kernel-4.1.6-201.fc22.x86_64 and later doesn't


How reproducible:

100%


Steps to Reproduce:
1.  palais# mount -r palms:/app/01/kick /x
2.
3.

Actual results:

mount.nfs: access denied by server while mounting palms:/app/01/kick


palms has this in the kernel log:

Oct  6 06:20:37 palms nfssrv: [ID 474727 kern.notice] NOTICE: Failed to decode arguments for NFS version 4 procedure RFS4_COMPOUND client palais.domain (192.168.41.191) 



Expected results:

success

Additional info:

Workaround is to use -vers=3 option, which works fine.

tcpdump of fc22 attempt shows the request that is failing has opcode EXCHANGE_ID

on fc21, the first op sent is SETCLIENTID, which gets a SETCLIENTID_CONFIRM 
response.

Comment 1 J. Bruce Fields 2015-10-06 14:53:54 UTC
See bz 1226387 for workarounds (or, if they don't work, reopen this bug so we can verify that this really is a dup).

Also, the bug is on the Solaris side, so if you have some way to lean on them to release the fix, please do.

*** This bug has been marked as a duplicate of bug 1226387 ***


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