We recently changed our fileserver setup and are in the middle of moving everything over to a new server. During the move both server should provide the same shares so we chose to mount the shares via NFS on the new server and then export it through samba (3.2.3-0.1-1882-SUSE-SL11.0).
This works fine for just about anything but it breaks for Microsoft Office Products running under Windows XP SP3 (SP2 is fine) or Windows Vista. The Office products complain, that the file is already opened by someone else.
As a workaround we set posix locking = no for all shares and it works fine now.
But as the manpage said "You should never need to disable this parameter." we thought we'd report this.
I have the same issues (although only with XP SP3 and Office 2003, Vista and Office 2007 work just fine as do XP SP3 and Office 2007).
Reexport NFS-mounted filesystems are -- according to Volker Lendecke -- unsupported:
I contacted Dirk Kastens -- the original reporter -- some months ago; he still has "posix locking" disabled which is a fine solution for him (see http://lists.samba.org/archive/samba/2008-June/141212.html and the following).
As I need cross-server locking and stuff like that I cannot go that way. "My" solution is not to use Office 2003 in combination with XP-SP3 or Vista.
PS: I'd like to vote on this bug/feature if only I could... ;-)
I really do wonder how you make Microsoft Office use of NFS locks.
actually not Office should use NFS locks but Samba.
In my setup several data servers use cross-mounted disk drives (via NFS) an reexport those via Samba. So I'd like "Server B" to notify users when they try to open an Office document that has already been opened -- no matter if it has been opened via "Server A" or "Server B" and no matter on which of the disks involved it is actually stored.
And what I can say from using such a setup for some years now (actually from mid 2002 on) is that it used to work just fine up to Win XP SP3 with Office 2003.
With "posix locking" disabled notifications do work -- but not cross-server anymore.
So you are exporting the same file space via two different Samba instances? That's even less supported than re-exporting an imported NFS share, that's the configuration that took us years to get right with clustered Samba.
Volker, should this bug report be closed as invalid?
Please look at ctdb.samba.org. Using that it will work. Closing the bug as worksforme. It does, but with a different configuration.