similar to: Oplocks, Oplock_break and request Oplock_break

A productional system (linux) running samba 2.2.5 runs 'cracy' from yesterday. There are lot of 'odd' behaviours. People cant logon or cant logoff. Access to files fails. Examining the logs the most eyecatching events are: (not that the keynumber started at 959 and went slowly down. I did not wait until it goes to zero and let the user reboot its machine before) Any idea ? thnx,

Hi everybody, although I'm not a member of this list, I'd like to address the following problem here. Maybe someone is familiar with it or knows how to solve it. He or she would save my sanity. We have a samba 2.05a server on a solaris 2.6 box. It works as file and program server. Once or twice a day some of our clients receive a redirector timeout, error code 3013. The error message

Greetings We just updated two RH9 servers to 3.0.14a-1 and are still seeing a lot of errors in the logs. They're not stopping us working but I would _really_ like to understand what is causing them. On the first server, in the logwatch, we get a whole swag of: samba: Unknown Entries: session opened for user janicer by (uid=0): 6 Time(s) session opened for user sonjap by

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

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

We are running Samba 2.0.5a on an AIX 4.2.1 box, and since we upgraded from 1.9.18, a Windows 95 client reports intermittent problems (timeouts) when saving small files. The log.smb file has entries from those events: [1999/09/08 14:59:07, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:17, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:27,

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]

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

-----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

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! 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, 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

Fabian, Fast explains. On the NT server work BrightStore with version r9, more highly does not go because of NT. On the REHL4 side works (worked) BrightStore Linux Client r11.5. Smaller version does not work goes because of RHEL4. BrightStore servers r9 and Linux Client r11.5 are not compatible unfortunately. I must now decide everything with the version Share to work to get. Or the operating

Sorry for all my emails. I don't know where to post this problem, so I also post it to the ntdom mailing list... Since I upgrade to 2.0beta5, I got a lot of messages like this in log.smb: [1999/01/08 16:30:38, 0] smbd/oplock.c:(734) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file GN/previsions/previsions 99/previsions globales 99.xls (dev = 800073,

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 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,

can anyone tell me what these sorts of errors in log.smbd mean? my searches thus far haven't uncovered anything at all recent [2011/04/25 23:19:43, 0] smbd/dir.c:292(dptr_close) Invalid key 0 given to dptr_close we have samba 3.4.8 running under solaris10; the number of clients ranges between 30-100 at any given time. all works flawlessly for months at a time, yet every few months or

Hi all, I've posted a similar message a few weeks ago. I had the 'oplock' problem. I run a linux server with samba (specification below). I get a reply who told me to disable kernel oplocks and oplocks. I did exactly what he told me to do. I hoped it worked... but it did not... From there one i started reading in the archives and followed the 'lock' discussions in this list.

Hi, I run a Samba Server on openSuSE 11.4 with LDAP Authentication Backend. appears to work fine. However, only some shares work on my Mac client boxes: for instance, i can browse my home directory on the Linux box (/home/ray), whereas other shares are simply empty ("r01" below) on the mac (but they are shown as connected). [homes] comment = Home Directories valid users =

Concerning the question "Why on earth do I see the dosChDir to /home/girgen/ports???!" you might check out how you *start* or *started* Samba. Based on my observations, and a quick check of the source code (see source/smbd/server.c, and source/smbd/uid.c), when you start up smbd, it finds out the current directory, saves it as "OriginalDir", then whenever a new user is setup,