Date: Wed, 24 Oct 2012 21:36:02 +0200 From: Yamagi Burmeister <lists@yamagi.org> To: rmacklem@uoguelph.ca Cc: freebsd-fs@freebsd.org Subject: Re: Can not read from ZFS exported over NFSv4 but write to it Message-ID: <20121024213602.b727c557f0332f28a66f87cc@yamagi.org> In-Reply-To: <1579346453.2736080.1351029315835.JavaMail.root@erie.cs.uoguelph.ca> References: <20121023204623.a1eef4f99b5f786050229b6c@yamagi.org> <1579346453.2736080.1351029315835.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Wed__24_Oct_2012_21_36_02_+0200_X.MkMC0OSo=8XO+b Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello On Tue, 23 Oct 2012 17:55:15 -0400 (EDT) Rick Macklem <rmacklem@uoguelph.ca> wrote: > > # ZFS > > /usr/home/yamagi > > # UFS > > /mnt > > V4: / -sec=3Dsys 192.168.0.13 > >=20 > For ZFS, all volumes down to yamagi must be exported. > You don't show what your ZFS setup is, but you either > need to export "home" and "usr" if those are ZFS volumes. > (The above /etc/exports would be ok, only if /, /usr and > /home are all UFS volumes and /usr/home/yamagi is the root > of a ZFS volume.) For UFS, non-exported volumes can be > traversed by "mount", but for ZFS that is not the case. >=20 > The only way I know of to fix this inconsistency is to > disable the traversal capability for UFS, but that would > be a POLA violation, so the inconsistency (caused by ZFS > checking exports itself instead of leaving to the VFS layer) > remains. >=20 > OR > you can specify the root of V4 in the exported volume. > For example, you could: > # ZFS > /usr/home/yamagi > V4: /usr/home/yamagi -sec=3Dsys 192.168.0.13 >=20 > And then the client mount would be: > a:/ on /mnt > since "/" would be at /usr/home/yamagi. (If you do this, > the /mnt UFS volume wouldn't be mountable via NFSv4.) Okay, I didn't know that. What about adding a small notice to the nfsv4 (4) manpage to put users into the right direction? A correct /etc/exports didn't solve the problem. So I took some tcpdumps, while analyzing them I noticed that packages send by client never arived at the server. After I changed the NIC (I was using a rather cheap age(4) onboard NIC) everything worked okay. Apparently NFSv4 exhibited a bug in the driver that never showed up before. I'm sorry that i've wasted your time. Thanks again, Yamagi --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB --Signature=_Wed__24_Oct_2012_21_36_02_+0200_X.MkMC0OSo=8XO+b Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCIQyYACgkQWTjlg++8y8vZ4wCePa+YOukPlFNXzexcRhcDSExW FXUAmwWs0HE4FSOHLjbnGU6BSgqLxVXl =0fl6 -----END PGP SIGNATURE----- --Signature=_Wed__24_Oct_2012_21_36_02_+0200_X.MkMC0OSo=8XO+b--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121024213602.b727c557f0332f28a66f87cc>