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

Trond Myklebust
2003-02-24T17:07:32Z

>>>>> " " == Oleg Drokin <green@namesys.com> writes:

>> 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?

> 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?).

Cheers,
Trond