[Samba] Common MS Office and samba file share issue - Samba

This is a discussion on [Samba] Common MS Office and samba file share issue - Samba ; 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 ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: [Samba] Common MS Office and samba file share issue

  1. [Samba] 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
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  2. Re: [Samba] Common MS Office and samba file share issue

    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.
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  3. Re: [Samba] Common MS Office and samba file share issue

    On Tue, Jul 8, 2008 at 8:14 PM, 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
    >

    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
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  4. Re: [Samba] Common MS Office and samba file share issue

    Jeremy Allison wrote:
    > 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.


    Thanks Jeremy,

    Not intentionally mostly because I don't know how but I guess upgrading
    to 3.0.30 would fix it either way.

    Can you suggest a good source of info on the ACLs with Samba topic?

    Thanks again

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

  5. Re: [Samba] Common MS Office and samba file share issue

    John Drescher wrote:
    > On Tue, Jul 8, 2008 at 8:14 PM, 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
    >>

    > 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

    Thanks John,

    I have those options set on each share as create mode = 0660 and
    directory mode = 0770. I tried adding 'force' to those lines but the
    problem appeared to get worse. Is the 'force keyword important or is
    this two ways of saying the same thing and any change was purely
    coincidental?

    many thanks

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

  6. Re: [Samba] Common MS Office and samba file share issue

    Kevin Bedford wrote:
    > Jeremy Allison wrote:
    >> 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.

    >
    > Thanks Jeremy,
    >
    > Not intentionally mostly because I don't know how but I guess
    > upgrading to 3.0.30 would fix it either way.
    >
    > Can you suggest a good source of info on the ACLs with Samba topic?
    >
    > Thanks again
    >
    > Kevin



    Set force security mode = 0770 in the problematic share. This fix the
    bug... at least, works for me.
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  7. Re: [Samba] Common MS Office and samba file share issue

    > Set force security mode = 0770 in the problematic share. This fix the
    > bug... at least, works for me.
    > --


    I am sorry I was not sure of the exact params since I am not at work
    and will not be back till Monday. Anyways for what I remember this
    behavior started happening in a samba version between 3.0.14 to 3.0.24
    and forcing the security modes with 2770 fixed the problem. At that
    time I was not using acls at all. Now I am using 3.0.30 and 3.0.28a
    with acls and still I have the forced security on public and private
    folders.

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

  8. Re: [Samba] Common MS Office and samba file share issue

    John Drescher wrote:
    >> Set force security mode = 0770 in the problematic share. This fix the
    >> bug... at least, works for me.
    >> --

    >
    > I am sorry I was not sure of the exact params since I am not at work
    > and will not be back till Monday. Anyways for what I remember this
    > behavior started happening in a samba version between 3.0.14 to 3.0.24
    > and forcing the security modes with 2770 fixed the problem. At that
    > time I was not using acls at all. Now I am using 3.0.30 and 3.0.28a
    > with acls and still I have the forced security on public and private
    > folders.
    >
    > John

    Thanks John I've added that in place of the create mode and directory
    mode settings and will upgrade from 3.0.25c to 3.0.30 tonight.

    Thanks again

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

  9. Re: [Samba] Common MS Office and samba file share issue


    Jeremy Allison wrote:
    >
    > 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.
    >


    Why isn't there anything in the 3.0.30 changelog regarding this? It
    sounds like a major improvement.

    -Brian

    --
    ---------------------------------------------------
    Brian H. Nelson Youngstown State University
    System Administrator Media and Academic Computing
    bnelson[at]cis.ysu.edu
    ---------------------------------------------------

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

+ Reply to Thread