[Samba] Strange Problem with Access

[Sanjiv Bawa]

Is it trying to place a lock on the .LDB file and failing?

Can you post your log file messages, if any?

They should be in /var/log/messages or /var/log/samba/log.{machine}

Thanks.

-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]On
Behalf Of Bill Moran
Sent: Tuesday, March 05, 2002 9:15 PM
To: Ruben Fagundo
Cc: samba at lists.samba.org; tiuzzol at MIT.EDU
Subject: Re: [Samba] Strange Problem with Access


Ruben Fagundo wrote:

>
>
> I would like to pose the following problem to this mailing list to see
> if any of you have any suggestions you may offer.
>
> 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.


Sounds like oplock problems (possibly)
Try turning off oplocks on the Samba server and see if the problem
disappears.
The Windows 9X line has a lot of known bugs with regard to oplocks, and
file-based databases (such as Access) tend to find these problems more often
than other types of file access.  You can also look at the "veto
oplocks" feature
to disable oplocking only on .mdb files.

>


--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba