Re: 2.4 iget5_locked port attempt to 2.4 (supposedly fixed NFS version this time)

Oleg Drokin
2003-02-24T17:16:10Z

Hello!

On Mon, Feb 24, 2003 at 06:17:30PM +0100, Trond Myklebust wrote:
> >> like that keeps turning the clock backward on the server, then
> >> the NFS client has no chance of recognizing which attribute
> >> updates are the more recent ones.
> > Ok, I stopped ntpd. Will see what will happen. ;) Aha, it died
> > already: doread: read: Input/output error
> Silly question: Are you perhaps testing using the 'soft' mount option?

Hm. I just mount it as
mount server:/tmp /mnt -t nfs
no extra options. So I guess no, I do not have wthis soft stuff.

> > How about that "RPC request reserved 1144 but used 4024" alike
> > stuff"?
> Sounds like Neil made another accounting error in the server code
> 8-). Can you try to check on which type of request it occurs (readdir,
> read, readlink?).

Ok. Will try (I guess I need to do this on latest 2.4 kernel anyway.
(my nfs server is running 2.4.20)).

Bye,
Oleg