From owner-freebsd-fs@FreeBSD.ORG Fri Nov 13 09:44:29 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 D170F106566C for ; Fri, 13 Nov 2009 09:44:29 +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 5F57B8FC13 for ; Fri, 13 Nov 2009 09:44:29 +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 nAD9iQ35032336; Fri, 13 Nov 2009 10:44:27 +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 D33814F; Fri, 13 Nov 2009 10:44:26 +0100 (CET) Date: Fri, 13 Nov 2009 10:44:26 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Rick Macklem Message-Id: <20091113104426.e8e85871.gerrit@pmp.uni-hannover.de> In-Reply-To: References: <20091112182414.cebec1df.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=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.11.13.93327 Cc: freebsd-fs@freebsd.org 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 09:44:29 -0000 On Thu, 12 Nov 2009 17:17:55 -0500 (EST) Rick Macklem wrote about Re: nfsv4 FreeBSD server vs. Linux client I/O error: RM> One more thing that came to mind. If your root fs in NFS mounted, it RM> can't be exported, so you have to use the version (assuming /exports RM> is a local on-disk file system that is exported): RM> V4: /export RM> and not RM> V4: / I guess this does not apply do my situation, both client and server have their root fs on hard disks. RM> and then the mount needs to look like: RM> mount -t nfs4 :/export /mnt I tried that, just to make sure: pt-ws1 ~ # time mount -t nfs4 cliff:/tank /mnt mount.nfs4: mounting cliff:/tank failed, reason given by server: No such file or directory real 1m0.006s user 0m0.002s sys 0m0.002s I guess this is consistent, although I do not know why I see 30s timeout interval twice here. RM> I tried a relatively recent Ubuntu client here and it seemed to mount RM> ok. (There are many variants of the mount utilities and patch versions RM> of the nfs4 client for Linux, so your mileage definitely may vary.) I'm using Sabayon 3.5 with kernel 2.6.25 here. I guess I could try and update to the new Sabayon 5 for testing (if that might help). The installed nfs packages are: net-libs/libnfsidmap-0.20 net-fs/nfs4-acl-tools-0.3.2 net-fs/nfs-utils-1.1.2 RM> I'll be happy to look at a tcpdump capture, if you get one, rick You should have received it by now. I'm looking forward to your answer. Thanks again. cu Gerrit