On 9/15/07, Bill Fink <[EMAIL PROTECTED]> wrote: > Would it be worth a shot to try disabling the receiver hardware > checksumming (ethtool -K ethX rx off)? I just did, unfortunately it doesn't seem to change much. In the various attempts, however, I seem to have improved something, maybe. As I mentioned, the machine work as both a gateway and a samba server. It seems that as long as the one samba operation is the only activity that goes on between a specific client and the samba server, at least I do not get timeouts. I have to investigate further on file corruption, but the timeout doesn't occur. As soon as I try to perform a second samba operation - even on read - or I generate singificant net traffic, the samba connection times out. I have to assume that the added load is just enough to overload the link. The other curious fact is that occasionally the writing effectively pauses for 1-2s. It then resumes, with no ill effect. I have to assume that when the timeouts occur, the same thing happens for a sufficiently long period of time and the connection drops. For further reference, in case any of it is relevant, the samba shares are ext3 filesystems residing on a SATA based RAID5 (md) array. I include this because at a certain point I started suspecting the filesystem before the network, but it doesn't make too much sense.
LF - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html