From owner-freebsd-fs@FreeBSD.ORG Fri Nov 13 10:49:11 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 308DD1065697 for ; Fri, 13 Nov 2009 10:49:11 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 97E648FC1D for ; Fri, 13 Nov 2009 10:49:10 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id nADAn7fm002798; Fri, 13 Nov 2009 11:49:09 +0100 Received: from pmp.uni-hannover.de (theq.pmp.uni-hannover.de [130.75.117.4]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 08C6724; Fri, 13 Nov 2009 11:49:08 +0100 (CET) Date: Fri, 13 Nov 2009 11:49:07 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-fs@freebsd.org Message-Id: <20091113114907.cb04885e.gerrit@pmp.uni-hannover.de> In-Reply-To: <20091113104426.e8e85871.gerrit@pmp.uni-hannover.de> References: <20091112182414.cebec1df.gerrit@pmp.uni-hannover.de> <20091113104426.e8e85871.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.11.13.103324 Cc: Subject: Re: nfsv4 FreeBSD server vs. Linux client I/O error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2009 10:49:11 -0000 On Fri, 13 Nov 2009 10:44:26 +0100 Gerrit K=FChn wrote about Re: nfsv4 FreeBSD server vs. Linux client I/O error: GK> RM> I'll be happy to look at a tcpdump capture, if you get one, rick GK>=20 GK> You should have received it by now. I'm looking forward to your answer. GK> Thanks again. One more thing from my side: I guess I fixed the timeout problem by restarting all concerned services on the client side (namely rpc.idmapd and remounting rpc_pipefs). Now I get quick responses, but I still see the i/o error when trying to access the mounted volume. cu Gerrit