ZFS: Difference between revisions
m Undo revision 21396 by Musicmatze (talk) (Not a typo. 'made' is correct here.) Tag: Undo |
m fix error |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 65: | Line 65: | ||
== Guides == | == Guides == | ||
=== | === Root on ZFS with disko === | ||
disko[https://github.com/nix-community/disko/blob/master/example/zfs.nix] can partition disks declaratively and handle mount points at install time. | |||
Don't follow the Root on ZFS guide found in OpenZFS documentation. It was abandoned and has not been updated in years. See commit log for the openzfs-docs repo for details. | |||
=== Simple NixOS ZFS on root installation === | === Simple NixOS ZFS on root installation === | ||
Line 441: | Line 434: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Only this line is needed. Configure firewall if necessary, as described in [[NFS]] article. | Only this line is needed. Configure firewall if necessary, as described in [[NFS]] article. | ||
{{warning|<code>zfs share</code> or <code>sharenfs</code> does not work if the <code>mountpoint</code> is set to <code>legacy</code> (or <code>none</code>, of course). I was unable to find a source for this behaviour, but I was stuck on the problem for days, until I realized the problem. ::Reply: sharenfs controlls what | |||
is written into <code>/etc/exports</code>. If ZFS does not know the mountpoint, as is the case in | |||
mountpoint legacy or none, the contents of <code>/etc/exports</code> would be wrong}} | |||
Then, set <code>sharenfs</code> property: | Then, set <code>sharenfs</code> property: | ||
Line 467: | Line 464: | ||
tls_trust_file = "/etc/ssl/certs/ca-certificates.crt"; | tls_trust_file = "/etc/ssl/certs/ca-certificates.crt"; | ||
tls = "on"; | tls = "on"; | ||
auth = " | auth = "plain"; | ||
tls_starttls = "off"; | tls_starttls = "off"; | ||
}; | }; |