Oplock Problems: request_oplock_break: PANIC

Alexander Muth alexander.muth at gla-rlp.de
Thu Dec 13 01:23:14 GMT 2001


Hello,

we are using Samba 2.2.2 on Solaris 2.7 (sparc) with abount 80 NT
(SP6.0a) Clients.
After upgrading to Version 2.2.2 we get a lot of Oplock Problems.
Here are some prototyps of them:

1.

[2001/12/05 14:38:29, 0] smbd/oplock.c:request_oplock_break(929)
  request_oplock_break: PANIC : breaking our own oplock requested for
dev = 1540
056, inode = 2005320, tv_sec = 3c0e2355, tv_usec = 813e and no fsp found
!

2.

[2001/12/05 19:33:45, 0] locking/locking.c:delete_fn(250)
  locking : delete_fn. LOGIC ERROR ! Shutting down and a record for my
pid (1276
4) exists !

3.

[2001/12/12 14:19:00, 0] smbd/open.c:open_mode_check(555)
  open_mode_check: exlusive oplock left by process 9127 after break !
For file k
aiserslautern_arc/quellen_topo.shx, dev = 1540032, inode = 2580991.
Deleting it
to continue...

Because this is a production System it is very difficult to generate a
log level 10.

Are these Problems specific for Samba 2.2.2 or Solaris 2.7?
Is it known Problem?
Do you have any idea about how to solve this problem ?

Any ideas? Thanks!

--
Alexander Muth    mailto:alexander.muth at gla-rlp.de
Geologisches Landesamt Rheinland-Pfalz
EDV-Referat
Emy-Roeder-Str. 5, 55129 Mainz
Tel: 06131 9254 133 Fax: 06131 9254 123
http://www.gla-rlp.de






More information about the samba mailing list