Alan Cox wrote:
> > The NFS clients are getting
> > "Stale NFS handle"
> > messages every once in a while which will make a "touch somefile.o"
> > fail.
>
> If they have the previous .o handle cached and it was removed on another
> client thats quite reasonable behaviour. NFS isnt coherent
As r
> " " == stergaard writes:
> What happens is that one machine will finish compiling, and
> another machine will immediately thereafter do a "touch
> some_output.o". This "touch" sometimes fails with a stale
> handle message.
Does the appended patch change anything?
Che
On Tue, Feb 13, 2001 at 11:31:50PM +, Alan Cox wrote:
> > The NFS clients are getting
> > "Stale NFS handle"
> > messages every once in a while which will make a "touch somefile.o"
> > fail.
>
> If they have the previous .o handle cached and it was removed on another
> client thats quite rea
> The NFS clients are getting
> "Stale NFS handle"
> messages every once in a while which will make a "touch somefile.o"
> fail.
If they have the previous .o handle cached and it was removed on another
client thats quite reasonable behaviour. NFS isnt coherent
> It's quite annoying and I didn't
Hi !
I'm running a compilation cluster with various machines now
on 2.4.1 all mounting the same home filesystem over NFS from
the central NFS server.
All machines are 2.4.1 using NFSv3, some SMP some UP.
NFS server is a dual running an SMP kernel
The NFS clients are getting
"Stale NFS handle
5 matches
Mail list logo