Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Jun 2018 12:10:31 -0500
From:      Josh Paetzel <josh@tcbug.org>
To:        Robert Fitzpatrick <robert@webtent.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: NFS to FreeNAS
Message-ID:  <7D1659AB-6234-4DCA-9482-0D5E70E31242@tcbug.org>
In-Reply-To: <5B2534AB.3070003@webtent.org>
References:  <5B241273.3070004@webtent.org> <1529101626.966595.1409703528.3672C083@webmail.messagingengine.com> <5B2534AB.3070003@webtent.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help


> On Jun 16, 2018, at 11:02 AM, Robert Fitzpatrick <robert@webtent.org> wrot=
e:
>=20
> Josh Paetzel wrote:
>>=20
>> Take a look at /var/log/messages on the FreeNAS box for errors when you m=
ount, also paste the output of showmount -e and cat /etc/exports from the Fre=
eNAS system.
>>=20
>=20
> Thank you! Yes, I could see the connection being denied by FreeNAS in the c=
onsole. Once I realized with showmount, got it working. Failed to mention my=
 mx sub dir of backups is a dataset of its own. I was thinking the alldirs i=
n the exports would allow it, perhaps because mx being a separate dataset in=
 FreeNAS? Once I added mx as own share, works!
>=20
> --=20
> Robert
>=20

ZFS datasets are filesystems. So they need their own export in NFS.





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?7D1659AB-6234-4DCA-9482-0D5E70E31242>