similar to: Samba & Redhat - Oplocks

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

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

Hi all, I have the following problem. A Linux (2.2.19) machine is running Samba 2.2.2 as a PDC. The clients are Win2K SP2. A user accesses several Excel 2000 files on a share. This sometimes results in long(ish) delays (the user reports around 10 seconds, although this could be longer) and the message from Excel that the file is in use and can only be read. After closing and re-opening the file,

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

Well I'm having some trouble with samba, I had those troubles on a box for quite some time and not long ago I moved all the stuff to a new box to see if it'll work better but it doesn't. I'm monitoring one person in particular because she's the one who do most of the editing stuff in there. What happens is when she opens a document (.doc or .xls most of the time), when she

Guys, I think the answer to my question is to upgrade samba. However, since this is my production machine, I thought I would try and understand the problems I'm having a little better to insure that an upgrade will correct my issues. My setup - Mandrake 7.2, samba 2.09. Win98, ME and XP clients. The 98 and ME machines have no problems. The XP machine has some intermittent slowness

Hello! Whenenver I try to save a downloaded file with Opera [6.x] to a Samba share [2.2.x], Opera (and also the windows-explorer) freezes. Having set log-level to 1, I get the following message after a while. Sometimes, but not always, Opera continues working after 30seconds or so. I have the same behaviour in Samba 2.2.2, 2.2.3a and 2.2.4-pre. My Server is running SuSE 7.3 with the 2.4.16

I'm using samba and cups to allow NT/2k machines to print to an HP LaserJet 4000N printer. The printer works fine except for one in house program. In this one program, all the horizontal lines that should be printed are missing. Originally I thought this was a driver problem, but today, for no apparent reason, it started printing the horizontal lines... but only for the first page of each

> I have samba v 2.2 on one of my production server, the client connections > seem to drop sometimes, these clients run overnight jobs and when this > happens there job crashes and they have to manually start it. > > Below is the snippet of the log for one of such clients with problems. > > ###########cut-paste of log (only part of it)######### > > oplock_break:

Hi, we have a strange samba locking problem with version 3.0. Sometimes user only get a read only access to files. This happens with different users on different clients. Unix permissions are OK. I have realy no idea. Can you help ? Thanx Peter Huber -------------- next part -------------- [2004/03/02 15:03:56, 5] smbd/uid.c:change_to_root_user(217) change_to_root_user: now uid=(0,0)

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)

Hi folks I hope someone might be able to shed some light on a problem that I am experiencing with a Samba server. I installed this server about 2 and a half years ago on a client's site. The server has been running fine. We are now experiencing two problems which according to the client occured overnight. The first problem started about a week and a half ago when they found that when trying

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

Hi all Got a couple of errors in the logs wondering what they mean??? Google does not come up with too much on these NT_STATUS_NO_SUCH_FILE, NT_STATUS_SHARING_VIOLATION, NT_STATUS_INVALID_LEVEL and NT_STATUS_OBJECT_NAME_NOT_FOUND. Four clips illustrating the above are below... I have am wondering how I sort this out. I am particularly worried about the NT_STATUS_NO_SUCH_FILE. All the

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]

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

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

hello, until last week I had 2.2.1a in place, which, except some fox (dos) share which needed 'veto oplocks files', worked ok; upgraded to 2.2.3a with the same smb.conf (details below) and suddenly I started having oplocks problems (not on the dos share, that one is ok) with almost every other share (those hold windows files: programs, *doc, *xls): [2002/02/19 12:31:28, 0]

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

In my smb.conf file, I've got the following section: [homes] comment = Home Directories valid users = %S guest ok = no read only = No create mask = 0640 directory mask = 0750 browseable = No veto oplock files = /*.mdb/*.MDB/*.pst/*.PST/ And yet, in the syslog, I'm still getting these... Mar 10 10:22:34 riffraff