This is a discussion on Re: SAMBA & ISAM Databases - Samba ; Have you tried using the CIFS vfs instead of smbfs? Just a guess, but it may be worth trying. If the Windows clients are seeing and respecting the locks then I have to assume that Samba is handling them correctly. ...
Have you tried using the CIFS vfs instead of smbfs?
Just a guess, but it may be worth trying. If the Windows clients are
seeing and respecting the locks then I have to assume that Samba is
handling them correctly. The different piece, then, is the client on the
Another test worth trying would be to mount the directory on the Linux
clients using NFS instead of SMB. I'd test that configuration heavily
before going live with it, but it would provide some interesting
On Tue, Sep 14, 2004 at 10:23:09AM +0200, Pepe Guimarães wrote:
> I have a heterogeneous network with a R.H. Linux server running Samba
> 3.0.5 and various
> Win clients (from Win 98 to Win XP Pro). On a Samba share I have an ISAM
> database (Access, FoxPro etc. like)
> that is being accessed by applications running on the Win clients and by
> applications running in Linux.
> I have disabled "opplocks" in both Win9x clients and on the Samba share.
> I have "mounted" the Samba share on the Linux server so that Linux
> applications are "pathed"
> to the share and accessing the data there.
> The problem arises with locks. Files locked by the Win clients are
> seeing as locked by Win
> clients but not by Linux and viceversa.
> Any solution for this?
> I have "played" with options in Samba (level2 oplocks, veto oplocks,
> kernel oplocks, etc.) without any improvements. One thing that I have
> clear is oplocks = no.
> Other parameters we have tried:
> To be more specific:
> Network name for Linux machine: pepe
> Name of Samba share (as seen by Win clients) : testdata
> Directory where data is on linux machine : /u/testdata
> Thus data can be accessed by: //pepe/testdata
> Mount point for Samba share in Linux: /
> Comand given to mount Samba share:
> mount -t smbfs -o username=whatever,password=key //pepe/testdata
> Checked mounting with:
> gives me : //pepe/testdata mounted on /testdata type smbfs (o) <---
> By the way: what means the (o)?
> Then I make the paths to access the data from Linux to be /testdata and
> fron win clients to be //pepe/testdata
> Can you see anything wrong?
> Tests I am going to make are:
> 1-Modify the name of the Samba share so that "share name <> name linux
> 2-Mount the Samba share at another point rather than /
> 3-Try to access the data from Linux with the same full path as Win
> clients. In the above case //pepe/testdata rather than /testdata
> shouldn't "posix locking = yes" in smb.conf give consistent locking
> between SMB and posix (NFS or local) access?
> José Guimarães [ email@example.com ]
> Moose Software
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/ -)----- firstname.lastname@example.org
OnLineBook -- http://ubiqx.org/cifs/ -)----- email@example.com