Sorry to be cross-posting, but does this bug ring any bells? I'm having
trouble seeing how the sunrpc server code could be at fault.
Cheers,
Trond
--- Begin Message ---
http://bugzilla.kernel.org/show_bug.cgi?id=5644
Summary: NFS v3 TCP 3-way handshake incorrect, iptables blocks
access
Kernel Version: 2.6.14
Status: NEW
Severity: blocking
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Most recent kernel where this bug did not occur:
Distribution: Can't remember, possibly FC2.
Hardware Environment:
Software Environment:
Problem Description:
Steps to reproduce:
1. Boot NFS v3 TCP client running iptables & mount NFS filesystem
2. Do a normal NFS client reboot & try mounting the same filesystem again
3. Experience intermittent failure to read superblock
The cause of this problem is NFS server's improper response to SYN packet sent
by the client. This occurs *after* successful client authorization, when the
client tries to open the connection (i.e. sends SYN to the server's nfs port) to
read the superblock. The server (sometimes) responds with a pure ACK without
the SYN bit set. This is blocked by iptables -- thus, mount fails with a "could
not read superblock" message.
Here is an excerpt from ethereal log:
3 0.021733 client SERVER TCP 800 > nfs [SYN]
Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=24095 TSER=0 WS=2
4 0.021846 SERVER client TCP nfs > 800 [ACK]
Seq=9138391 Ack=3580883479 Win=16022 Len=0 TSV=244936050 TSER=1149400
5 0.021864 client SERVER ICMP Destination
unreachable (Host administratively prohibited)
The above problem occurs with a very simple default+ssh iptables configuration.
Disabling iptables on the client makes the problem go away. Even with iptables
active, there is no problem when nfsd responds with a proper [SYN,ACK] instead
of just pure ACK (this happens intermittently after the client reboot).
Please fix nfsd so that it reliably responds to SYN packets with proper
[SYN,ACK] packets instead of just ACK packets. Apparently, nfsd state doesn't
get properly reset on client reboots. Other people have reported autofs
failures which may be related (e.g. on remounts).
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
