[Samba] How is the Samba people stress testing Samba.

[jra at dp.samba.org]

On Thu, Nov 14, 2002 at 01:03:04PM +0100, Bo Jacobsen wrote:
> 
> A number of years ago I wrote a DOS program designed to run on multiple client hosts, stress and integrity testing 
> a shared file on a Windows NT 3.51 file servers. In principal the program continuously locks a random part of the testfile
> (on the server), reads the data and test the data for errors, then writes a new testpattern and removes the lock.
> 
> Lately I have tried it on different Samba servers with very different results.
> 
> When I tried to test a Samba 2.2.5 server (SuSE 8.0 Kernel 2.4.19, oplocks disabled, AMD XP1900+, 256MB) with two Win98 
> clients, the clients could never run more then maybe 6 hours before one of the clients completely lost contact 
> with the Samba server and had to be rebooted. Two bytes in the 250MB testfile was corrupted. If only one client was run, the 
> client still lost contact to the server and had to be rebooted.
> 
> When the same test was run on a Samba 2.2.6 server (SuSE 8.1 Kernel 2.4.19, oplocks disabled, AMD XP1900+, 256MB, and
> the same Win98 clients), the clients never lost contact to the server, but I have not yet been able to run the test more the maybe 48 
> hours without a corruption of the testfile.

Can you send me this test please so I can run it against Samba ?
amba is stress tested in many different ways. Whenever we discover a
new locking problem we add it to the smbtorture test suite.

Jeremy.