[Samba] Re: file locks problem??

Sun Nov 17 15:14:01 GMT 2002

This is what I'm using at home:

root at natsumi:/usr/local/samba/bin# ./testparm -v | grep oplock

        kernel oplocks = Yes
        oplock break wait time = 0
        veto oplock files =
        fake oplocks = No
        oplocks = Yes
        level2 oplocks = Yes
        oplock contention limit = 2

I'm running samba 3.0a20, and it works flawlessly. This also worked OK with
latest stable (2.2.6).

In the office I disabled kernel oplocks to solve the issue and promised
myself I would go and make big update, but I still haven't (shame on me :^).
If I remember right the version there is 2.0.something...

Boogerman

----- Original Message -----
From: "Francesco Samba/ML" <samba at colliniconsulting.it>
To: "Boogerman" <boogerman at interar.com.ar>
Cc: <samba at lists.samba.org>
Sent: Sunday, November 17, 2002 7:03 AM
Subject: Re: file locks problem??

>
> Hi Boogerman,
>
> thank you for the kind reply you gave me.
>
> Furthermore i would like to ask you if, with latest Samba version, do you
> still use the kernel oplocks, level2 oplocks and the oplocks options set
to
> NO.
>
> Thnk you again, bye.
>
>
>
> Boogerman writes:
>
> > I suggest you get the latest samba version.
> > I've been having similar problems with older versions, wich I solved
> > disabling kernel oplocks:
> >
> > kernel oplocks = no
> >
> > If that doesn't solve your problem, try also
> >
> > level2 oplocks = no
> > oplocks = no
> >
> > (note that this will reduce the performance since clients will no longer
be
> > able to cache files, so I suggest you get a newer samba/kernel)
> >
> > Boogerman
> >
> > ----- Original Message -----
> > From: "Francesco Samba/ML" <samba at colliniconsulting.it>
> > To: <samba at lists.samba.org>
> > Sent: Saturday, November 16, 2002 8:23 AM
> > Subject: [Samba] file locks problem??
> >
> >
> >> Hello,
> >>
> >> i am running Samba 2.2.3a on a Red Hat Linux 7.3 box with kernel
> > 2.4.18-10.
> >>
> >> I am experiencing some problems on a particular samba share, which is
> >> accessed by 10 Windows 98SE clients working on a COBOL production
packet
> > by
> >> mapping with a G: letters this samba folder.
> >>
> >> Well, some times a day it happens that this packed blocks because some
> > files
> >> on that samba folder remains locked; i also cannot browse this network
> > drive
> >> because, when arriving to these locked files, windows explorer crash.
> >>
> >> By viewing samba logs i see that, i think!, the problem could be
perhaps
> > in
> >> a oplocks problem?
> >>
> >> [2002/11/16 11:15:45, 0] smbd/open.c:open_mode_check(551)
> >>  open_mode_check: exlusive oplock left by process 20445 after break !
For
> >> file PROSYST/73002/73002DAT/SISTEMA, dev = 805, inode = 2588750.
Deleting
> > it
> >> to continue...
> >> [2002/11/16 11:15:45, 0] smbd/open.c:open_mode_check(555)
> >>  open_mode_check: Existent process 20445 left active oplock.
> >> [2002/11/16 11:15:45, 0] tdb/tdbutil.c:tdb_log(475)
> >>  tdb(/var/cache/samba/locking.tdb): tdb_lock failed on list 54 ltype=0
> >> (Interrupted system call)
> >> [2002/11/16 11:22:09, 0] smbd/oplock.c:request_oplock_break(981)
> >>  request_oplock_break: no response received to oplock break request to
pid
> >> 20445 on port 32964 for dev = 805, inode = 3326030, file_id = 95
> >> [2002/11/16 11:22:09, 0] smbd/open.c:open_mode_check(551)
> >>  open_mode_check: exlusive oplock left by process 20445 after break !
For
> >> file PROSYST/PRO02/SYSMENU.LOG, dev = 805, inode = 3326030. Deleting it
to
> >> continue...
> >> [2002/11/16 11:22:09, 0] smbd/open.c:open_mode_check(555)
> >>  open_mode_check: Existent process 20445 left active oplock.
> >> [2002/11/16 11:22:09, 0] smbd/oplock.c:oplock_break(758)
> >>  oplock_break: receive_smb error (Success)
> >>  oplock_break failed for file PROSYST/PRO02/SYSMENU.LOG (dev = 805,
inode
> > =
> >> 3326030, file_id = 95).
> >> [2002/11/16 11:22:09, 0] smbd/oplock.c:oplock_break(843)
> >>  oplock_break: client failure in break - shutting down this smbd.
> >> [2002/11/16 11:22:09, 0] tdb/tdbutil.c:tdb_log(475)
> >>  tdb(/var/cache/samba/locking.tdb): tdb_lock failed on list 24 ltype=1
> >> (Resource deadlock avoided)
> >> [2002/11/16 11:22:09, 0] tdb/tdbutil.c:tdb_log(475)
> >>  tdb(/var/cache/samba/locking.tdb): tdb_lock failed on list 24 ltype=0
> >> (Resource deadlock avoided)
> >> [2002/11/16 11:22:51, 0] smbd/oplock.c:request_oplock_break(981)
> >>  request_oplock_break: no response received to oplock break request to
pid
> >> 19083 on port 32927 for dev = 805, inode = 507948, file_id = 1856
> >> [2002/11/16 11:22:51, 0] smbd/open.c:open_mode_check(551)
> >>  open_mode_check: exlusive oplock left by process 19083 after break !
For
> >> file PROSYST/ISE02/ISE02DAT/NETUSER, dev = 805, inode = 507948.
Deleting
> > it
> >> to continue...
> >> [2002/11/16 11:22:51, 0] smbd/open.c:open_mode_check(555)
> >>  open_mode_check: Existent process 19083 left active oplock.
> >> [2002/11/16 11:23:14, 0]
> >> smbd/oplock_linux.c:linux_oplock_receive_message(135)
> >>  Invalid file descriptor 23 in kernel oplock break!
> >>
> >>
> >>
> >> The only way to repair this problem is restarting the SMB daemon.
> >>
> >> Could you please help me in order to solve this problem?
> >>
> >> Thank you again, best regards!
> >>
> >> Francesco Collini
> >> --
> >> To unsubscribe from this list go to the following URL and read the
> >> instructions:  http://lists.samba.org/mailman/listinfo/samba
> >>
> >>
> >
> >
>
>
>