[Samba] Fwd: Strange Problem with Access

[Sanjiv Bawa]

Can you try turning off all oplocks altogether.

kernel oplocks
level2 oplocks
oplocks
should all be no.

Then see if you have the problem. They recently discovered another bug in
oplock code which is due to be fixed in the next version.

Pls. do provide an update. I am very interested in this issue.

Thanks.

-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]On
Behalf Of Ruben Fagundo
Sent: Wednesday, April 10, 2002 12:06 PM
To: samba at lists.samba.org
Subject: [Samba] Fwd: Strange Problem with Access


I replaced the NIC card on one of the machines having the problem I just
mentioned below, and the problem still persists.  I don't know if the size
of the database has anything to do with this, but the DB is over 10Meg.

If anyone has any other suggestions, I'm all ears.  Also, I have attached
the results of smbstatus.

Regards,
Ruben


Script started on Tue Apr 9 18:03:42 2002
[rubenf at dorchester ~]$ smbstatus
Samba version 2.2.3a
Service uid gid pid machine
----------------------------------------------
public johnensor users 3408 johnensor (192.168.1.104) Sat Apr 6 11:23:45
2002
rubenf rubenf adm 10173 volunteer (192.168.1.103) Tue Apr 9 17:47:34 2002
public rubenf adm 10173 volunteer (192.168.1.103) Tue Apr 9 17:47:34 2002
applicatio marilyn users 10056 damascus (192.168.1.106) Tue Apr 9 12:36:12
2002
applicatio johnensor users 3408 johnensor (192.168.1.104) Sat Apr 6
11:23:45 2002
marilyn marilyn users 10056 damascus (192.168.1.106) Tue Apr 9 12:36:11 2002
johnensor johnensor users 3408 johnensor (192.168.1.104) Sat Apr 6 11:23:45
2002
applicatio rubenf adm 10173 volunteer (192.168.1.103) Tue Apr 9 17:47:34
2002
public karen adm 9953 karen (192.168.1.101) Tue Apr 9 09:39:18 2002
public marilyn users 10056 damascus (192.168.1.106) Tue Apr 9 12:36:11 2002
Locked files:
Pid DenyMode R/W Oplock Name
--------------------------------------------------
3408 DENY_NONE RDWR NONE /home/apps/public/Donor database and letters/AWC
Supporters.mdb Tue Apr 9 17:29:25 2002
9953 DENY_NONE RDWR NONE /home/apps/public/Donor database and letters/AWC
Supporters.mdb Tue Apr 9 09:39:20 2002
10173 DENY_WRITE RDONLY EXCLUSIVE+BATCH
/home/apps/shared-apps/ssh_putty.exe Tue Apr 9 18:02:33 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH
/home/apps/shared-apps/win-rar250.exe Tue Apr 9 17:58:56 2002
10056 DENY_WRITE RDWR EXCLUSIVE+BATCH /home/users/marilyn/eudora/EUDORA.INI
Tue Apr 9 16:25:55 2002
10056 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/users/marilyn/eudora/In.toc
Tue Apr 9 16:45:59 2002
10056 DENY_WRITE RDONLY EXCLUSIVE+BATCH
/home/users/marilyn/eudora/Plugins/unwrap32.dll Tue Apr 9 16:25:56 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH
/home/apps/shared-apps/winzip32v63.exe Tue Apr 9 17:58:56 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/apps/public/Shortcut to
marilyn.lnk Tue Apr 9 18:00:15 2002
10056 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/users/marilyn/eudora/In.mbx
Tue Apr 9 16:28:47 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/apps/shared-apps/usr-wiza.exe
Tue Apr 9 17:58:56 2002
10056 DENY_NONE WRONLY EXCLUSIVE+BATCH
/home/users/marilyn/eudora/eudora.log Tue Apr 9 17:45:59 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/apps/public/Office forms.lnk
Tue Apr 9 18:00:15 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/apps/shared-apps/x-win41.exe
Tue Apr 9 17:58:56 2002
3408 DENY_NONE RDWR NONE /home/apps/public/Donor database and letters/AWC
Supporters.ldb Tue Apr 9 17:29:25 2002
9953 DENY_NONE RDWR NONE /home/apps/public/Donor database and letters/AWC
Supporters.ldb Tue Apr 9 09:39:21 2002
10056 DENY_WRITE RDONLY EXCLUSIVE+BATCH
/home/users/marilyn/eudora/Plugins/PureVoice32.dll Tue Apr 9 16:25:56 2002
10056 DENY_WRITE RDONLY EXCLUSIVE+BATCH
/home/users/marilyn/eudora/Plugins/Sort32.dll Tue Apr 9 16:25:56 2002
3408 DENY_WRITE RDONLY NONE /home/users/johnensor/eudora/EuShlExt.dll Sat
Apr 6 13:01:56 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/apps/public/Shortcut to
Statistics.lnk Tue Apr 9 18:00:15 2002
10056 DENY_WRITE RDONLY EXCLUSIVE+BATCH
/home/users/marilyn/eudora/Plugins/UprLwr32.dll Tue Apr 9 16:25:56 2002
10173 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/apps/shared-apps/winamp264.exe
Tue Apr 9 17:58:56 2002
10056 DENY_NONE RDWR EXCLUSIVE+BATCH /home/users/marilyn/eudora/OWNER.LOK
Tue Apr 9 16:25:58 2002
[rubenf at dorchester ~]$ exit
exit
Script done on Tue Apr 9 18:03:48 2002

>Date: Mon, 08 Apr 2002 17:51:21 -0400
>To: samba at lists.samba.org
>From: Ruben Fagundo <rfagundo at npv.com>
>Subject: Strange Problem with Access
>
>
>I posed the following problem a few weeks ago, and finally, I've had time
>to update the RPM for the latest samba Version 2.2.3a
>
>I added the following line to [global]
>
>veto oplock files = /*.mdb/*.MDB/*.ldb/
>
>And the following line to the directory having problems.
>
>  [public]
>    locking = yes
>    oplocks = yes
>    veto oplock files = /*.mdb/*.MDB/*.ldb/
>
>I am still having problems opening the Access database from certain
>computers.  All other systems are working perfectly fine.  There is no
>correlation to the version of Windows opening the database.  If anyone has
>any more suggestions, I would really love to hear them.  The orginial
>problem description is listed below.  And a more detailed log file is
>attached.  The file experiencing problems is called
>
>"AWC Supporters.mdb"
>
>The irony of all this is that this was all working perfectly fine with
>Redhat 5.2
>
>=================================================
>
>I am running samba on a RedHat 7.2 Athalon box with software RAID 0 dual
>IDE disks on an ext3 filesystem.
>
>I have several users in a large community of users that are always hitting
>the samba server.  The machine has been consistently reliable with one
>exception.  There is a particularly large MS Access Database (10Meg) that
>everyone likes to use.  A problem has developed from certain Win 98 and
>Win95 computers where users get an error message saying that someone
>currently has a lock on the database, and that it cannot be
>opened.  However, smbstatus, reports that the user is actually trying to
>establish a lock on a different file, not the database in question.  To
>add to the strangeness, I have opened the database on a different
>computer, and then all of a sudden everyone else can now open it as
>well.  In addition to that, I had the database open from a win 98 machine,
>and someone else (that had been experiencing problems) opened it up, but
>smbstatus reports that the 2nd individual had a second file open in
>addition to the database, and clearly there were no other files open on
>that computer, by that user.  So, we have files opening and getting locked
>when they were not opened, and a database that only certain users can
>open, cause other computers are being told that it is already open, and
>locked by a different user.
>
>Can anyone tell me what the heck is going on here, and what is the answer
>to this apparent lunacy ???
>
>Thanks,
>Ruben