samba - Jul 2008 - Common MS Office and samba file share issue

Hi all,

There are many posts on many lists about this issue but no definitive 
answers.

For me the issue came up with a new server running CentOS 5 + samba 
3.0.35c + openldap.

The recent postings I've seen always seem to have either RHEL 5 or 
CentOS 5 in common with the provided 2.6.18 kernel.

The issue is .doc or .xls files saving and then producing an error about 
not being able to open the file for writing.  Then it claims the file is 
locked by the user who just saved the file.  It even occurs in users own 
home directories where no one else could have opened the file

I've tried disabling kernel locks, oplocks, level2 oplocks, create mode 
=0660 and
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 
SO_SNDBUF=8192

All of which have been listed somewhere as fixes but do not help.  I've 
been searching for a solution for nearly two months now.

Can someone please tell me what it is????


Thanks in advance

Kevin Bedford

On Wed, Jul 09, 2008 at 10:14:23AM +1000, Kevin Bedford
wrote:
> Hi all,
> 
> There are many posts on many lists about this issue but no definitive 
> answers.
> 
> For me the issue came up with a new server running CentOS 5 + samba 
> 3.0.35c + openldap.
> 
> The recent postings I've seen always seem to have either RHEL 5 or 
> CentOS 5 in common with the provided 2.6.18 kernel.
> 
> The issue is .doc or .xls files saving and then producing an error about 
> not being able to open the file for writing.  Then it claims the file is 
> locked by the user who just saved the file.  It even occurs in users own 
> home directories where no one else could have opened the file
> 
> I've tried disabling kernel locks, oplocks, level2 oplocks, create mode
> =0660 and
> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 
> SO_SNDBUF=8192
> 
> All of which have been listed somewhere as fixes but do not help.  I've
> been searching for a solution for nearly two months now.
> 
> Can someone please tell me what it is????
Are you using ACLs on the drive ? If so, this is a bug with ACL
inheritance I've fixed for 3.0.30. Thanks

Jeremy.

On Tue, Jul 8, 2008 at 8:14 PM, Kevin Bedford <kevin@sepit.com.au>
wrote:
> Hi all,
>
> There are many posts on many lists about this issue but no definitive
> answers.
>
> For me the issue came up with a new server running CentOS 5 + samba 3.0.35c
> + openldap.
>
> The recent postings I've seen always seem to have either RHEL 5 or
CentOS 5
> in common with the provided 2.6.18 kernel.
>
> The issue is .doc or .xls files saving and then producing an error about
not
> being able to open the file for writing.  Then it claims the file is locked
> by the user who just saved the file.  It even occurs in users own home
> directories where no one else could have opened the file
>
> I've tried disabling kernel locks, oplocks, level2 oplocks, create mode
> =0660 and
> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192
> SO_SNDBUF=8192
>
Disable any socket options on 2.6 kernels as the os handles this
better.
>
> All of which have been listed somewhere as fixes but do not help.  I've
been
> searching for a solution for nearly two months now.
>
> Can someone please tell me what it is????
The problem is instead of saving a file excel and word create new
files with a temp name then delete the old file then rename the new
file to the same name as the old. When this rename takes place the
windows filesystems apply the permissions of the old file to the new
file. The problem is linux filesystems do not do this weird behavior
so with samba you have to force it using the force create mode param
and force directory mode param.

John

Il 9-07-2008 2:14, Kevin Bedford ha scritto:
> The issue is .doc or .xls files saving and then producing an error about 
> not being able to open the file for writing.  Then it claims the file is 
> locked by the user who just saved the file.  It even occurs in users own 
> home directories where no one else could have opened the file
Are you sure you aren't talking about this Excel bug?
http://support.microsoft.com/?scid=kb%3Ben-us%3B324491&x=14&y=13

-- 
Ciao,
   Marco.