From owner-freebsd-stable@FreeBSD.ORG Tue Feb 9 16:30:09 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D47011065744; Tue, 9 Feb 2010 16:30:09 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0B68FC16; Tue, 9 Feb 2010 16:30:09 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAKMbcUuDaFvG/2dsb2JhbADaV4RUBA X-IronPort-AV: E=Sophos;i="4.49,437,1262581200"; d="scan'208";a="64798280" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 09 Feb 2010 11:30:08 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 664B32101A0; Tue, 9 Feb 2010 11:30:08 -0500 (EST) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6fwn95C3UoX3; Tue, 9 Feb 2010 11:30:07 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 651DE21019D; Tue, 9 Feb 2010 11:30:07 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o19GfPW19098; Tue, 9 Feb 2010 11:41:25 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 9 Feb 2010 11:41:25 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "O. Hartmann" In-Reply-To: <4B712B54.4020000@zedat.fu-berlin.de> Message-ID: References: <4B6FE550.9020506@zedat.fu-berlin.de> <4B70497B.1000908@zedat.fu-berlin.de> <4B712B54.4020000@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: NFSv4: mount -t nsf4 not the same as mount_newnfs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2010 16:30:10 -0000 On Tue, 9 Feb 2010, O. Hartmann wrote: > Well, I guess I havn't uderstood everything of NFSv4. The 'concept' of the > 'root' is new to me, maybe there are some deeper explanation of the purpose? > Are there supposed to be more than one 'root' enries or only one? > Only to specify different security flavours for different client host IP#s. There is only one "root" location in the file system tree. This was done for NFSv4 to avoid any need for the mount protocol. See below. > At this very moment mounting seems to work, but I always get a 'permission > denied' error on every ZFS exported filesystem. Doing the same with UFS2 > filesystems, everything works as expected. > In NFSv4 "mount" does very little, since it does not use the mount protocol. It basically passes a "pathname" from the NFSv4 "root" into the kernel for later use. (Since UFS doesn't actually check exports, the experimental server checks them, but "cheats" and allows a minimal set of NFSv4 Operations on non-exported volumes, so that this "pathname" can be traversed to the exported volume. At this time ZFS checks exports. As such everything in the tree from the "root" specified by the "V4:" line must be exported for ZFS to work. I believe others have gotten a ZFS export to work, but I have no experience with it at this time. > Is there a way to inspect the exports and mounts for the used NFS-protocol? Not that I am aware. (Excluding ZFS, which I don't know anything about, the /etc/exports file specifies the exports.) > When issuing 'mount', the 'backup' mount is repoted to be 'newnfs', I assume > this reflects NFSv4 being used, now I need to figure out what's going wrong > with the ZFS export. NFS export of the ZFS filesystem is enabled, but as far > as I know, this feature is not used in FreeBSD since ZFS in FreeBSD lacks of > the capabilities of autonomously exporting its via NFS - well, I'm not an > expert in this matter. > I'm definitely not a ZFS expert either:-) I think the mount command is showing you that the mount point was created ("newnfs" refers to the experimental client), but as noted above, that doesn't indicate that it is accessible. (If you haven't tried moving the "V4: /backup ..." that moves the NFSv4 "root" to /backup, you should do that and see how it goes.) Good luck with it, rick