On Wed, 19 Sep 2007, L F wrote:
> Well,
> the issue seems to have gone away as of this morning, but I am
> somewhat unsure as to why.
> Placement of some things were modified so as to allow shorter cables.
> Now there are 3' CAT6 cables everywhere except for the 15' cable
> between the two switches. All the cables are new, high quality
> 'tested' cables from a company nearby.
> The server is now running 2.6.22.6 with the 7.6.5 e1000 driver from
> intel.com and samba 3.0.26-1 ... and it seems to work. Samba will not
> disconnect, even with all 8 clients running unreasonable read/write
> loads and CRC and MD5 checksums of the transferred files all match.
> The issue therefore seems to have gone away, but the reason why still
> escapes me. I cannot believe that CAT5 cables under 10' in length were
> causing it, because if that were the case
> 1) it would've shown itself, I presume, from the beginning
> 2) I could name dozens of different locations which would be having
> the same problems
> Samba 3.0.25 was definitely part of the problem and I sent a nice
> nastygram to the debian maintainers, because -testing is not
> -unstable, last I checked.
> As to samba having any sort of data integrity capability, to the best
> of my knowledge that has never been the case.
> To answer further questions: I checked for file integrity with
> CRC/CRC32/MD5 checksum utilities. They used to fail fairly
> consistently, they have been fine all this morning.
By any chance did you happen to power cycle some equipment in this
process that you didn't previously power cycle during earlier testing
and debugging? If so, perhaps that hardware had somehow gotten into
a funky state, and the power cycling might have cleared it up.
Just a thought.
-Bill
-
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
