From owner-freebsd-stable@FreeBSD.ORG Mon Feb 8 17:25:59 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 0579D106566C; Mon, 8 Feb 2010 17:25:59 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 4AE188FC13; Mon, 8 Feb 2010 17:25:53 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1NeXMv-0000Yp-4W>; Mon, 08 Feb 2010 18:25:53 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1NeXMv-0004xH-2W>; Mon, 08 Feb 2010 18:25:53 +0100 Message-ID: <4B70497B.1000908@zedat.fu-berlin.de> Date: Mon, 08 Feb 2010 17:27:23 +0000 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100206 Thunderbird/3.0.1 MIME-Version: 1.0 To: Rick Macklem References: <4B6FE550.9020506@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 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: Mon, 08 Feb 2010 17:25:59 -0000 On 02/08/10 15:01, Rick Macklem wrote: > > > On Mon, 8 Feb 2010, O. Hartmann wrote: > >> >> Mounting the filessystem via >> >> mount_newnfs host:/path /path >> >> works fine, but not >> >> mount -t nfs4 host:/path /path. >> > > The mount command can be either: > mount -t nfs -o nfsv4 host:/path /path > or > mount -t newnfs -o nfsv4 host:/path /path > (The above was what the old now removed nfs4 used.) > > Have fun with it, rick So I guess the above one is the more 'transparent' one with respect to the future, when NFSv4 gets mature and its way as matured into the kernel? I tried the above and it works. But it seems, that only UFS2 filesystems can be mounted by the client. When trying mounting a filesystem residing on ZFS, it fails. Mounting works, but when try to access or doing a simple 'ls', I get ls: /backup: Permission denied On server side, /etc/exports looks like -- V4: / -sec=sys:krb5 #IPv4# /backup #IPv4# -- Is there still an issue with ZFS? Regards, Oliver