From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Oleg Drokin <green@namesys.com>
Cc: Andrew Morton <akpm@digeo.com>,
vs@namesys.com, nikita@namesys.com, jaharkes@cs.cmu.edu,
linux-kernel@vger.kernel.org
Subject: Re: 2.4 iget5_locked port attempt to 2.4 (supposedly fixed NFS version this time)
Date: Mon, 24 Feb 2003 18:33:33 +0100 [thread overview]
Message-ID: <15962.22381.294644.724830@charged.uio.no> (raw)
In-Reply-To: <20030224202619.A18641@namesys.com>
>>>>> " " == 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
next prev parent reply other threads:[~2003-02-24 17:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030220175309.A23616@namesys.com>
[not found] ` <20030220154924.7171cbd7.akpm@digeo.com>
2003-02-21 19:03 ` 2.4 iget5_locked port attempt to 2.4 Oleg Drokin
2003-02-21 20:04 ` Jan Harkes
2003-02-22 9:29 ` Oleg Drokin
2003-02-24 10:21 ` 2.4 iget5_locked port attempt to 2.4 (supposedly fixed NFS version this time) Oleg Drokin
2003-02-24 16:50 ` Trond Myklebust
2003-02-24 17:02 ` Trond Myklebust
2003-02-24 17:03 ` Oleg Drokin
2003-02-24 17:17 ` Trond Myklebust
2003-02-24 17:26 ` Oleg Drokin
2003-02-24 17:33 ` Trond Myklebust [this message]
2003-02-24 17:38 ` Oleg Drokin
2003-03-03 14:09 ` 2.4 iget5_locked port attempt to 2.4 Oleg Drokin
2003-03-03 16:25 ` Alan Cox
2003-03-03 15:35 ` Nikita Danilov
2003-03-03 15:38 ` Oleg Drokin
2003-03-03 15:57 ` Anton Altaparmakov
2003-03-03 16:04 ` Oleg Drokin
2003-03-03 16:27 ` Anton Altaparmakov
2003-03-03 16:45 ` Oleg Drokin
2003-03-03 16:50 ` Jan Harkes
2003-03-03 16:57 ` Oleg Drokin
2003-03-03 17:23 ` Jan Harkes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15962.22381.294644.724830@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@digeo.com \
--cc=green@namesys.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@namesys.com \
--cc=vs@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox