2.2.1 breaking oplocks failing
Mike Gerdts
Michael.Gerdts at usa.alcatel.com
Fri Aug 10 12:29:49 GMT 2001
Possibly related to this, I have a Win2k user that had a word doc open,
rebooted his computer, then tried to open the doc again. He says that
he is getting a dialogue telling him that he has it open (Currently the
document is being modified by [the user]). He claims to have it open no
where else.
The only relevant debug message that I see is...
[2001/08/09 15:33:29, 2] smbd/process.c:switch_message(661)
switch_message: queueing message due to being in oplock break state.
Level 10 debugs will come soon, unless I hear from someone else before
then.
Mike
On 08 Aug 2001 12:47:53 -0400, Mike Gerdts wrote:
> I am not terribly sure if this is a bug or just the way windows works...
>
> I had a user complaining about very slow reads of an html file. Turning
> up debugging revealed (among other things...)
>
> [2001/08/08 11:42:19, 5] smbd/open.c:open_mode_check(496)
> open_mode_check: oplock_request = 3, breaking oplock (3) on file
> dsl1/index.htm, dev = 3dc19ad, inode = 43826
> [2001/08/08 11:42:19, 3] smbd/oplock.c:request_oplock_break(932)
> request_oplock_break: sending a oplock break message to pid 19017 on
> port 35260 for dev = 3dc19ad, inode = 43826, tv_sec = 3b703b19, tv_usec
> = 6bcbb
>
> ...
> [2001/08/08 11:42:34, 0] smbd/oplock.c:request_oplock_break(997)
> request_oplock_break: no response received to oplock break request to
> pid 19017 on port 35260 for dev = 3dc19ad, inode = 43826
> for dev = 3dc19ad, inode = 43826, tv_sec = 3b703b19, tv_usec = 6bcbb
> [2001/08/08 11:42:34, 3] smbd/oplock.c:request_oplock_break(1073)
> request_oplock_break: broke oplock.
>
>
> Meanwhile smbstatus reports:
>
> 19017 DENY_NONE RDONLY EXCLUSIVE+BATCH /path/to/dsl1/index.htm
> Tue Aug 7 15:01:45 2001
>
> More log entries and raw snoop data are available if this would be
> helpful in diagnosing the problem, if there is one.
>
> If this is not a bug, can I get a hint as to the right place to find
> enlightenment on oplocks?
>
> Thanks much,
> Mike
>
More information about the samba-technical
mailing list