Red Hat Bugzilla – Bug 218330
NFS with Kereberos completely broken on 2.6.18 and 2.6.19
Last modified: 2014-06-18 03:35:42 EDT
Description of problem:
NFS with Kerberos is completely broken since 2.6.18 due to a bug in the NFS
client code. An NFS client can no longer mount more than one NFS+KRB5 volume
from a single server. If you try to do so, you will get the error:
mount.nfs: File exists
from the mount program.
Version-Release number of selected component (if applicable):
Any kernel 2.6.18 and up.
This is 100% reproducible.
Steps to Reproduce:
1. Export two share using either NFSv4 or NFSv3 with the sec=krb5 option.
2. Mount one on the client.
3. Try to mount the other on the client.
You will now see the "File exists" error.
The mount should complete without incident.
This is an urgent problem that needs attention. The problem has been isolated.
See the following mailing list post:
And a patch has been proposed:
The patch works on 2.6.19 vanilla kernel (it does not apply cleanly on 2.6.18
and a simple readjustment of the patch does not work) as verified by both the
maintainer and myself.
Here's what I suggest: add the patch ASAP to the Fedora SRPM of kernel 2.6.19
and propagate this new kernel release to FC5 updates as well as FC6 updates.
This of course affects FC6. I suspect the beta of RHEL5 (although I can't check
at the moment) will have the same problem as well.
Yes, that's why I listed that the kernel SRPM include the patch and be released
in FC5 and FC6. That's also a good point about RHEL 5. Can someone move this
forward soon? Thanks!
I haven't heard anything back from anyone about this bug. I've been fighting
this problem for nearly two months and it's getting very frustrating, especially
since 2.6.17 has now been removed from the fc5 updates repository!!! This has
caused considerable inconvenience for our company since we use NFSv3+Kerberos
and need to have machines installed with a properly working kernel.
I am unable to increase the urgency field past "Urgent", so can someone help me out.
Cloning the bug to FC6 and possibly RHEL5b2 might help there. It usually takes
some time before that bug is assigned to anyone but lack of activity in bugzilla
doesn't necessarily mean that someone isn't looking at it right now.
Sorry it's taken so long to get to this bug. It sounds like there was an
upstream fix to this problem in 2.6.20 or so? In any case, I believe this bug to
fixed at this point. Please reopen it if you're still experiencing this problem
with the most current kernel from F7 or later releases.