samba - Jun 2002 - Dangers of oplock break wait time

Hello,

the man page is quite explicit about not fiddling with the oplock break
wait time parameter unless one has understood the oplock code.

Is there an explanation for this that doesn't require one to be fully
read up on the SMB/CIFS protcols? :) What form of errors are we talking
about? Race conditions? How dangerous is it?

The thing is that we're having a lot of trouble related to the clients
missing the break requests (the word/excel documents-take-time-to-open
story). User's are getting seriously annoyed... so we have to do
something. But I thought I'd ask here before fiddling with the setting.

Thanks!

-- 
/ Peter Schuller, InfiDyne Technologies HB

PGP userID: 0xE9758B7D or 'Peter Schuller
<peter.schuller@infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org

On Tue, Jun 04, 2002 at 08:49:45PM +0200, Peter Schuller
wrote:
> Hello,
> 
> the man page is quite explicit about not fiddling with the oplock break
> wait time parameter unless one has understood the oplock code.
> 
> Is there an explanation for this that doesn't require one to be fully
> read up on the SMB/CIFS protcols? :) What form of errors are we talking
> about? Race conditions? How dangerous is it?
> 
> The thing is that we're having a lot of trouble related to the clients
> missing the break requests (the word/excel documents-take-time-to-open
> story). User's are getting seriously annoyed... so we have to do
> something. But I thought I'd ask here before fiddling with the setting.
What version of Samba. What clients ? What are the symptoms ?

Please give some details before we can help.

Thanks,

	Jeremy.

On Tue, Jun 04, 2002 at 10:06:45PM +0200, Peter Schuller
wrote:
> > What version of Samba. What clients ? What are the symptoms ?
> 
>> Various versions, including the latest stable release as of this
moment.
>> Win2k on the clients. Symptoms are long delays when opening Word/Excel
>> documents; along with (sometimes) error messages about file permissions
>> after the delay is over.
>I presume that is 2.2.4 ? Or are you testing the SAMBA_2_2 CVS ?
>If not, I'd recommend doing that as we're preparing for a 2.2.5
>release soon and extra feedback would be good.
> As far as I can tell I'm experiencing a known issue (I've seen
people
> talk about this in various mailinglist archives). I'm just wondering
> what dangerous side effects changing the oplock break wait time
> parameter might have - it's supposedly a possible fix. But the man page
> makes it sound pretty dangerous to fiddle with that particular option,
> so I am hesitant to try it.
>>No, not really a known issue with the Samba code as such. Many
>>people experience this problem when they're having networking
>>problems. Samba reports these problems in the log files, WinNT
>>and above just silently ignore them (the network goes a bit
>>slower when it happens) so people report it more to us.
>I've often been tempted to just supress the error messages
>so people don't report it :-) :-). That's the Microsoft solution
>here :-).
I have the same problem.
I am using Samba 2.2.4. I think problem is not to reports errors in log files.
Microsoft NT server doesn't slow file opening but Samba does! I thing it
would
be very good when this problem will be solved.

I think all people don't need Active directiory and other lesser features. 
But all of them need VERY STABLE AND ROBUST file server. 
If it will work as well as NT 4.0 it will be the greatest thing you would do.

-- 
with respection Andrey Feofilactovich.
e-mail: feo@ttn.ru, feo@feo.org.ru
ICQ: 28073807