Locking problem with 2.2x

Scott Moomaw scott at bridgewater.edu
Wed Aug 29 02:39:29 GMT 2001


I've been looking lately for the cause of the locking problems on Samba
2.2.x.  Beginning this week, I've had to turn off oplocks on our
production server that's running 2.2.x  because we were getting hit with
too many stuck processes.  Looking back at a log, I've found the following
short dialog.

  api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON.
[2001/08/27 11:56:55, 0, pid=8010] rpc_server/srv_pipe.c:api_rpcTNP(1204)
  api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
[2001/08/27 11:57:09, 1, pid=8010] smbd/service.c:make_connection(610)
  writing3 (147.138.120.73) connect to service profiles as user ags002
(uid=12763, gid=60) (pid 8010)
[2001/08/27 11:57:11, 1, pid=8010] smbd/service.c:make_connection(610)
  writing3 (147.138.120.73) connect to service netlogon as user ags002
(uid=12763, gid=60) (pid 8010)
[2001/08/27 11:57:36, 1, pid=8010] smbd/service.c:make_connection(610)
  writing3 (147.138.120.73) connect to service profiles as user ags002
(uid=12763, gid=60) (pid 8010)
[2001/08/27 11:58:24, 1, pid=8010] smbd/service.c:close_cnum(650)
  writing3 (147.138.120.73) closed connection to service netlogon
[2001/08/27 11:58:24, 1, pid=8010] smbd/service.c:close_cnum(650)
  writing3 (147.138.120.73) closed connection to service profiles
[2001/08/27 11:58:40, 0, pid=8010] smbd/oplock.c:request_oplock_break(913)
  request_oplock_break: PANIC : breaking our own oplock requested for dev
= 740040, inode = 356082, tv_sec = 3b8a6e30, tv_usec = 46e8f and no fsp found !
[2001/08/27 11:58:40, 0, pid=8010] lib/util.c:smb_panic(1102)
  PANIC: request_oplock_break: no fsp found for our own oplock

In this log, it appears that pid 8010 does the following:
	connect to service profiles
	connect to service netlogon
	connect to service profiles (again)
	close connection to netlogon
	close connection to profiles
	get stuck on an oplock without a Files entry

I haven't had time yet to look at this in detail but wanted to through out
a possibility.  Is it possible that the multiple connects to the profiles
service are causing issues when the close connection occurs?  I know that
close connection removes entries from the files table.  Do connect and
close operations nest?  Is the close deleting entries that the client
thinks are still valid because of the multiple connects?  I may be way off
on this but couldn't resist asking about the possibility.

Scott
------------------------------------------------------------------------
 Scott Moomaw, Network Administrator              Scott at Bridgewater.edu
 Bridgewater College, IT Center
 Bridgewater, VA  22812
 Phone (540) 828 - 8000  x5437              FAX:  (540) 828 - 5493





More information about the samba-technical mailing list