[Samba] Oplock problem in 2.2.3a - is there a solution?

[Sanjiv Bawa]

Please provide more details about this. What platform are you running on?
What client os are you using?

What programs are you running on your clients?

Also use,
oplocks = no
level2 oplocks = no

Thanks.

Sanjiv

-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]On
Behalf Of Stuart Haas
Sent: Monday, February 11, 2002 10:32 AM
To: samba at lists.samba.org
Subject: [Samba] Oplock problem in 2.2.3a - is there a solution?


Hi -

This oplock issue has turned out to be a real problem with 2.2.3a - it is
preventing my clients from access files.  In 2.2.2 I still had problems, but
they did not prevent files from being accessed. I am running Linux 2.4.18
pre9 using reiserfs, if that matters.

---
Feb 11 11:22:19 fs1 smbd[14907]: [2002/02/11 11:22:19, 0]
smbd/oplock.c:oplock_break(758)
Feb 11 11:22:19 fs1 smbd[14907]:   oplock_break: receive_smb error (Success)
Feb 11 11:22:19 fs1 smbd[14907]:   oplock_break failed for file
Documents/Comp Lists/New Comp List.xls (dev = 811, inode = 474105, file_id =
934).
Feb 11 11:22:19 fs1 smbd[14907]: [2002/02/11 11:22:19, 0]
smbd/oplock.c:oplock_break(843)
Feb 11 11:22:19 fs1 smbd[14907]:   oplock_break: client failure in break -
shutting down this smbd.
---

I have been following the list, but I have not seen a solution posted - I
tried 'kernel oplocks = no', but I still have the problem.

Any suggestions?

Stuart



This email has been scanned for all viruses by the MessageLabs SkyScan
service. http://www.messagelabs.com/

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba