similar to: 2.0.4, still oplock_break failures [Actually dosChDir issue]

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

Hi All, First time mailing here, I hope someone can help. We?re running a OpenStack Newton environment on top of CentOS-7.3, LibVirt and Qemu-KVM-EV. We are encountered an issue live migrating a VM between 2 hosts with different CPUs and LibVirt throws the following error: libvirtError: unsupported configuration: guest and host CPU are not compatible: Host CPU does not provide required features:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of the Samba 2.2 code base. This is a maintenance release of Samba 2.2.8a to address the problem with user password changes after applying the Microsoft hotfix described in KB282741 to Windows NT 4.0/200x/XP clients. No other changes have been applied since Samba 2.2.8a. There are no further Samba 2.2.x releases

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of the Samba 2.2 code base. This is a maintenance release of Samba 2.2.8a to address the problem with user password changes after applying the Microsoft hotfix described in KB282741 to Windows NT 4.0/200x/XP clients. No other changes have been applied since Samba 2.2.8a. There are no further Samba 2.2.x releases

My name is Kenji Ichinoseki and I am in charge of a project at Sumitomo Electric Networks, Inc. Please give me cooperation by all means about the affair in the account of a title. Now, I included "Samba 3.0.37" in the Linux system currently developed (us). And it is testing using "smbtorture(samba3.5.8 source4) ". The point in question was found in our entry of this test. It

Oisin, Dave, Thanks both for sending me the mmap page from Ultrix. The problem I see is the following paragraph : > The mmap system call maps the memory of a character device (fd) It's the "character device (fd)" that's the problem. Reading this it appears that Ultrix doesn't have the ability to mmap a file descriptor from a arbitary file in the filesystem. For the

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

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

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

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,

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,

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,

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

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

Jay.Anderson@dw.deere.com wrote: > I believe the problem that occurs is that oplocks are left hanging on > the server, and are never removed. After a period of time, all the > shared memory that is allocated to file locking is filled, and the > server starts sending garbage back to the clients when they request > locks, confusing the clients and creating all sorts of strange

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

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

Hello, I hope anybody can help me with the following tough problem. We are running a samba-server (3.0.7) for providing fileservices for our constructions department. Since 2 Weeks we encounter problems with 2 of our workstations, running under win xp professional (The third xp workstation and the 2 running under win2k do not have this problem). The cad program tell's me, that it can not set