oplock problem

[Robert Schott]

> I was wondering if you had solved your data corruption
> problem in samba?  I seem to have a similar problem and have
> not found a solution in the samba mailing list or archives.


Hello Rick,

for several days there occured no more fault (exactly since last friday
morning).

But I am still not save because the app manufacturer is not willing to
provide a torture test that uses his DB and his libs. And we could not force
the failure in a predictable way. So it is *impossible* to me to say:
We solved it - yes.

The only thing I can say is - the corruption did not occur again - until
now.
I am the consultant there and suggested to do at least daily backups.

The settings I changed in /etc/smb.conf (we are using SMB 2.0.6 kernel
2.2.16):

   strict locking = yes
   oplocks = False
   oplock break wait time = 20
   oplock contention limit = 4

This is placed in general section of smb. I wanted to be safe that smb
is configured this way. I don't want to make experiments on a live system.

I did some tests from a single workstation copying about 100 MB to smb
server
and found no influence in performance. That params seem really to hit the
locking. So it will switch on *conservative* settings (again - I still guess
if I am wrong).

There is a file speed.txt in /usr/doc/packages/samba that explains some but
not all. And I must admit that I am not that perfect when it comes to
reading
C sources implementing SMB.
Ok maybe I should try it - but the time factor - you know... ;-)

I was some disappointed that nobody of the specialists here in the list
could
help me out. I assumed that there would be at least one who could explain me
if I am right in my assumptions what these params do.

I hope the things above may give hints and do help. Maybe one of the
mentioned
above finds now it is worth to tell us if I am right? Maybe you could e-mail
me your experiences?


Robert



Robert Schott
roottec.com


-----------------------------------------------
security is an illusion
(Bombolo)