Date: Mon, 8 Feb 2010 14:32:30 -0800 From: Freddie Cash <fjwcash@gmail.com> To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: NFSv4: mount -t nsf4 not the same as mount_newnfs? Message-ID: <b269bc571002081432n19f126d8se9193ae1e5e00301@mail.gmail.com> In-Reply-To: <Pine.GSO.4.63.1002081729450.17410@muncher.cs.uoguelph.ca> References: <4B6FE550.9020506@zedat.fu-berlin.de> <Pine.GSO.4.63.1002080959030.25952@muncher.cs.uoguelph.ca> <4B70497B.1000908@zedat.fu-berlin.de> <Pine.GSO.4.63.1002081729450.17410@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 8, 2010 at 2:37 PM, Rick Macklem <rmacklem@uoguelph.ca> wrote: > ps: ZFS also has its own export stuff, but it is my understanding that > putting a line in /etc/exports is sufficient. I've never used ZFS, > so others will know more than I. > My understanding (from having used NFS and ZFS, haven't looked at the code) is that: The sharenfs property for a ZFS dataset gets written out to /etc/zfs/exports, which gets appended to the mountd command-line by default. Thus, you can use /etc/exports or sharenfs property, whichever is easier. # zfs get sharenfs storage/backup NAME PROPERTY VALUE SOURCE storage/backup sharenfs -maproot=root 192.168.0.12 local # cat /etc/exports # cat /etc/zfs/exports # !!! DO NOT EDIT THIS FILE MANUALLY !!! /storage/backup -maproot=root 192.168.0.12 # pgrep -lf exports 1381 /usr/sbin/mountd -r -p 32000 /etc/exports /etc/zfs/exports -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b269bc571002081432n19f126d8se9193ae1e5e00301>