Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 13 Feb 2003 10:35:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 13 Feb 2003 10:35:44 -0500 Received: from mons.uio.no ([129.240.130.14]:47812 "EHLO mons.uio.no") by vger.kernel.org with ESMTP id ; Thu, 13 Feb 2003 10:35:44 -0500 To: Dave Jones Cc: Linux Kernel Subject: Re: 2.5.60 NFS FSX References: <20030213152742.GA1560@codemonkey.org.uk> From: Trond Myklebust Date: 13 Feb 2003 16:45:27 +0100 In-Reply-To: <20030213152742.GA1560@codemonkey.org.uk> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1051 Lines: 23 >>>>> " " == Dave Jones writes: > 2.5.60's NFS seems to have various issues. (2.5.60 client, > 2.4.21pre3 server) > - I ran an fsx and an fsstress in parallel. > Client rebooted after 2-3 minutes. I know. There's memory corruption going on somewhere, but I'm not sure exactly where. > - fsx on its own, after quite a while, this happens.. Also known. It's a bit odd really: the reads fail due to some form of corruption, but the writes are OK. Means that when you later come to compare the '.fsxgood' file to the 'bad' file, then things look OK. I'm a bit confused w.r.t. both these issues. Neither occur on the 2.4.x platform despite the fact that the code is more or less the same. This is why I suspect an IPv4 socket problem. 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/