ZFS: Difference between revisions
imported>2r m rm blank lines |
imported>2r smbshare to do |
||
| Line 169: | Line 169: | ||
When you login by SSH into the box or when you have physical access to the machine itself, you will be prompted to supply the unlocking password for your zroot and tankXXX pools. | When you login by SSH into the box or when you have physical access to the machine itself, you will be prompted to supply the unlocking password for your zroot and tankXXX pools. | ||
== NFS share == | |||
With <code>sharenfs</code> property, ZFS has build-in support for generating <code>/etc/exports.d/zfs.exports</code> file, which in turn is processed by NFS service automatically. | |||
{{warning|If you are intending on defining an IPv6 subnet as part of your sharenfs rule, as of ZFS 2.0.6 (2021-09-23) please note that due to a bug in openzfs '''your rule will not correctly apply''', and may result in a security vulnerability (CVE-2013-20001). A fix has been implemented in the next yet-to-be-released upstream version - [https://github.com/openzfs/zfs/pull/11939 openzfs/zfs#11939]}} | |||
To enable NFS share on a dataset, only two steps are needed: | |||
First, enable [[NFS|NFS service]]: | |||
<syntaxhighlight lang="nix"> | |||
services.nfs.server.enable = true; | |||
</syntaxhighlight> | |||
Only this line is needed. Configure firewall if necessary, as described in [[NFS]] article. | |||
Then, set <code>sharenfs</code> property: | |||
<syntaxhighlight lang="console"> | |||
# zfs set sharenfs="ro=192.168.1.0/24,all_squash,anonuid=70,anongid=70" rpool/myData | |||
</syntaxhighlight> | |||
For more options, see <code>man 5 exports</code>. | |||
Todo: smbshare property for Samba. | |||
== Mail notification for ZFS Event Daemon == | == Mail notification for ZFS Event Daemon == | ||
| Line 265: | Line 286: | ||
# zpool scrub $pool | # zpool scrub $pool | ||
</syntaxhighlight> | </syntaxhighlight> | ||
[[Category:Guide]] | [[Category:Guide]] | ||