AFAIK 2.0 did not support oplocks, oplocks are a new feature in 2.2. You
can turn off oplocks in smb.conf if you want. Oplocks are meant to
increase the performance.
drenning, bruce wrote:> After upgrading from 2.0.10a to 2.2.4, I'm seeing many new messages
being
> logged. What does this mean?
>
> Jun 5 09:42:50 files2 smbd[27585]: [2002/06/05 09:42:50, 0]
> smbd/oplock.c:oplock_break(788)
> Jun 5 09:42:50 files2 smbd[27585]: oplock_break: no break received from
> client within 30 seconds.
> Jun 5 09:42:50 files2 smbd[27585]: oplock_break failed for file
> Pledgemaker/Pledgemaker-DRF/Appeal Loaders/02-R02L01-Lifeline Invite #1.txt
> (dev = 904, inode = 10554, file_id = 113).
> Jun 5 09:42:50 files2 smbd[27585]: [2002/06/05 09:42:50, 0]
> smbd/oplock.c:oplock_break(833)
> Jun 5 09:42:50 files2 smbd[27585]: oplock_break: client failure in
oplock
> break in file Pledgemaker/Pledgemaker-DRF/Appeal Loaders/02-R02L01-Lifeline
> Invite #1.txt
> Jun 5 09:42:50 files2 smbd[27585]: [2002/06/05 09:42:50, 0]
> smbd/reply.c:reply_lockingX(4480)
> Jun 5 09:42:50 files2 smbd[27585]: reply_lockingX: Error : oplock break
> from client for fnum = 10128 and no oplock granted on this file
> (Pledgemaker/Pledgemaker-DRF/Appeal Loaders/02-R02L01-Lifeline Invite
> #1.txt).
>
>