From owner-freebsd-fs@FreeBSD.ORG Mon Feb 23 12:35:08 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CAB4988 for ; Mon, 23 Feb 2015 12:35:08 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0527CD23 for ; Mon, 23 Feb 2015 12:35:07 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YPsE2-0006Tu-MW for freebsd-fs@freebsd.org; Mon, 23 Feb 2015 13:35:02 +0100 Received: from p4fdddda4.dip0.t-ipconnect.de ([79.221.221.164]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Feb 2015 13:35:02 +0100 Received: from christian.baer by p4fdddda4.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Feb 2015 13:35:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Christian Baer Subject: Re: The magic of ZFS and NFS (2nd try) Date: Mon, 23 Feb 2015 13:32:31 +0100 Lines: 55 Message-ID: <3359447.v8JUK05WsX@falbala.rz1.convenimus.net> References: <4257601.p3oiXZFr4n@falbala.rz1.convenimus.net> <12103095.viZFqgegqA@falbala.rz1.convenimus.net> <54E8D38F.9090608@pinyon.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p4fdddda4.dip0.t-ipconnect.de User-Agent: KNode/4.14.2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 12:35:08 -0000 Russell L. Carter wrote: > When I was working out my own mounts, it seemed that sharenfs=on was > required to make them work, but I just checked and indeed I can > mount a zfs file system over NFS4.1 without it. So I would definitely > agree about not complicating things. The complicated thing about the options here is not so much where they have to be set (although I am doing a pretty good job ob messing that up), but rather that it's a pain if a setting can be found in one of 10 configuration files. That is a real pain. > Having both sharenfs and sharesmb *seem* to work does complicate > figuring out how to make NFS work if you don't already know this, > though. Well, I always got NFS to work fine in the past and we use it quite heavily at work. This is my first try at NFS with ZFS. And as I stated, the directory /usr/archive (which is a subfolder of / and formated with UFSv2) can be read fine. So if move or copy something from within /usr/archive/Shared to /usr/archive, I can access that file or folder tree. But let's say that is sub-optimal. > Back to Christian's problem, I don't see nfsv4_server_enable="YES" > in your rc.conf lines. I have it in mine, and NFSv4 works. > See man(4) nfsv4. I was actually expecting NFSv4 to be that default in FreeBSD 10.1. But ok, I added the line and restarted the nfsd with root@obelix:/usr/archive/Shared # /etc/rc.d/nfsd restart Stopping nfsd. Waiting for PIDS: 11247 11248, 11247. Starting nfsd. > You might have a look at /var/log/messages after restarting nfsd. There was nothing in /var/log/messages about the nfsd restarting. But there was something when I tried to mount the export: Feb 23 13:05:19 obelix mountd[50070]: mount request denied from 192.168.100.8 for /usr/archive/Shared Is there a way to get a message about what motivated this reaction? The mount command wasn't helpful either: root@falbala:/mnt # mount obelix:/usr/archive/Shared /mnt/Shared/ [tcp] obelix:/usr/archive/Shared: Permission denied Note that this keeps going and I have to exit it via ctl-c. Kind regards, Christian