similar to: SAMBA 2.0.5a oplock_break: client failure in break

Hi, I have referred to the archive and some of you were having the oplock_break problem. Does anyone have any solution for this? Will reboot fix the problem? Please advise. regards, Bridget

Hi, Probably this problem is known and has already been discussed in this group, but I did not find any hints in the archive nor in the package description. On a PII/400/256MB RAM I am running SuSE 5.3 with smbd 2.0.2. Unfortunately, sometimes the WinNT client seems to loose its connection which crashes a WinNT application (SolidWorks) if the latter wants to save a project. (This happened 8

Hi! I keep getting errors like these: oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success)

Hi there everyone! I'm using Samba 2.0.5a-19990721 on a RedHat 6.0 machine with Linux kernel 2.2.12. My system generally works fine, however recently I've had some complaints about some files being corrupted. The latest and best-handled to enable a debugging happened at around the same time. Both clients were using Windows95 OSR2 machines with Excel 97 SP-2. Two users reported the problem

We recently tried the upgrade to 2.0 Beta series (just finished testing Beta 4) on our network. Everything works fine with 1.9.18pl10, but once we start 2.0 in its place we start getting the following in the log files: [1998/12/17 05:00:12, 1] smbd/files.c:file_init(219) file_init: Information only: requested 10000 open files, 246 are available. [1998/12/17 05:07:52, 1]

2.0.4b, RH60 (2.2.6+raid1, non root-raid), accessed from win98/ie5. Intermittently ie5 takes very long to load an html page from samba; at the same time it loads another html page ok from another linux/samba1.9.x At 10:47:34 I click on the html page and it is loaded at 10:48:18. [1999/06/23 10:47:34, 1] smbd/service.c:make_connection(488) go (10.0.0.115) connect to service go as user go

Dear Samba users, I've had a problem recently with Samba (2.2.3a, and now 2.2.5) on my OpenBSD 3.1-stable Installation. Bsd: OpenBSD 3.1-stable (CYNOSURE) #1: Fri Oct 4 01:06:45 EST 2002 avant@XXXX:/usr/src/sys/arch/i386/compile/CYNOSURE I get problems such as these: <poor formatting> [2002/10/13 23:00:04, 0]

Hi, I am running Samba 2.0.3 on Linux Kernel 2.2.5 (SuSE 6.1) in a test environment with a Win NT server (PDC), the Linux box taking over step by step the file- and printserver tasks, and Win 95 clients. Samba is setup with security=domain at this stage. It just happened again what I have seen only a few times before. When I use Outlook 98 on the Win95 machine and want to access the

hello i have "oplock_break failed " in logs, see below. should i consider removing oplocks ? regards --------------- [2004/09/09 11:08:53, 1] smbd/service.c:make_connection_snum(705) ul_55 (129.199.59.202) connect to service users initially as user DOM_BIBLIO+Daniele (uid=10029, gid=10000) (pid 19058) [2004/09/09 11:09:23, 0] smbd/oplock.c:oplock_break(807) oplock_break: receive_smb

I've been seeing these in my logs files ever since I upgraded to 1.9.18p10 and turned on oplock support for users' home directories: --snip -- 1998/10/07 10:05:44 oplock_break: receive_smb timed out after 30 seconds. 1998/10/07 10:05:44 oplock_break failed for file Start Menu/Open Office Document.lnk (fnum = 14, dev = 808446, inode = 45cb8). 1998/10/07 10:05:44 oplock_break: client

Hi everyone, Just today one of our users informed me that a file she was working on in Microsoft Excel 97 got corrupted. She was working on the file directly on our server, which is running Samba 2.2.3a compiled using gcc-3.0.4 on Linux kernel 2.4.17-xfs and XFS-based filesystems. I checked the Samba logs for her machine and found the following in a search for the filename of the Excel file she

samba@samba.org ????????: > SAMBA Digest 2226 > >For information on unsubscribing see http://samba.org/listproc/ >Topics covered in this issue include: > > 1) RE: weird printing problems. > by "cbrink" <cbrink@allsportssupply.com> > 2) Re: weird printing problems. > by "John J. LeMay Jr." <jlemay@njmc.com> > 3) Connection

I found these articles that talk about the oplock_break problem (specifically they are related to problems with word97): http://support.microsoft.com/support/ntserver/serviceware/nts40/e9msge2bc.asp http://support.microsoft.com/support/kb/articles/q163/5/25.asp Basically they say: either apply sp3 on the winnt client or disable oplock on nt server But they don't say anything about win9x,

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

Im running an accounting package (Sage Businessworks) and I'm running into issues with file locking with this program when I put the businessworks data files on a Samba file share. I'd like to get it off a NT file share if at all possible as Im about to decommission our NT server. Im running Samba 2.0.6 Im seeing errors from any machine accessing the Accounting data: ==> log.ryan

-----Oprindelig meddelelse----- Fra: Simo Sorce [mailto:idra@samba.org] Sendt: 8. januar 2003 15:40 Til: Preben S?rensen Cc: Andrew Tridgell; Jeremy Allison; samba-bugs@samba.org Emne: Re: oplock_break (PR#26342) Please send help request to the users mailinglist samba@samba.org Simo. On Wed, 2003-01-08 at 15:38, ps@datamann.dk wrote: > Full_Name: Preben S?rensen > Samba_Version: 2.2.5

Hi! Even with 2.0.4, I'm still seeing a lot of oplock break failures (clients failing, see log further down). The client hangs for approx 30 secs (sometimes more) and then gets back online. At least one user can't use the file shares at all; it hangs whatever he does, and on any computer he uses (NT or 98, laptop, desktop...) Other users have less problems, but maybe they are less

Many 2.0.x users have the: [1999/06/23 10:47:48, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:47:58, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:48:08, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:48:18, 0] smbd/oplock.c:oplock_break(790) oplock_break: receive_smb timed out after 30 seconds. problem. I get this

Hello there. I'm having a few problems using samba 2.2.3a and sharing a paradox database. On the whole everything works fine but (there's always a but), every now and again. a machine's shares will close causing the database to crash (sometimes only that machine) - the other networked machine recover after a few error messages. I guess the easy answer would be to disable oplocks

We're using CentOS samba for about 20 workstations, mostly XP, some 2000 and two win98. Samba shares a data directory with Word, Excel and Access documents/db's. Also Exact for Dos is running from this share (executable and data). The users experience a long delay every morning opening the first Word document (Word 97, Word 2000). This could take 10 minutes or so. If they close