On Fri, 29 Apr 2011 08:06:49 -0700
Mike Dillinger <[email protected]> wrote:
> > What sort of host is "peart" here? WinXP?
>
> peart is WinXP 64 SP2, and the Linux machine is running Debian wheezy.
> The XP firewall is off and the internet security firewall (Kaspersky
> Internet Security) is off.
>
> The firewall thing doesn't make sense, or else it seems to me that I
> wouldn't be able to view the remote data. The remote side *always*
> works when I view the file share. I have even tried during viewing the
> data multiple times during the 5 minute interval where syslog states the
> host is not responding. I will capture Wireshark traces though if there
> aren't any other suggestions.
>
I might see the problem here. I think there's a bug in 2.6.38ish
kernels that's fixed by commit fd88ce93:
@@ -421,7 +420,7 @@ cifs_demultiplex_thread(struct TCP_Server_Info *server)
pdu_length = 4; /* enough to get RFC1001 header */
incomplete_rcv:
- if (echo_retries > 0 &&
+ if (echo_retries > 0 && server->tcpStatus == CifsGood &&
time_after(jiffies, server->lstrp +
(echo_retries * SMB_ECHO_INTERVAL))) {
cERROR(1, "Server %s has not responded in %d seconds. "
...if the server decides to disconnect the client for some reason, then
the above delta will prevent that error message from popping
unnecessarily. Steve, I think that patch should probably go to -stable
as well.
--
Jeff Layton <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
