FW: kernel oplocks 2.2.1a
Juer.Lee at raidtec.ie
Mon Sep 17 03:47:02 GMT 2001
I went through the source code (smbd/files.c) already, I got some
information about oplocks there, so my previous problem is not the
problem :) =20
But I still have a question:
If I disable the 'kernel oplocks' and enable 'oplocks', if I edit and
save a file on Samba client, can I get the changes right away ( using vi
to open the same file under Linux )? My results are all same when I
disable or enable 'kernel oplocks'.
Has anybody experience this problem?
>From: Juer Lee=20
>Sent: 17 September 2001 10:08
>To: Gerald Carter; ian j hart
>Cc: samba at lists.samba.org
>Subject: RE: kernel oplocks 2.2.1a
>I think there still are some problems with OPLOCK.
>I installed Samba2.2.1a on my SuseLinux7.1, my kernel is using 2.4.5
>I tried to disable/enable 'kernel oplocks' here.Two results I got:
>1.Enable 'kernel oplocks'
>In log message, I got 'set_file_lock: got kernel oplock on=20
>file ...' and
>'set_file_oplock: granted oplock on file ...',
>If I only edited that file and saved it on Samba client, I got
>'oplock_break: returning success for dev =3D ...' more
>2.Disable 'kernel oplocks'
>In log message, I got 'set_file_oplock: granted oplock on file ...'
>If I edit that file and saved it on Samba client, I couldn't get same
>message as section 1.
>What I cannot understand is in section 1, why I got 'oplock_break:
>returning success ...' even I haven't opened that same file under Linux
>box, or NFS client side ..
More information about the samba