Problems with SAMBA 2.2.2 Oplocks

[Noel Kelly]

Drew,

The unkillable processes seem to have gone away with 2.2.3pre which is great
news,

Noel

-----Original Message-----
From: Robert Blayzor [mailto:rblayzor at inoc.net]
Sent: 11 January 2002 16:18
To: Drew.Zeller at statcan.ca; samba at lists.samba.org
Subject: RE: Problems with SAMBA 2.2.2 Oplocks


I believe oplock issues are being addressed in 2.2.3, however, I'm still
seeing some oplock issues on 2.2.3-PRE today.  I have to check my
software and make sure I'd not clobbering the same files, but I've also
had oplock errors from individual machines now that access their own
files and are accessed from no other machine.

At this point, my only solution is to turn oplocks off on the shares
that are giving me problems.

--
Robert Blayzor, BOFH
INOC, LLC
rblayzor at inoc.net


> -----Original Message-----
> From: samba-admin at lists.samba.org 
> [mailto:samba-admin at lists.samba.org] On Behalf Of 
> Drew.Zeller at statcan.ca
> Sent: Friday, January 11, 2002 10:43 AM
> To: samba at lists.samba.org
> Subject: Problems with SAMBA 2.2.2 Oplocks
> 
> 
> Hi,
> 
> I have recently upgraded one of my SAMBA servers from SAMBA 
> 2.0.7 to SAMBA
> 2.2.2 (December) and have now started to notice a number of 
> OPLOCK problems
> coming up in the logs and with users accessing files.
> 
> The following is a copy of what has been recorded in the logs 
> about the
> oplocks :
> 2002/01/10 11:26:34, 1] smbd/service.c:(610)
>   ieawts01 (142.205.48.25) connect to service macpchr as user macpchr
> (uid=699, gid=101) (pid 13980)
> [2002/01/10 11:27:06, 0] smbd/oplock.c:(1026)
>   request_oplock_break: no response received to oplock break 
> request to pid
> 29920 on port 52339 for dev = 40050001, inode = 31477  for 
> dev = 40050001,
> inode = 31477, tv_sec = 3c18bba8, tv_usec = e2dca
> [2002/01/10 11:27:06, 0] smbd/open.c:(554)
>   open_mode_check: exlusive oplock left by process 29920 
> after break ! For
> file windows/extend.dat, dev = 40050001, inode = 31477. Deleting it to
> continue...
> [2002/01/10 11:27:06, 0] lib/util.c:(1055)
>   PANIC: open_mode_check: Existant process 29920 left active oplock.
> 
> Also, when I checked, there are a number of smb processes 
> left running on
> the server that I am unable to kill.
> 
> I have tried searching in the news groups and have found 
> references to other
> people experiencing similar problems, however I have not 
> found anything with
> regards to a solution.  Does anyone know if there is a 
> solution available.
> Do I maybe just have an old version of 2.2.2 or is there a 
> patch available?
> 
> 
> Thanks in advance.
> 
> Drew
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
> 


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba