From owner-freebsd-fs@FreeBSD.ORG Mon Feb 23 16:27:28 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59A8ECDB for ; Mon, 23 Feb 2015 16:27:28 +0000 (UTC) Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EF55B7C for ; Mon, 23 Feb 2015 16:27:28 +0000 (UTC) Received: by yhoc41 with SMTP id c41so11112899yho.2 for ; Mon, 23 Feb 2015 08:27:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w19ZN40RSR+FkMrA6USsLMEy5ITvrO8ZDD1/z4g7Xzs=; b=CFOrMwJVShJ2cMJ10FPEB+RLO9gueQNlYa50jj0TQok4eGieiUr2pCXJhP8qcs3ibq X2rz7cpc+dk08v9fRQH5O4q+x5+HPd0E17cu2CISO0jciJ39oHUJG0+t7Occr9TMqeRk etmpbVlYxB4b0uaOKnKhQao37Pzs6Q0ggR8yRVi+a6ky7+z0c7k3DbNFoit87ZS8aZKn epPXmmdGsBzt7yTb2cpovCg/aHvTcOodjjjGggXZLPa9CDVdfsHI3kSX88JPCerpp8af MnPY5CU7hnUJLTvsm8FGn1J/XHRvmXS42ycNNatF4UXBlBoqrUpOpUVahg95YHB308Nq lCtg== MIME-Version: 1.0 X-Received: by 10.170.142.85 with SMTP id j82mr7634593ykc.123.1424708847155; Mon, 23 Feb 2015 08:27:27 -0800 (PST) Received: by 10.170.79.87 with HTTP; Mon, 23 Feb 2015 08:27:27 -0800 (PST) In-Reply-To: <13471232.xpn8XerdpW@falbala.rz1.convenimus.net> References: <4257601.p3oiXZFr4n@falbala.rz1.convenimus.net> <12103095.viZFqgegqA@falbala.rz1.convenimus.net> <13471232.xpn8XerdpW@falbala.rz1.convenimus.net> Date: Mon, 23 Feb 2015 08:27:27 -0800 Message-ID: Subject: Re: The magic of ZFS and NFS (2nd try) From: Freddie Cash To: Christian Baer Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Filesystems 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 16:27:28 -0000 On Mon, Feb 23, 2015 at 4:30 AM, Christian Baer < christian.baer@uni-dortmund.de> wrote: > Rainer Duffner wrote: > > > These lines get written into /etc/zfs/exports > > > > I like it that way because if a filesystem is destroyed, I don=E2=80=99= t have to > > remember removing it from /etc/exports. > > > > I also admit I=E2=80=99m heavily influenced by Solaris on this particul= ar > setting=E2=80=A6 > > I didn't come from Solaris and I wasn't a big fan of it during my time at > university. It wasn't the really a problem with the OS itself but with th= e > userland which really sucked rocks at the time. We are talking SunOS 5.8 > here. > > I am guessing that in the future, ZFS will be far more important and UFS > will become more and more exotic. Then it would be fine to config > everything > the ZFS-way. But currently, it seems pretty dumb to have to go through a > case list like: > > =E2=80=8BYou don't. All NFS-related configuration stuff goes into /etc/exp= orts by default. Including ZFS stuff. Just treat ZFS like any other filesystem when it comes to NFS, and configure it just like any other filesystem. If, and only if, you want to play with the ZFS property "sharenfs", then you can. You aren't required to (and probably shouldn't as the syntax will be different for every OS and may cause issues with replication to other pools). If you do, then anything you put into that property will be automatically copied into /etc/zfs/exports. You should never be manually editing /etc/zfs/exports, as any manual changes you make will be lost the next time you edit any "sharenfs" property on any ZFS filesystem. --=20 Freddie Cash fjwcash@gmail.com