samba - Nov 2002 - Fw: How is the Samba people stress testing Samba.

> 
> I'm in the "testing and proof" stage of converting from
Windows NT 4 to
> Linux/SAMBA and I'm very interested in any "stress testing"
that you (or
> anyone else) could point me to.  If you get your DOS Program working,
> would you mind sharing it?
> 
> The other thing that interests me in your post is the corruption of a
> Paradox database.  I'm also trying to convert of a buddy of mine to the
> SAMBA scene at his wife's Veterinarian clinic.  They use a Paradox
> database for just about ALL of their record keeping and billing.  Last
> week we setup a test server with Red Hat 8 and Samba 2.2.5 and got nearly
> 4 times the performance over Windows 2000 running the database on the same
> hardware.  The problem is that they *pound* on the database 8-12 hours a
> day 6 days a week.  I I'm looking at corruption 4-48 into production,
I'm
> not going to have a buddy for very long....  Have been able to learn
> anything more on this front?
> 
> I'm going back out the clinic tonight to do some more testing and
I'll
> report anything that happens while I'm there.
> 
> Kevin
> 
> 
I understand your worry. I'm right now considering going back to Win98 as we
have to figure out, where exactly the problem lies. I have tried with different
kernels
2.4.16 through 2.4.19 but have not yet been able to solve this issue.

If I were you I would be very careful about moving the database as things are
right now. I suggest that you at least run a very lengthy concurrent paradox
stress
test (from multiply workstations) before moving.


You could have a copy of my DOS testprogram, but it's in Danish and I have
never
translated it to English.
The program was written as we had problems with database corruption when moving
a
financial database from Netware to Windows NT3.5.


The reason I posted the original message is that I'm really interested in
knowing how
Samba has been stress tested. 


Bo
-------------- next part --------------
HTML attachment scrubbed and removed

On Thu, Nov 14, 2002 at 04:38:03PM +0100, Bo Jacobsen
wrote:
> 
> The reason I posted the original message is that I'm really interested
> in knowing how Samba has been stress tested. 
This came up recently in the thread "How Samba let us down". Members
of the Samba Team responded with some impressive facts and figures.

Try here:
http://marc.theaimsgroup.com/?l=samba&w=2&r=1&s=how+samba+let+us+down&q=b

In summary, Samba is tested with extreme thoroughness before a production
release is put up on the FTP site. Many of the corruption
problems are caused by clients and bad network hardware. Definitely
set oplocks = off when using Samba with large or flat database files,
or use the veto oplock files parameter to turn off oplocks for just the
database files.

If you are experiencing file corruption that is actually caused by
Samba, then we'd all like to know exactly how to reproduce the problem.
The Samba Team takes this kind of thing very seriously ... but the
thing is, it's usually a client or network hardware problem.

Jay Ts