From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 16 Dec 2001 20:48:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 16 Dec 2001 20:47:51 -0500 Received: from mons.uio.no ([129.240.130.14]:13957 "EHLO mons.uio.no") by vger.kernel.org with ESMTP id ; Sun, 16 Dec 2001 20:47:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15389.20155.378980.692209@charged.uio.no> Date: Mon, 17 Dec 2001 02:47:39 +0100 To: Dave Jones Cc: Linux Kernel Subject: Re: More fun with fsx. In-Reply-To: In-Reply-To: <15389.19300.179304.433697@charged.uio.no> X-Mailer: VM 6.92 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: trond.myklebust@fys.uio.no From: Trond Myklebust Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>>>> " " == Dave Jones writes: > The only stuff that looks related is... > call_verify: server accept status: 2 call_verify: server accept > status: 2 call_verify: server accept status: 2 RPC: garbage, > exit EIO nfs_get_root: getattr error = 5 Are the timestamps correct? If the server is replying with a 'garbage' message, then certainly that will result in an EIO. However I didn't see anything like that in your tcpdump, and the juxtaposed 'nfs_get_root' error rather points to that as being a mount error. Cheers, Trond