oplock_break errors - XP clients & 2.2.3a server

Stuart Freedman stuart.freedman at thefreedmanfamily.com
Thu Mar 14 09:57:02 GMT 2002


Hi folks.  I hope I'm addressing the correct forum here, since this
appears to be a bug rather than an RTFM issue.  (BTW, I appreciate all
the work the Samba team have been doing over the years.  Thank you all!)

I currently manage a Linux (kernel v. 2.2.18) box running 2.2.3a
functioning as PDC & "almost everything server" on a small office LAN
with most clients now running XP Professional.  I'm surprised I haven't
seen more complaints from the users, but I did get a complaint about
"access denied" to a file & found a corresponding set of error messages
in the log.smbd (BTW, my log level is 1):

[2002/03/13 11:54:13, 0] smbd/oplock.c:oplock_break(758)
  oplock_break: receive_smb error (Success)
  oplock_break failed for file [file path]
(dev = 301, inode = 315075, file_id = 651).
[2002/03/13 11:54:13, 0] smbd/oplock.c:oplock_break(843)
  oplock_break: client failure in break - shutting down this smbd.
[2002/03/13 11:54:13, 1] smbd/service.c:close_cnum(655)
  [machine name] (192.168.1.8) closed connection to service shared
[2002/03/13 11:54:13, 1] smbd/service.c:close_cnum(655)
  [machine name] (192.168.1.8) closed connection to service [username]

I've seen this type of log entry with several different applications (MS
Word 2000, Publisher 2002, a Hebrew WP program called Davka Writer), so
I don't think it's app dependent.  (Some apps probably recover better
than others.)  In fact, I see something similar with .lnk files even! 
In some cases like that one (which I assume is just Explorer) or Excel
2000 I can see sets of slightly different series of messages:

[2002/03/11 17:45:11, 0] smbd/oplock.c:oplock_break(788)
  oplock_break: no break received from client within 30 seconds.
  oplock_break failed for file [filepath.xls] (dev = 301, inode =
252898, file_id = 4510).
[2002/03/11 17:45:11, 0] smbd/oplock.c:oplock_break(833)
  oplock_break: client failure in oplock break in file [filepath.xls]
[2002/03/11 17:45:11, 0] smbd/reply.c:reply_lockingX(4388)
  reply_lockingX: Error : oplock break from client for fnum = 8894 and
no oplock
 granted on this file ([filepath.xls]).

While I have your attention, I hope you don't mind if I add to the
chorus of folks I've seen (mostly on the "samba" list), who have
witnessed a few other glitchy behaviors & error messages, such as:

1. Reading roaming profiles sometimes (i.e., occasionally) fails. 
(Sorry I didn't write down the error message on the XP popup - it
threatens to go away after 20 secs. anyway.  I think it often chastises
me for enabling offline caching on the profiles share.)  Note that I
have tried setting "nt acl support = no" on the profiles share to no
avail.  Do I need to disable oplocks or something?  (If so, will our
logons & logoffs take even longer?)

2. Domain logons from XP work, but A) don't look like they run the
defined startup BAT file from the netlogon share (while the couple of 98
boxes we have left do run it), and B) generate error messages in the log
a la:

[2002/03/13 10:30:21, 0] rpc_server/srv_netlog.c:api_net_sam_logon(206)
  api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON.
[2002/03/13 10:30:21, 0] rpc_server/srv_pipe.c:api_rpcTNP(1200)
  api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.

NB:  Given that this is a production environment, I'm more likely to
implement workarounds (e.g., turning off oplocks, if it's a good idea)
and wait for a "blessed" 2.2.4 tar-ball than I am to grab today's fixes
from the CVS tree.

Sorry to be so long-winded here, but I've been just lurking for a
while.  Thanks in advance for any & all fixes & advice.

			Stuart

P.S. Any plans to implement a network recycle bin option (e.g.,
http://www.amherst.edu/~bbstone/howto/samba.html ) into the main code
tree?
-- 
Stuart Freedman             E-mail: stuart at thefreedmanfamily.com
Unix & Network Consultant        or stuart_freedman at yahoo.com
408 S. Pleasant Ave.        http://www.thefreedmanfamily.com/
Ridgewood, NJ 07450-5446    Phone/FAX: +1 201 689 6832
U.S.A.




More information about the samba-technical mailing list