Talk:ZFS - Revision history

Devvythelopper: /* Open Issues with ZFS enryption */

2024-08-17T16:37:02Z

Open Issues with ZFS enryption

← Older revision		Revision as of 16:37, 17 August 2024
Line 1:		Line 1:
	== Open Issues with ZFS enryption ==		== Open Issues with ZFS enryption ==

	Should this guide not have a big fat red warning that tells users, that openzfs currently has bugs, which can lead to data loss when using recv/send?		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:		see:

	https://github.com/openzfs/openzfs-docs/issues/494		https://github.com/openzfs/openzfs-docs/issues/494


	== Add <code>boot.initrd.supportedFilesystems = ["zfs"];</code> ? ==		== Add <code>boot.initrd.supportedFilesystems = ["zfs"];</code> ? ==

Devvythelopper at 16:36, 17 August 2024

2024-08-17T16:36:32Z

← Older revision		Revision as of 16:36, 17 August 2024
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 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> ? ==

imported>Vater: /* best practice */ new section

2024-02-17T17:56:25Z

best practice: new section

← Older revision		Revision as of 17:56, 17 February 2024
Line 52:		Line 52:

	--[[User:Keksbg\|Keksbg]] ([[User talk:Keksbg\|talk]]) 21:55, 29 March 2022 (UTC)		--[[User:Keksbg\|Keksbg]] ([[User talk:Keksbg\|talk]]) 21:55, 29 March 2022 (UTC)

			== best practice ==

			; Datasets:
			* https://grahamc.com/blog/nixos-on-zfs/

imported>Keksbg at 21:55, 29 March 2022

2022-03-29T21:55:01Z

← Older revision		Revision as of 21:55, 29 March 2022
Line 45:		Line 45:
	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.		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)		--[[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)

imported>Grische: /* Unable to follow instructions from "Laying out the filesystem hierarchy" */ new section

2022-02-26T12:45:16Z

Unable to follow instructions from "Laying out the filesystem hierarchy": new section

← Older revision		Revision as of 12:45, 26 February 2022
Line 38:		Line 38:

	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)

imported>Thedude: Suggest adding 'sleep' to multi-pool encrypted ZFS example.

2021-10-23T19:23:03Z

Suggest adding 'sleep' to multi-pool encrypted ZFS example.

← Older revision		Revision as of 19:23, 23 October 2021
Line 13:		Line 13:

	--[[User:Mohe2015\|Mohe2015]] ([[User talk:Mohe2015\|talk]]) 15:46, 22 March 2021 (UTC)		--[[User:Mohe2015\|Mohe2015]] ([[User talk:Mohe2015\|talk]]) 15:46, 22 March 2021 (UTC)



			== Multiple Encrypted Pools Issue ==

			I tried following the "Import and unlock multiple encrypted pools/dataset at boot" section (and friends) but could not get it to work, with the dataset either not being mounted, or the boot aborting with a permission error. What finally fixed it for me:

			# Create pool like so:
			zpool create <your-other-options> -O keyformat=passphrase pool_name $DISK_HDD

			And use this for initrd.network.postCommands:

			cat <<EOF > /root/.profile
			if pgrep -x "zfs" > /dev/null
			then
			zpool import hdd # Import pool like in example
			sleep 3 # <---- THIS IS THE IMPORTANT PART
			zfs load-key -a
			killall zfs
			else
			echo "zfs not running -- maybe the pool is taking some time to load for some unforseen reason."
			fi
			EOF

			Long story short, I think the example on the ZFS page should include the sleep.

imported>Vater: Vater moved page Talk:NixOS on ZFS to Talk:ZFS

2021-10-11T03:57:56Z

Vater moved page Talk:NixOS on ZFS to Talk:ZFS

← Older revision		Revision as of 03:57, 11 October 2021
(No difference)

imported>Mohe2015: Created page with " == Add `boot.initrd.supportedFilesystems = ["zfs"];` ? == What about recommending to also add boot.initrd.supportedFilesystems = ["zfs"]; See https://github.co..."

2021-03-22T15:46:29Z

Created page with " == Add <code>boot.initrd.supportedFilesystems = ["zfs"];</code> ? == What about recommending to also add boot.initrd.supportedFilesystems = ["zfs"]; See https://github.co..."

New page

== Add <code>boot.initrd.supportedFilesystems = ["zfs"];</code> ? ==

What about recommending to also add

boot.initrd.supportedFilesystems = ["zfs"];

See https://github.com/NixOS/nixpkgs/pull/99386#issuecomment-798813567

I think recommending to add this would allow you in the far future to use zfs as filesystem without forcing to add grub support for zfs if you don't need it.

I currently have https://github.com/NixOS/nixpkgs/pull/117071 open to revert back to that behaviour like it's been in 20.09 (adding a zfs filesystem also adds support to grub, more exactly the original behaviour was to always enable zfs support in grub even without any zfs filesystem)

--[[User:Mohe2015|Mohe2015]] ([[User talk:Mohe2015|talk]]) 15:46, 22 March 2021 (UTC)