[Samba] Oplock problem
Boogerman
experiencing. Today, when I deleted the file pspbrwse.jbf, I experienced the
problem, and I immediately went to the logs. Here's what I got:
[2003/05/06 11:06:50, 0] smbd/oplock.c:oplock_break(796)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file htdocs/pictures/pspbrwse.jbf (dev = 901,
inode = 11009, file_id = 2654).
[2003/05/06 11:06:50, 0] smbd/oplock.c:oplock_break(868)
oplock_break: client failure in oplock break in file
htdocs/pictures/pspbrwse.jbf
[2003/05/06 11:06:51, 0] smbd/reply.c:reply_lockingX(4626)
reply_lockingX: Error : oplock break from client for fnum = 11670 and no
oplock granted on this file (htdocs/pictures/pspbrwse.jbf).
Ok, by the looks of it (anyone whith better knowledge of the SMB protocol
and Samba internals, please correct me if I'm wrong), I would say the client
requested an oplock on pspbrowse.jbf, then when it deleted it, the server
issued an oplock break request wich was unanswered by the client... so after
30 seconds of receiving no answer, the server timed out the operation. So,
there appears to be a bug in the client (not responding to the oplock break
request). I must mention that the client is a Windows XP SP1.
During those 30 seconds, the server didn't seem to respond to any request
made by the client (that's why the client locked up). Other clients worked
fine during those 30 seconds.
Well, I have described what I think is the issue as best as I could...
Apparently, It has nothing to do with WebDAV (I have already disabled it,
and it didn't fix anything).
Any suggestions?
Regards,
Gaston Dassieu Blanchet
boog...@interar.com.ar
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Jon Foster
I have yet to see a version of windows that can handle the "oplock" properly. It doesn't seem to even work right going from a windows work station to a windows server (one of the reasons I went from an NT server to Linux/Samba). I have always just turned off "oplocks" with "oplocks=no" in the "[global]" section of the "smb.conf". I'll be watching this thread to see if someone else has a better answer :-).
-Jon
On Tue, 6 May 2003 12:33:08 -0300
"Boogerman" <boog...@interar.com.ar> wrote:
> So, there appears to be a bug in the client (not responding to the oplock
> break request). I must mention that the client is a Windows XP SP1.
-----
Jon Foster
JF Possibilites
j...@jfpossibilities.com
Making computers work for you, instead of you working for your computers!
John H Terpstra
There is a new chapter in the Samba-HOWTO-Collection.pdf (a work in
progress) on locking. I'd appreciate your feedback on it and any
suggestions you might make. Here is the URL for the in development
version:
http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf
- John T.
--
John H Terpstra
Email: j...@samba.org
Boogerman
read-only files). Even with good clients (bug free), this could still fail
in case of a network error or something.
I guess I will just disable oplocks (or else this will trouble my sleep).
I still wonder why M$ designed this mechanism if it was to bring such
problems. Furthermore, is there any way to implement failproof oplocks (not
over SMB, but in general)?
Regards,
Gaston Dassieu Blanchet
boog...@interar.com.ar
----- Original Message -----
From: "John H Terpstra" <j...@samba.org>
To: "Boogerman" <boog...@interar.com.ar>
Sent: Tuesday, May 06, 2003 11:05 PM
Subject: Re: [Samba] Oplock problem
> On Tue, 6 May 2003, Boogerman wrote:
>
> > John
> >
> > Yes, I had already read the Locking chapter of the HOWTO-Collection
(I've
> > been crawling trought the list archives seeking for a solution to my
problem
> > when I found a link to it).
> >
> > I found it very instructive. It describes very well what the types of
> > oplocks are and what they are used for. It's a real good work.
> >
> > I only have one question. At a certain point, you mention a "risk of
data
> > corruption". Can you explain me where this risk comes from? Is there a
flaw
> > in the oplock request/break mechanism?
>
> Clients can fail to see oplock break requests, the server then times out
> the lock, another client writes to the file, then the original client
> write to it also. Bang! Bad data!
>
> - John T.
>
> >
> > Regards,
> >
> > Gaston Dassieu Blanchet
> > boog...@interar.com.ar
> >
Rashkae
would like to point out that, unlike Windows, Samba allows fine grained
control over what shares, dicrectories files or groups of files to allow
or disallow oplocks on. If I were to take the time to performance tune a
Samba server, I would only disable opolocks on those files that are likely
to be opened read-write by multiple users. (Database files, as the most
comon example.) Performance improvements from oplocks are impressive,
and the load on the network is greatly reduced.
Boogerman
lockup problem. This is a very ugly problem. The office network users' keep
yelling at me because of that!
Is there a way to fix this? (I know, I know, it's a client bug, but is there
a server workaround for it?)
Regards,
Gaston Dassieu Blanchet
boog...@interar.com.ar
----- Original Message -----
From: "Rashkae" <ras...@tigershaunt.com>
To: "Boogerman" <boog...@interar.com.ar>
Cc: "John H Terpstra" <j...@samba.org>; <sa...@lists.samba.org>
Sent: Wednesday, May 07, 2003 10:21 AM
Subject: Re: [Samba] Oplock problem
> I've never been comfortable with the concept of oplocks myself. But I
> would like to point out that, unlike Windows, Samba allows fine grained
> control over what shares, dicrectories files or groups of files to allow
> or disallow oplocks on. If I were to take the time to performance tune a
> Samba server, I would only disable opolocks on those files that are likely
> to be opened read-write by multiple users. (Database files, as the most
> comon example.) Performance improvements from oplocks are impressive,
> and the load on the network is greatly reduced.
Giulio Orsero
wrote:
>Yes, you're probably right. Still, we haven't solved that annoying 30 second
>lockup problem. This is a very ugly problem. The office network users' keep
>yelling at me because of that!
>
>Is there a way to fix this? (I know, I know, it's a client bug, but is there
>a server workaround for it?)
Just use
oplocks = no
or are you saying that you did it and you still get the 30 sec delay?
"oplocks = no" is the first thing to do after installing samba, unless your
job is doing benchmarks :-)
Boogerman
an example) was delete one file (pspbrowse.jbf). Immediately after, the
service locked up (for that client only) for about 30 seconds. When I
checked the logs, I got this:
[2003/05/06 11:06:50, 0] smbd/oplock.c:oplock_break(796)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file htdocs/pictures/pspbrwse.jbf (dev = 901,
inode = 11009, file_id = 2654).
[2003/05/06 11:06:50, 0] smbd/oplock.c:oplock_break(868)
oplock_break: client failure in oplock break in file
htdocs/pictures/pspbrwse.jbf
[2003/05/06 11:06:51, 0] smbd/reply.c:reply_lockingX(4626)
reply_lockingX: Error : oplock break from client for fnum = 11670 and no
oplock granted on this file (htdocs/pictures/pspbrwse.jbf).
I think the client is to be blamed (for not responding to the oplock break
request). I wonder if there is a way for Samba to reduce the timeout, retry
sending the oplock break request, or at least keep providing service while
waiting for the client reply...
Gaston Dassieu Blanchet
boog...@interar.com.ar
----- Original Message -----
From: "Rashkae" <ras...@tigershaunt.com>
To: "Boogerman" <boog...@interar.com.ar>
Cc: "Rashkae" <ras...@tigershaunt.com>; "John H Terpstra" <j...@samba.org>;
<sa...@lists.samba.org>
Sent: Thursday, May 08, 2003 10:37 AM
Subject: Re: [Samba] Oplock problem
> In this case, I would disable oplocks. My earlier post was only to point
> out that with Samba, you can disable oplocks selectively on files that
> might cause problems. Such as database files, or whatever strange
> activity you're seeign here. (Note: Are there multiple computers
> accessing the file when you get this 30 second lockup? If this is a
> client locking itself up, there might be a protocol quirk in Samba causing
> it.)
>
> On Thu, 8 May 2003, Boogerman wrote:
>
> Yes, you're probably right. Still, we haven't solved that annoying 30
second
> lockup problem. This is a very ugly problem. The office network users'
keep
> yelling at me because of that!
>
> Is there a way to fix this? (I know, I know, it's a client bug, but is
there
> a server workaround for it?)
>
> Regards,
>
> Gaston Dassieu Blanchet
> boog...@interar.com.ar
>
> ----- Original Message -----
> From: "Rashkae" <ras...@tigershaunt.com>
> To: "Boogerman" <boog...@interar.com.ar>
> Cc: "John H Terpstra" <j...@samba.org>; <sa...@lists.samba.org>
> Sent: Wednesday, May 07, 2003 10:21 AM
> Subject: Re: [Samba] Oplock problem
>
>
> > I've never been comfortable with the concept of oplocks myself. But I
> > would like to point out that, unlike Windows, Samba allows fine grained
> > control over what shares, dicrectories files or groups of files to allow
> > or disallow oplocks on. If I were to take the time to performance tune
a
> > Samba server, I would only disable opolocks on those files that are
likely
> > to be opened read-write by multiple users. (Database files, as the most
> > comon example.) Performance improvements from oplocks are impressive,
> > and the load on the network is greatly reduced.
>
>
>
Boogerman
----- Original Message -----
From: "Rashkae" <ras...@tigershaunt.com>
To: "Boogerman" <boog...@interar.com.ar>
Cc: <sa...@lists.samba.org>
Sent: Thursday, May 08, 2003 12:41 PM
Subject: Re: [Samba] Oplock problem
> How are you deleting the file? By that, I mean, what program are you
> using to delte the file. Windows explorer or within something else?
Dan Austin
OS's.
Two changes were required-disabling oplocks in smb.conf and disabling
oplocks on the local XP machine by changing or creating two registry keys.
Did the following and the problem went away immediately:
These lines need to be in the global section of smb.conf:
oplocks = false
level2oplocks = false
(and then kill SIGHUP (smbd's PID), of course)
DISABLING OPLOCKS IN NT+ OS, Client side
===================================
To disable oplocks, the value of EnableOpLockForceClose must be set to 1.
You can verify (or change or add, if necessary) this Registry value using
the Windows Registry Editor (regedit.exe).
If you do change this Registry value, you will have to reboot the PC to
ensure that the new setting goes into effect.
STEPS:
1. Start > Run > Regedit.exe
2. Click on the + (plus sign) next to HKey_Local_Machine
3. Click on the + (plus sign) next to System
4. Click on the + (plus sign) next to CurrentControlSet
5. Click on the + (plus sign) next to Services
6. Click on the + (plus sign) next to LanManWorkstation
7. Click on the Parameters entry on the left-hand side of Registry Editor
8. If the EnableOpLockForceClose registry value already exists (on the
right-hand side of Registry Editor), ensure that its value is 1
9. If the EnableOpLockForceClose value already exists but its value is
not 1, double-click on EnableOpLockForceClose to change its value to 1
10. If the EnableOpLockForceClose entry does not exist, right-click in
the white space of the right-hand side of Registry Editor
11. Select New > DWORD value
12. Rename the value to EnableOpLockForceClose
13. Double-click on EnableOpLockForceClose to change its value to 1
To disable oplocks, the value of EnableOplocks must be set to 0.
You can verify (or change or add, if necessary) this Registry value using
the Windows Registry Editor (regedit.exe).
If you do change this Registry value, you will have to reboot the PC to
ensure that the new setting goes into effect.
STEPS:
1. Start > Run > Regedit.exe
2. Click on the + (plus sign) next to HKey_Local_Machine
3. Click on the + (plus sign) next to System
4. Click on the + (plus sign) next to CurrentControlSet
5. Click on the + (plus sign) next to Services
6. Click on the + (plus sign) next to LanManWorkstation
7. Click on the Parameters entry on the left-hand side of Registry Editor
8. If the EnableOplocks registry value already exists (on the right-hand
side of Registry Editor), ensure that its value is 0
9. If the EnableOplocks value already exists but its value is not 0,
double-click on EnableOplocks to change its value to 0
10. If the EnableOplocks entry does not exist, right-click in the white
space of the right-hand side of Registry Editor
11. Select New > DWORD value
12. Rename the value to EnableOplocks
13. Double-click on EnableOplocks to change its value to 0
"Boogerman" <boog...@interar.com.ar> wrote in message
news:20030508131009$7a...@gated-at.bofh.it...
Rashkae
using to delte the file. Windows explorer or within something else?
Rashkae
out that with Samba, you can disable oplocks selectively on files that
might cause problems. Such as database files, or whatever strange
activity you're seeign here. (Note: Are there multiple computers
accessing the file when you get this 30 second lockup? If this is a
client locking itself up, there might be a protocol quirk in Samba causing
it.)
On Thu, 8 May 2003, Boogerman wrote: