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

Trond Myklebust
2003-02-24T17:23:33Z

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

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

...and there were no accompanying messages logged by syslog? In
principle the NFS client is always supposed to supply an error message
when it generates an EIO.

Cheers,
Trond