Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S265708AbTBXRXd>; Mon, 24 Feb 2003 12:23:33 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S266323AbTBXRXd>; Mon, 24 Feb 2003 12:23:33 -0500
Received: from pat.uio.no ([129.240.130.16]:16117 "EHLO pat.uio.no")
	by vger.kernel.org with ESMTP id <S265708AbTBXRXc>;
	Mon, 24 Feb 2003 12:23:32 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15962.22381.294644.724830@charged.uio.no>
Date: Mon, 24 Feb 2003 18:33:33 +0100
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)
In-Reply-To: <20030224202619.A18641@namesys.com>
References: <20030220175309.A23616@namesys.com>
	<20030220154924.7171cbd7.akpm@digeo.com>
	<20030221220341.A9325@namesys.com>
	<20030221200440.GA23699@delft.aura.cs.cmu.edu>
	<20030224132145.A7399@namesys.com>
	<15962.19783.182617.822504@charged.uio.no>
	<20030224200323.A18408@namesys.com>
	<15962.21418.869267.676983@charged.uio.no>
	<20030224202619.A18641@namesys.com>
X-Mailer: VM 7.07 under 21.4 (patch 8) "Honest Recruiter" XEmacs Lucid
Reply-To: trond.myklebust@fys.uio.no
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1092
Lines: 26

>>>>> " " == 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/