Skip to contentSkip to conversation

printk in xs_tcp_setup_socket needs rate limit ... and delay

Bug 13034 Trond Myklebust 3 participants 4 messages Apr 22, 2009 – Apr 23, 2009 5 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 200904222049.n3MKnxZi019947-jEpIWWs/[email protected]

#3 lore raw

(Switching to bugzilla email interface, and ccing linux-nfs)

Quoted 10 lines · On Wed, 2009-04-22 at 20:49 +0000, bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGk…

http://bugzilla.kernel.org/show_bug.cgi?id=13034

--- Comment #12 from Petr Vandrovec <[email protected]> 2009-04-22 20:49:58 --- Unfortunately I have no access to the server (they are some NetApp and EMC storage devices maintained by company IT).

Quoted 5 lines

It seems that they are all configured same way, so after mount they start timing out connections all at the same moment (after 10 minutes since mount, or something like that), and netstat above is captured when I run 'df' after connections moved from established to time_wait on client side. That TIME_WAIT disappear after 60 seconds, as expected.

So these connections are basically timing out because the systems are idle? (FYI: the NFS convention is that clients are supposed to close the TCP connection if it has been idle for 5 minutes, whereas the servers usually close it if the client has been idle for 6 minutes)...

A message that is not in the archive (sent off-list or not yet received): 1240433936.9197.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org

#5 lore raw
Quoted 20 lines · Trond Myklebust

(Switching to bugzilla email interface, and ccing linux-nfs)

Quoted 10 lines · On Wed, 2009-04-22 at 20:49 +0000, bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGk…

http://bugzilla.kernel.org/show_bug.cgi?id=13034

--- Comment #12 from Petr Vandrovec <[email protected]> 2009-04-22 20:49:58 --- Unfortunately I have no access to the server (they are some NetApp and EMC storage devices maintained by company IT).

Quoted 5 lines

It seems that they are all configured same way, so after mount they start timing out connections all at the same moment (after 10 minutes since mount, or something like that), and netstat above is captured when I run 'df' after connections moved from established to time_wait on client side. That TIME_WAIT disappear after 60 seconds, as expected.

Quoted 4 lines

So these connections are basically timing out because the systems are idle? (FYI: the NFS convention is that clients are supposed to close the TCP connection if it has been idle for 5 minutes, whereas the servers usually close it if the client has been idle for 6 minutes)...

Yes, they are timing out because system is idle. It seems that it behaves way it should - it is client who closes them, 5 minutes after I run 'df':

$ savedq=-1; df > /dev/null; while true; do q="`netstat -atn | grep 2049 | grep TIME_WAIT | wc -l`"; if [ "$q" != "$savedq" ]; then echo -n "$q "; date; savedq="$q"; fi; sleep 1; done
0 Wed Apr 22 14:59:10 PDT 2009
28 Wed Apr 22 15:04:10 PDT 2009
0 Wed Apr 22 15:05:08 PDT 2009

So as far as I can tell with patch everything works as expected.
Petr

#6 lore raw
Quoted 9 lines · Petr Vandrovec
Quoted 4 lines · Trond Myklebust

So these connections are basically timing out because the systems are idle? (FYI: the NFS convention is that clients are supposed to close the TCP connection if it has been idle for 5 minutes, whereas the servers usually close it if the client has been idle for 6 minutes)...

Yes, they are timing out because system is idle. It seems that it behaves way it should - it is client who closes them, 5 minutes after I run 'df':

Good! The 5minute idle timeout is the one case where we don't care about preserving the port number (because there are no outstanding NFS requests to replay to the server).

Jean, are you seeing the same behaviour (i.e. errors only on idle timeout), and is the fix working for you?

A message that is not in the archive (sent off-list or not yet received): 1240447977.9197.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org

#8 lore raw
Quoted 6 lines · Trond Myklebust

Good! The 5minute idle timeout is the one case where we don't care about preserving the port number (because there are no outstanding NFS requests to replay to the server).

Jean, are you seeing the same behaviour (i.e. errors only on idle timeout), and is the fix working for you?

I didn't hit the problem since I applied your patch, but that was only yesterday so it's too early to draw statistically valid conclusions.

It is highly possible that the bug was happening on idle timeout, I am the only user on this machine and I access the NFS mounts only from times to times.

Signature · 1 line
Jean Delvare