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. I've t
ried a lot of options. I even got myself a CVS samba, because that (so i've
read) would solve the the oplock 'bug', but still no luck... I don't
know what to do anymore.
Allright, here is an overview of the layout of the small network.
Ik have 12 win95 client (a school class), and one debian (sid) linux server.
See here for the server specs:
Samba version: 2.2.3-pre
hda: QUANTUM FIREBALL ST1.6A, ATA DISK drive
cpu: Intel Pentium 75 - 200 stepping 05
Memory: 61732k/65536k available (1407k kernel code, 3416k reserved, 477k
data, 204k init, 0k highmem)
kernel: 2.4.4
fstab entry:
/dev/hda1 / reiserfs defaults,errors=remount-ro 0
1
There is a directory /opslag
drwxr-xr-x 4 nobody nogroup 160 Nov 12 14:28 bak/
In this directory are the files which more clients at the same time have to
acces. But as you might expected, only one client is allowed to do s
o, if an other client tries to access the same file, it gets a time-out or
crashes.
I tries it with win98 and there were no problems. Only win95 has the oplock
problem. Can some pls take a look at my problem.. I would be very gr
acefull if someone could straighten things up for me.
Below is my very small smb.conf and a log output from the moment things went
wrong. I hope i've given enough information.
Thanx in advance
Housebee
===== smb.conf =====
# Global parameters
[global]
config file = /usr/local/samba/lib/smb.conf.%I
workgroup = PCROOM
netbios name = MerkelBach
encrypt passwords = Yes
wins support = Yes
security = share
socket options = TCP_NODELAY
guest ok = yes
# Browsing election options
local master = no
# Debug logging information
log level = 2
log file = /var/log/samba.log.%m
max log size = 1000
debug timestamp = yes
syslog = 2
[bak]
comment = bak
path = /bak
browseable = yes
read only = no
# kernel locking = no
===== end smb.conf ====
Here is a bit from the log produced when two client tried to access the same
file.
[2001/11/12 16:22:37, 0] smbd/oplock.c:request_oplock_break(981)
request_oplock_break: no response received to oplock break request to pid 636
on port 1036 for dev = 301, inode = 45828, file_id = 1
[2001/11/12 16:22:37, 0] smbd/open.c:open_mode_check(552)
open_mode_check: exlusive oplock left by process 636 after break ! For file
cfiles/digiwijs.FCD, dev = 301, inode = 45828. Deleting it to cont
inue...
[2001/11/12 16:22:37, 0] lib/util.c:smb_panic(1053)
PANIC: open_mode_check: Existant process 636 left active oplock.
[2001/11/12 16:22:37, 2] smbd/connection.c:count_fn(97)
pid 639 doesn't exist - deleting connections 1 [bak]
[2001/11/12 16:22:37, 2] smbd/reply.c:reply_sesssetup_and_X(979)
Defaulting to Lanman password for pcroom
[2001/11/12 16:22:37, 1] smbd/service.c:make_connection(619)
pcr4 (172.16.8.106) connect to service bak as user nobody (uid=65534,
gid=65534) (pid 640)
[2001/11/12 16:22:37, 0] smbd/dir.c:dptr_close(278)
Invalid key 257 given to dptr_close
[2001/11/12 16:22:37, 0] smbd/dir.c:dptr_close(278)
Invalid key 256 given to dptr_close
--
MVG,
Guido
*********************************************************************
Email: housebee@xs4all.nl
Homepage: http://housebee.xs4all.nl
OS: Debian GNU Linux (Sid)
__ __ __
/\ \/\ \ /\ \
\ \ \_\ \ ___ __ __ ____ __\ \ \____ __ __
\ \ _ \ / __`\/\ \/\ \ /',__\ /'__`\ \ '__`\ /'__`\
/'__`\
\ \ \ \ \/\ \L\ \ \ \_\ \/\__, `\/\ __/\ \ \L\ \/\ __//\ __/
\ \_\ \_\ \____/\ \____/\/\____/\ \____\\ \_,__/\ \____\ \____\
\/_/\/_/\/___/ \/___/ \/___/ \/____/ \/___/ \/____/\/____/
*********************************************************************
pkg PBE-SIT
2001-Nov-14 01:26 UTC
Re: win95 + linux oplock error, even with kernel oplocks = no.
This might not be the solution, but since you are so desperate I'll give it a shot. ;-)> Ik have 12 win95 client (a school class), and one debian (sid) linux server.We had the excact same problems in the log as yours with a small network of our own. We figured the problem was with the speed and duplex of the network cards, and this again generated the samba error messages. - Our Solaris box was up with 100mhz/full duplex and hub'ed (100mhz hub) to a - NT-box with 100mhz/full duplex. This would seem quite nice in theory, but it seems that the hub could not handle the full-duplex part. So we put both to 100Mhz/half-duplex (which really is a no no with 100Mhz speeds) and we had no problems with the transfer nor any error messages in the samba-log anymore. Another solution might be to 'switch' the network components. Put a switch there instead of a HUB. You might then see that 100Mhz/Full Duplex would work. Hint: if you can, never use 'auto-negotiate' on speed nor duplex in any op-sys environment. You can check what speed and duplex you have (in solaris anyway) with this command: dmesg And you can set the unix-network speed and duplex in /etc/system (dunno if its the same in Linux). Search for "hme_adv_100fdx_cap" on the net and you should get some manual hits for it i would guess.> Æ2001/11/12 16:22:37, 0Å smbd/oplock.c:request_oplock_break(981) > request_oplock_break: no response received to oplock break request to pid 636 on port1036 for dev = 301, inode = 45828, file_id = 1> Æ2001/11/12 16:22:37, 0Å smbd/open.c:open_mode_check(552) > open_mode_check: exlusive oplock left by process 636 after break ! For filecfiles/digiwijs.FCD, dev = 301, inode = 45828. Deleting it to cont> inue... > Æ2001/11/12 16:22:37, 0Å lib/util.c:smb_panic(1053) > PANIC: open_mode_check: Existant process 636 left active oplock.Regards Per Kjetil Grotnes --- IT-Seksjonen, Plan- og bygningsetaten, Oslo Kommune Tlf: 22 66 26 61, Fax: 22 66 26 65