Displaying 20 results from an estimated 1000 matches similar to: "oplock break"
2002 Jun 05
1
oplock break failures
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
1997 Oct 15
8
OPLOCKS
Robert Dal Santo wrote:
> Is there any work underway to get Samba to support OPLOCKS? I know
> they are difficult to implement but I'm faced with a decisions now to buy an
> NT box (Ugh!) or do a lot of messing around to get this application
> to perform decently. The application in questions takes around 5
> hours to do a taks without OPLOCKS and around an hour to do the
1998 Dec 14
15
oplock problem
Hello!
I need help (but who doesn's huh? :-) )
I meant to run one program - Money2000 (no, it is _not_ program from
Microsoft) together with samba on linux, but i have problems with oplocks.
This program is installed locally on win9x/NT and shares its databases. We
tried to place databases on novell, on NT server and on win95 acting as
server and everything worked fine. But when we tried
2001 Nov 16
1
CPU-load, memory-load, oplocks, smbd-core-dumps
Hi all,
I use samba 2.2.2 on AIX 4.3.2 (1500 NT4 sp6a / w2k sp2 workstation). since
i had updated from 2.0.7 to 2.2.2 the CPU load will very fast go to 100% an
d teh memory use of a smbd process will grow up to 100 MB. In teh log-files
are many errors like that:
PANIC: open_mode_check: Existant process 22700 left active oplock
smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock
2002 Jan 15
1
Oplock problems under high load
Hello, all.
I'm using Samba 2.2.2 at my FreeBSD 4.4-STABLE server, and have next
problems:
There is pool of W2K machines, each starting compilation job (usually 2
at one dual CPU machine).
Then these jobs trying to simultaneously access sources, located at
Samba server, appear problems.
Then I running 2 compilation threads from single machine - there is no
problems.
For jobs error seems
2002 Oct 29
5
oplock problems
We are running samba 2.2.3a ( for about 3000 users ) on HP/UX 11.11
fileservers.
Our customers are complaining about slow response on the opening/closing
of files in office/excel etc.
In the samba log file we see the following messages :
[2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(761)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file My
2002 Oct 14
2
oplock_break
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]
2000 May 03
2
2.0.7: unsolicited oplock break reply
I've used
oplocks = no
for a long time now, because of the famous "oplock_break" error, but I
decided to give 2.0.7 a try.
I still get "oplock break" errors as before, but this time I got a new
error too:
[2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file XXXXX/xxxxxx/mailbox.pst
2001 Feb 23
2
Unsolicited oplock breaks
Dear All,
we've been having some intermittent problems with students who's home directories are on a
Sun E450 running Samba 2.0.6. I'm not totally convinced that the problem is caused by the
server, but may be the network. However, I've had a look at the log.smb file and I'm seeing some
error messages that I've not come across before:
[2001/02/23 18:20:40, 0]
2002 Oct 29
1
BUG: 2.2.6 and dos recusive filecopy
Hi!
I've been using samba for some time now with about 20 users and with
remote installation of Windows XP from dos (TFTPboot image with dos
network drivers - ms client 1.6c).
On all releases (up to, and including 2.2.5) a recursive xcopy (from
dos) copied all files normally.
When I upgraded to samba 2.2.6, the recursive xcopy (win98 version of
xcopy.exe, copying from a mapped drive)
2002 Sep 09
6
problem saving word documents
Hi,
Thought I posted this already two weeks ago. Haven't seen any reactions
yet, so I post it again
We got the following problem here:
Every now and then, users are unable to save Word or Excel documents on our
Samba server. We already tried a couple of things: disabling oplocks,
increasing oplock break wait time, putting the documents on a new share,
... but to no success so far.
The
2000 Mar 18
6
Login Scripts
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Everybody,
I would like to run a login script that maps out the different shares
on a RH 6.1 server running SAMBA 2.06. I have several Win98 and NT
workstation clients that log into an NT domain and use my server for
file and print services. The Samba server is not part of the domain.
The clients currently have access to a share common to us
1999 Nov 12
4
Oplock
Hi
Does any one has idea if Samba supports client side oplocks.
i.e if we are using "smbclient"
If yes how to enable/disable it. Where can we get the details.
Thanks
Pankaj
2003 Jul 31
1
oplock_break: client failure in oplock break in file ...
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)
2005 Jul 29
0
incoherent oplock request/reply
Hello,
I'm running a samba 3.0.14a server in production on a fedora core 3 (kernel
2.6.9-1.667smp) with a least 250 clients (XP Pro SP2) (up to 400 sometimes).
A few days ago, a problem appeared with a soft that we are using for a long
time. (Petit Robert, a french dictionnary).
When someone launch the dictionnary, many clients are freezed when they try to
access to the "start
2002 Oct 15
0
What is "client failure in oplock break"?
Below are a number of errors that appeared in a log file today.
I am running Samba v2.2.5 on a Red Hat Linux v7.3 system. The client
experiencing/causing the errors below is a WinXP(SP1) machine.
The log entries below pertain to 2 errors, the first in handling file
"6.zip" and the second in attempting to run file
"DiskeeperWks413zssi.exe". I didn't see the first
2000 Feb 14
3
File Locking Issues/Oplock problems
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
2005 Feb 02
1
Oplock errors in 2.2.8a
Hi,
We are having connection timeout issues in Excel and Word. Was this an
issue that was resolved in post 3.0 versions? We are running 2.2.8a.
Below is the samba log file and I have attached a netmon output.
Thanks,
Domenic
[2005/01/24 09:13:48, 0] smbd/oplock.c:oplock_break(797)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file
2002 Mar 15
1
2 Samba problems (oplock & hosts allow)
Hello everybody,
I have 2 questions about Samba operation:
First, hostnames don't work in my "hosts allow"
directive, although smb.conf(5) explicitly says "You
can specify the hosts by name or IP
number". If I specify a client by its name, that
client is not allowed access, even though the server
can do reverse DNS on the client's IP. The message I
get in the
2004 Apr 03
1
oplock windows XP client
Hi,
I use samba for 5 years in a small enterprise network. We have recently
changed our windows client and migrate from windows 95 to windows XP :-).
Samba is running on a debian woody. Since we are using windows XP home
edition I can see the following log messages :
[2004/04/02 15:27:50, 0] smbd/oplock.c:oplock_break(758)
oplock_break: receive_smb error (Success)
oplock_break failed for