When trying to delete or copy over certain files on my Samba server,
Windows hangs for some time and then gives "access denied". I can
delete
these files directly from the server, so it's a Samba or Windows problem.
There seems to be nothing special about these files, other than that Samba
doesn't like touching them. Upon checking the Samba logs, I find this
message or similar repeating constantly:
[2002/06/10 20:47:22, 0] smbd/oplock.c:request_oplock_break(997)
request_oplock_break: no response received to oplock break request to
pid 3303 on port 1098 for
dev = 302, inode = 2528190
for dev = 302, inode = 2528190, tv_sec = 3d048716, tv_usec = 19b20
Are these problems related? How can I fix them?
Thanks,
Tim Bates
After some more research, I have more information on the oplock problem:
The problem occurs when trying to copy files. I was originally using DOS
xcopy. It copies cheerily along until reaching some seemingly random file,
and then dies with "The specified network resource or device is no longer
available". Then when I go back to delete the (half-copied) file through
Explorer, it tells me 'access denied'. I then have to log into the
server
and delete it using good old 'rm'. If I now try to copy the same file
using
xcopy once more, the same error occurs on the same file. However, if I use
Explorer to copy it, it copies that file quite happily and then gives the
same error on a different, later file. I click OK, and the copy dialog sits
there until I click Cancel on it, whereupon Explorer hangs the window for a
good 15 seconds before doing anything, including redrawing itself. Once
again, if I try to delete the file, I get a 15 second pause and then an
'access denied'.
The oplock break messages in the log are persistant, even when I'm doing no
more than looking at filenames, not even opening files. This makes me doubt
the two being related, but since I have very little idea of how Samba
operates, and no idea about what an oplock is, I'm hoping someone can help
me out.
Thanks,
Tim Bates
Here's more info for your diagnosing pleasure (and my frustration).
I discovered that I had about 20 copies of smbd running. As daemons.
Restarting Windows fixed the "access denied" errors. Or maybe it was
killing all the smbd's and starting just one. I did both at the same time,
you see.
With only one smbd running, I'm no longer getting oplock errors. There were
a few like this:
[2002/06/10 21:37:47, 0] smbd/oplock.c:process_local_message(356)
process_local_message: Received unsolicited break reply - dumping info.
some time ago but they're not happening any more. It seems that having all
those smbd's running was the source of the oplock problem, but what caused
them all to start is beyond me. It's running as a daemon, not through inetd.
I'm not actually having any more problems now, but if someone can suggest
what caused all those smbd's to open, I'd like to try and prevent it
happening again.
More proof that posting a problem publicly is the best way to fix it, or in
my case make it go away.
Thanks,
Tim Bates
I got this error message today (have never seen it with 2.2.4) [2002/06/21 14:30:38, 0] smbd/oplock.c:oplock_break(796) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file user/prices 7.02.qpw (dev = 29d03, inode 2998188, file_id = 2228). [2002/06/21 14:30:38, 0] smbd/oplock.c:oplock_break(868) oplock_break: client failure in oplock break in file user/prices 7.02.qpw [2002/06/21 14:30:38, 0] smbd/reply.c:reply_lockingX(4490) reply_lockingX: Error : oplock break from client for fnum = 10509 and no oplock granted on this file (user/prices 7.02.qpw). Now, I see that it says "client failure," however I checked the logs on the client computer, and see no evidence of a crash (XP computer). However, I think Quatro Pro (.qpw) is fairly unstable, so it's possible it was a program crash that for some reason didn't show up in the logs. Should I be worried about this error? thanks, Scott