MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16065.12944.741393.595356@charged.uio.no>
Date: Tue, 13 May 2003 19:59:44 +0200
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6 must-fix list, v2
In-Reply-To: <20030513173801.GA2763@suse.de>
References: <20030512155417.67a9fdec.akpm@digeo.com>
	<20030512155511.21fb1652.akpm@digeo.com>
	<shswugvjcy9.fsf@charged.uio.no>
	<20030513135756.GA676@suse.de>
	<16065.3159.768256.81302@charged.uio.no>
	<20030513152228.GA4388@suse.de>
	<16065.4109.129542.777460@charged.uio.no>
	<20030513154741.GA4511@suse.de>
	<16065.5911.55131.430734@charged.uio.no>
	<20030513173801.GA2763@suse.de>
Reply-To: trond.myklebust@fys.uio.no
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1047
Lines: 25

>>>>> " " == Dave Jones <davej@codemonkey.org.uk> writes:

     > On Tue, May 13, 2003 at 06:02:31PM +0200, Trond Myklebust
     > wrote:
    >> Then I'm confused as to what you are saying. Are we talking
    >> about a full NFS server crash or just a temporary 'server not
    >> responding' situation? Does NFS over TCP fix it, for instance?

     > Just to keep you busy..  I had thought NFS over TCP fixed
     > it. It rang for a lot longer (around 50 minutes), and then did
     > the following..  Looks like a different bug to my untrained
     > eye.

Nah. Looks like the same thing: mmapped writes followed by truncate.
TCP is likely to change the timings a bit (reliable transport means
that the race between out-of-order write and truncate is smaller, but
it is still there.

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/