Red Hat Bugzilla – Bug 213351
NFSv4 regression between FC5 and FC6
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
After upgrading my NFS (v4) server from FC5 to FC6, I need to open up my
iptables firewall for ports other than 2049.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. On the nfs server, install FC5 with SELinux (targeted policy) and iptables
enabled. Permit TCP traffic to arrive via port 2049:
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT
Configure NFS to export a shared home directory space. /etc/exports:
(plus a bind mount in /etc/fstab for the /home -> /srv/nfs/home translation)
On the client (previously FC5, now FC6, same configuration both ways),
* -fstype=nfs4,rw,proto=tcp,port=2049 nfsserver:/home/&
/home /etc/auto.home --timeout=90
On both client and server, set up /etc/idmapd.conf to specify nfsnobody as the
user and group, and a common domain.
2. Watch as /home automounts wondefully on the client.
3. Upgrade server to FC6, watch as client can no longer automount directories in
Completely disabling the iptables firewall on the NFS server has corrected the
problem as a stop-gap measure. I haven't had a chance to spend much time
debugging this yet, as we just needed the machine back up and running; I'll try
to spend a bit of time with ethereal over the next few days seeing what
specifically isn't working.
I'm basing this approach on the documentation found here:
Would it be possible to post a bzip2 binary tethereal network trace
of the mount? Something similar to
tethereal -w /tmp/data.pcap host <server> ; bzip2 /tmp/data.pcap
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.