[Samba] smb + nfs lock problem
Jehan.Procaccia at int-evry.fr
Thu Nov 23 16:54:37 GMT 2006
If found a solution , but I'am not sure of the consequences ...
I added in /etc/samba/smb.conf
lock directory = /var/lock/samba
locking = yes
strict locking = no
Is it the recommended solution ?
Jehan PROCACCIA wrote:
> whenever I try to copy a new file from windowsXP (2K also) to a samba
> share which is NFS mounted on the samba server, I get an error on the
> client: "impossible to copy file.txt: the process cannot access the
> file because an other process has locked a part of it" (my english
> translation of the french message I have !)
> It worked fine before (3weeks ago) and I think that problem appeared
> when I upgraded my NFS server, because the samba server running
> directly on that NFS server work fine (no lock pb) ,
> I tried looking through samba locking mechanisms, but I'am a bit lost
> in there:
> I blindly tested
> veto oplock files = /filename.htm/*.txt/
> kernel oplocks = yes
> with no success !
> Do you have an idea ? is it a samba problem ? an NFS problem ? a
> windows client problem ?
> I've got undred of users "locked" :-(
> Thanks .
> Here's my samba server system config:
> bash-3.00# cat /etc/redhat-release
> Fedora Core release 4 (Stentz)
> bash-3.00# rpm -qa | grep samba
> bash-3.00# uname -a
> Linux fpublic.int-evry.fr 2.6.17-1.2147_FC4.vs220.127.116.11 #1 Thu Sep 14
> 22:30:50 EDT 2006 i686 i686 i386 GNU/Linux
> here's the NFS server config on wich samba works fine (local disk
> access !)
> $ cat /etc/redhat-release
> Red Hat Enterprise Linux ES release 4 (Nahant Update 4)
More information about the samba