RE: ZFS sharenfs and NFS options
- From: "Michael Jung" <mikej@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 5 Mar 2008 08:33:50 -0500
When does /etc/zfs/exports get written?
Should you have to HUP mountd after adding the nfs share via "zfs set
sharenfs=....."? it doesn't make any difference for me.
Should showmount -e show the zfs exported NFS share?
(root@zega) /etc/zfs# zfs get sharenfs tank/export1
NAME PROPERTY VALUE
SOURCE
tank/export1 sharenfs -maproot=root -alldir -network 10.0.0.3 -mask
255.255.255.255 local
(root@zega) /etc/zfs#
(root@zega) /etc/zfs# cat /etc/zfs/exports
# !!! DO NOT EDIT THIS FILE MANUALLY !!!
(root@zega) /etc/zfs#
(root@zega) /etc/zfs# showmount -e
Exports list on localhost:
/export0 10.0.0.3
(root@zega) /etc/zfs#
(root@zega) /etc/zfs# uname -a
FreeBSD zega.mikej.com 7.0-STABLE FreeBSD 7.0-STABLE #2: Sun Mar 2
20:39:38 UTC 2008 mikej@xxxxxxxxxxxxxx:/usr/obj/usr/src/sys/ZEGA
i386
(root@zega) /etc/zfs#
NOTE****** /export0 is exported via /etc/exports
Needless to say, I'm not able to mount export1 on 10.0.0.3 when I share
it via the "zfs set sharenfs" command.
exporting the ZFS mount point via /etc/exports works fine.
--mikej
-----Original Message-----
From: Dmitry Morozovsky [mailto:marck@xxxxxxxx]
Sent: Wednesday, March 05, 2008 1:44 AM
To: Scot Hetzel
Cc: Michael Jung; current@xxxxxxxxxxx; Pawel Jakub Dawidek
Subject: Re: ZFS sharenfs and NFS options
On Tue, 4 Mar 2008, Scot Hetzel wrote:
SH> > what is a way to specify NFS options, such as -maproot and
SH> > -network, on an ZFS filesystem? Man page is almost quiet about
SH> > it, and my quick experiments did not show any success...
SH> >
SH> > I suppose, it should be documented a bit more...
SH> >
SH> It is documented in the zfs(1M) man page.
SH>
SH> zfs set sharenfs="-maproot=root -alldir -network 10.0.0.3 -mask
SH> 255.255.255.255" myzpool/test
SH>
SH> cat /etc/zfs/exports
SH> # !!! DO NOT EDIT THIS FILE MANUALLY !!!
SH>
SH> /myzpool/test -maproot=root -alldir -network 10.0.0.3 -mask
255.255.255.255
Hmm... where did you find it in the manpage? Or did you mean Solaris man
page version?
Anyway, thanks, it is working now.
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: marck@xxxxxxxxxxx ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@xxxxxxxx ***
------------------------------------------------------------------------
CONFIDENTIALITY NOTE: This message is intended only for the use
of the individual or entity to whom it is addressed and may contain
information that is privileged, confidential, and exempt from
disclosure under applicable law. If the reader of this message is
not the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication
is strictly prohibited. If you have received this transmission
in error, please notify us by telephone at (502) 212-4001 or
notify us at PAI , Dept. 99, 11857 Commonwealth Drive,
Louisville, KY 40299. Thank you.
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: ZFS sharenfs and NFS options
- From: FreeBSD
- Re: ZFS sharenfs and NFS options
- From: Scot Hetzel
- Re: ZFS sharenfs and NFS options
- References:
- ZFS sharenfs and NFS options
- From: Dmitry Morozovsky
- RE: ZFS sharenfs and NFS options
- From: Michael Jung
- Re: ZFS sharenfs and NFS options
- From: Scot Hetzel
- Re: ZFS sharenfs and NFS options
- From: Dmitry Morozovsky
- ZFS sharenfs and NFS options
- Prev by Date: Re: NFS locking revisited
- Next by Date: Re: cvs [update aborted]: received broken pipe signal
- Previous by thread: Re: ZFS sharenfs and NFS options
- Next by thread: Re: ZFS sharenfs and NFS options
- Index(es):
Relevant Pages
|
