Date: Mon, 8 Sep 2008 02:10:52 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: freebsd-fs@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org> Subject: Re: ZFS filesystem: export for more than one subnet Message-ID: <20080908091052.GA63182@icarus.home.lan> In-Reply-To: <alpine.BSF.2.00.0809081112410.53906@woozle.rinet.ru> References: <alpine.BSF.2.00.0809071836130.76180@woozle.rinet.ru> <20080907220104.GA26094@icarus.home.lan> <alpine.BSF.2.00.0809080237580.53906@woozle.rinet.ru> <20080907233637.GA51889@icarus.home.lan> <alpine.BSF.2.00.0809081112410.53906@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 08, 2008 at 11:21:48AM +0400, Dmitry Morozovsky wrote: > On Sun, 7 Sep 2008, Jeremy Chadwick wrote: > JC> That said, what happens if you edit /etc/zfs/exports by hand, then run > JC> "zfs list -o sharenfs"? Does it show the changes you put in place? If > JC> so, then great -- it means there's two ways a person can edit the > JC> NFS-exported ZFS shares (by editing the file directly, or using "zfs"). > > Nope, ZFS does not track /etc/zfs/export, hence "Do not edit!" comment in it. Understood. Then using "zfs" is the only option. > JC> If not (e.g. mountd rejects it, or only the first network is used), then > JC> this would indicate a problem with the exports file syntax / problem > JC> with mountd, and not with ZFS. > > It is of course FreeBSD' mountd problem (more than it does not understand CIDR > slashed notation): > > marck@beaver:~# cat /etc/zfs/exports > # !!! DO NOT EDIT THIS FILE MANUALLY !!! > > /FreeBSD -ro -alldirs -network 195.54.192.0 -mask 255.255.255.192 > 255.255.255.192 > marck@beaver:~# zfs get sharenfs bv/FreeBSD > NAME PROPERTY VALUE SOURCE > bv/FreeBSD sharenfs -ro -alldirs -network 195.54.192.0 -mask 255.255.255.192 local > marck@beaver:~# zfs set sharenfs="ro,alldirs,network=195.54.192.0/26,192.168.39.0/24" bv/FreeBSD > marck@beaver:~# zfs get sharenfs bv/FreeBSD > NAME PROPERTY VALUE SOURCE > bv/FreeBSD sharenfs ro,alldirs,network=195.54.192.0/26,192.168.39.0/24 local > > Sep 8 11:18:18 beaver mountd[25992]: can't get address info for host 192.168.39.0/24 > Sep 8 11:18:18 beaver mountd[25992]: bad host 192.168.39.0/24, skipping > Sep 8 11:18:18 beaver mountd[25992]: network/host conflict > Sep 8 11:18:18 beaver mountd[25992]: bad exports list line /FreeBSD -ro -alldirs -network It does support CIDR, and the output mountd gave you even shows that it does (look closely at what "bad host" it's giving you -- that isn't the first host in the exports list!). You changed the syntax of what I gave you as an example. Look closely: # zfs set sharenfs="ro,network=aaa/xx,network=bbb/yy,network=ccc/zz" some_fs Here's what you typed in: # zfs set sharenfs="ro,alldirs,network=195.54.192.0/26,192.168.39.0/24" bv/FreeBSD -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080908091052.GA63182>