Just upgraded Saturday from Ubuntu 7.10 to 8.04.01. File locking in Samba is now broken, meaning two different users can have the same file open at the same time and edit it. Server is RedHat 9.0 running Samba 2.2.7a-security-rollup-fix. This has been working well for us for several years. Have one WinXP box accessing the server using OOo 2.0. Have another couple of Win95 boxes. In addition, have one Ubunutu 6.06 box, and three other 8.04 boxes. It appears the XP and the 6.06 box lock files so the other cannot edit them while one has them open, but the 8.04 boxes, running OOo 2.4 can access and edit and save these files, thus causing havoc. The linux clients mount via cifs, such as this line from /etc/fstab: //samba1/vol22 /sam/vol22 cifs rw,user,credentials=/[blanked],uid=doug,gid=data 0 0 This is a production environment. Could it be a mis-match between the version of samba on the server and the one on the clients? Can anybody suggest a solution or at least a trouble-shooting procedure? Thanks! :- Doug.
On Tue, Aug 05, 2008 at 12:50:42AM +0000, Doug Germann wrote:> Just upgraded Saturday from Ubuntu 7.10 to 8.04.01. File locking in Samba is now > broken, meaning two different users can have the same file open at the same time > and edit it. > > Server is RedHat 9.0 running Samba 2.2.7a-security-rollup-fix. This has been > working well for us for several years. Have one WinXP box accessing the server > using OOo 2.0. Have another couple of Win95 boxes. > > In addition, have one Ubunutu 6.06 box, and three other 8.04 boxes. > > It appears the XP and the 6.06 box lock files so the other cannot edit them > while one has them open, but the 8.04 boxes, running OOo 2.4 can access and edit > and save these files, thus causing havoc. > > The linux clients mount via cifs, such as this line from /etc/fstab: > //samba1/vol22 /sam/vol22 cifs > rw,user,credentials=/[blanked],uid=doug,gid=data 0 0 > > > This is a production environment. > > Could it be a mis-match between the version of samba on the server and the one > on the clients? > > Can anybody suggest a solution or at least a trouble-shooting procedure?Normally what you call "file locking" in this case is really access exclusion ie. share modes. Use smbstatus on the server to see what open modes the clients are currently using. Jeremy.
On Tue, Aug 12, 2008 at 10:21:56PM -0400, douglas germann wrote:> Jeremy-- > > Thanks! Had not thought of using smbstatus. > > What is happening is that the Ubuntu clients are establishing a lock of > deny_none, and the WinXP client is establishing deny_write. > > I have tried changing oplocks and kernel oplocks to yes, and all else to > the defaults shown here, but there is no change in this behavior: > http://www.physiol.ox.ac.uk/Computing/Online_Documentation/using_samba/ch05_05.htmll > > What else should I try, please?Ok, deny_none should conflict with deny_write, so you should see "someone else has this file open" between WinXP and the Ubuntu clients. However, for UNIX clients they need to provide mutual exclusion using byte range locks (the traditional UNIX way) not deny modes. I'm not sure if OpenOffice on Ubuntu does this (it should). Jeremy.