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?
On Thu, 8 May 2003, Boogerman wrote: Nope, there is only one client accessing the file. What I did (this is just 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 [EMAIL PROTECTED] ----- Original Message ----- From: "Rashkae" <[EMAIL PROTECTED]> To: "Boogerman" <[EMAIL PROTECTED]> Cc: "Rashkae" <[EMAIL PROTECTED]>; "John H Terpstra" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> 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 > [EMAIL PROTECTED] > > ----- Original Message ----- > From: "Rashkae" <[EMAIL PROTECTED]> > To: "Boogerman" <[EMAIL PROTECTED]> > Cc: "John H Terpstra" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > 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. > > > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
