7 second pause when writing file using samba before it is read viaNFS

I use a server as a go-between between my Windows Vista desktop
machine and some of my linux development machines. The file server
has both a samba server for talking to the windows boxes, and an NFS
server for talking to the Linux boxes. Commonly I'll edit source using
the windows machine, and then try to compile it on the development
machines.

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'm not sure whether the problem is with the windows box, the server,
or the linux client. Any ideas?

Thanks,
Scott

Scott wrote:

> I use a server as a go-between between my Windows Vista desktop
> machine and some of my linux development machines. The file server
> has both a samba server for talking to the windows boxes, and an NFS
> server for talking to the Linux boxes. Commonly I'll edit source using
> the windows machine, and then try to compile it on the development
> machines.
>
> 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'm not sure whether the problem is with the windows box, the server,
> or the linux client. Any ideas?
>
> Thanks,
> Scott


I'm afraid micoshaft developers have been ordered to fsck with Samba
and like good little bum boys, they have obeyed micoshaft managements
instead of taking them to court over it for anti-competitive monopoly
practices.

You might be able to google and find the flag that needs to be set
so that equal priority is given between windummy guests and samba
guests. This flag is deliberately set so as not to give samba connections
high priority over windummy clients.

Just to be sure, you should be able to verify it by logging into
another samba server (a Linux one) and checking your
file transfer speeds. Linux to Linux samba has astronomical speed.

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