Talk:ZFS: Difference between revisions
imported>Thedude Suggest adding 'sleep' to multi-pool encrypted ZFS example. |
|||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
== Open Issues with ZFS enryption == | |||
Should this guide not have a big fat red warning that tells users, that openzfs currently has encryption related bugs, which can lead to data loss when using recv/send? | |||
see: | |||
https://github.com/openzfs/openzfs-docs/issues/494 | |||
== Add <code>boot.initrd.supportedFilesystems = ["zfs"];</code> ? == | == Add <code>boot.initrd.supportedFilesystems = ["zfs"];</code> ? == | ||
| Line 38: | Line 45: | ||
Long story short, I think the example on the ZFS page should include the sleep. | Long story short, I think the example on the ZFS page should include the sleep. | ||
== Unable to follow instructions from "Laying out the filesystem hierarchy" == | |||
I tried following the instructions from [[ZFS#Laying_out_the_filesystem_hierarchy]] but the system never fully booted and had errors about being unable to mount "/home" or "/root". | |||
The fix was to use a legacy mountpoint instead, while also reducing the number of ZFS data sets to a minimum and using "/" as a ZFS data set instead of tmpfs. | |||
--[[User:Grische|Grische]] ([[User talk:Grische|talk]]) 12:45, 26 February 2022 (UTC) | |||
== Inclusion of /var/persist == | |||
Looking over the post, there is no mention of creating a /var/persist directory. I'd personally recommend adding it as a separate volume/dataset which is autosnapshotted in case it is needed. | |||
# zfs create -o canmount=on rpool/nixos/var/persist | |||
--[[User:Keksbg|Keksbg]] ([[User talk:Keksbg|talk]]) 21:55, 29 March 2022 (UTC) | |||
== best practice == | |||
; Datasets: | |||
* https://grahamc.com/blog/nixos-on-zfs/ | |||