On May 5, 4:33 pm, Scott <smba...@gmail.com> wrote:

> There is an annoying pause of about 7 seconds when I write a file
> using samba before it can be read using NFS. This happens reliably
> every time I write to a file. The Linux box that is trying to read
> the file blocks for these 7 seconds.

I think the machine using Samba knows that it is the only user of the
file and grabs an oplock to allow it to manipulate the file remotely
without having to synch back to the server. When the NFS client
accesses the file, the oplock has to be revoked, the other client's
buffer flushed, and so on.

One solution may be the "veto oplock files" option in the 'smb.conf'
file. This should convince the Samba client to make its writes
immediately, without a lock, instead of buffering them.

DS