We regularly do large file Copy-Paste tests with files between 30G and 60G. We have yet to see a problem.
Tricord's market is Network Attached Storage, and our product is a file system. Samba is the main interface between our market and our file system. We spend a lot of time making sure the data that goes through Samba and into our file system comes back out in the same shape it went in. We have a whole department devoted to that purpose. Trust me, we'd notice if there was a problem. :)
-----Original Message-----
From: Jay Ts [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 23, 2002 2:25 PM
To: Esh, Andrew
Cc: 'John H Terpstra'; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Mathew
McKernan; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Samba] Re: How Samba let us down
Esh, Andrew wrote:
> Here at Tricord, we run Samba through some pretty intense tests, as well.
> Since we are a file system producer, we focus on corruption bugs. We haven't
> found any in Samba,
Since I've been curious about this anyway, I might go ahead and check:
Do you (And J. Terpstra, and others) test sending really huge files,
such as 700 MB ISO CD-ROM images or bigger, across the net, and then
run a cmp on them, going in each direction. That is:
1. Start with a reference huge file on Windows, known to match an
existing file on Unix, then copy it over through Samba and
do a cmp on them? About how many times is this done in your
tests? More than a few hundred?
2. Also run the test the other way, and compare the copies on
the Windows side?
> I'm not trying to chime in here, but if there was
> the kind of bug someone would notice within the first few hours of use, we'd
> have hit it hundreds of times already, just in our testing this week. We've
> been testing like this for more than two years.
That's what I thought, too. My take on it was that it was related to
Samba, but not necessarily caused by it. In any case, it was all more
than a year ago, and isn't an issue to me at all.
Jay Ts
