[Samba] 3.0.13 - word cannot complete the save due to a file permission error. for smb/NFS mounted dirs

[Jeremy Allison]

On Mon, Apr 11, 2005 at 11:39:35AM +0100, Urs Rau wrote:
> I am using 3.0.13 and have temporarily run out of disk space on the main 
> samba server, so I have NFS mounted some space from another machine. 
> into a directory that is accessible under samba.
> 
> When I try to save directly from ms word 2003 sp1 (and same from word 
> 2000) it tells me:
> 
> on the win98se and win xp pro sp2 clients:
> 
> "Microsoft Office Word"
> Word cannot complete the save due to a file permission error.
> (I:\transfer\ursr\chidren\2005.doc)
> 
> and on the server it logs
> 
> [2005/04/11 11:03:06, 0] locking/posix.c:posix_fcntl_lock(659)
>   on 32 bit NFS mounted file systems.
> [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(657)
>   posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 
> 1 returned
> [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(658)
>   an No locks available error. This can happen when using 64 bit lock 
> offsets
> [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(659)
>   on 32 bit NFS mounted file systems.
> 
> Now, this does sound a bit as if this was/is expected to go wrong. But 
> if I save my document locally and then copy it with the same name and to 
> the same dir on the server there is no issue.
> 
> Is there anything I can do from the samba server to avoid this error? As 
> from a unix perspective there is no permissions problem.

If your nfs locking is broken you can add "strict locking = no" to the
share definition exporting that part of the filesystem. That will prevent
locking from occurring on read/write access. If it's still failing (and
the nfs locking is *really* broken :-) you can add "locking = no" to
the share definition. But that risks file corruption.

Jeremy.