Talk:ZFS - Revision history

Kacper: /* Remote unlock Section out of date */ Reply

2026-06-06T21:48:31Z

Remote unlock Section out of date: Reply

← Older revision		Revision as of 21:48, 6 June 2026
Line 91:		Line 91:
	: };		: };
	:</syntaxhighlight> [[User:Quio\|Quio]] ([[User talk:Quio\|talk]]) 15:59, 6 June 2026 (UTC)		:</syntaxhighlight> [[User:Quio\|Quio]] ([[User talk:Quio\|talk]]) 15:59, 6 June 2026 (UTC)
			::We have a bit of a discussion on this over at the discourse forum: https://discourse.nixos.org/t/decrypting-zfs-pools-over-ssh-on-26-05/77828 [[User:Kacper\|Kacper]] ([[User talk:Kacper\|talk]]) 21:48, 6 June 2026 (UTC)

2026-06-06T15:59:09Z

Remote unlock Section out of date: Reply

← Older revision		Revision as of 15:59, 6 June 2026
Line 68:		Line 68:

	In [[ZFS#Unlock encrypted ZFS via SSH on boot]] it mentions to use ''postCommands'', but this option is now no longer supported in the newest version of NixOS. [[User:Quio\|Quio]] ([[User talk:Quio\|talk]]) 15:54, 6 June 2026 (UTC)		In [[ZFS#Unlock encrypted ZFS via SSH on boot]] it mentions to use ''postCommands'', but this option is now no longer supported in the newest version of NixOS. [[User:Quio\|Quio]] ([[User talk:Quio\|talk]]) 15:54, 6 June 2026 (UTC)

			:Maybe something like this:
			:<syntaxhighlight lang="nix">
			: initrd = {
			: ...
			: systemd = {
			: enable = true;
			: # Write the ZFS unlock command to root's profile so it runs automatically
			: # when an admin SSHs in during boot; killall zfs unblocks systemd's wait
			: services.zfs-setup-unlock = {
			: wantedBy = ["initrd.target"];
			: before = ["initrd.target"];
			: unitConfig.DefaultDependencies = false;
			: script = ''
			: echo "zpool import -a && zfs load-key -a && killall zfs" >> /root/.profile
			: '';
			: serviceConfig = {
			: Type = "oneshot";
			: RemainAfterExit = true;
			: };
			: };
			: };
			:</syntaxhighlight> [[User:Quio\|Quio]] ([[User talk:Quio\|talk]]) 15:59, 6 June 2026 (UTC)

2026-06-06T15:54:18Z

Remote unlock Section out of date: new section

← Older revision		Revision as of 15:54, 6 June 2026
Line 64:		Line 64:
	; Datasets:		; Datasets:
	* https://grahamc.com/blog/nixos-on-zfs/		* https://grahamc.com/blog/nixos-on-zfs/

			== Remote unlock Section out of date ==

			In [[ZFS#Unlock encrypted ZFS via SSH on boot]] it mentions to use ''postCommands'', but this option is now no longer supported in the newest version of NixOS. [[User:Quio\|Quio]] ([[User talk:Quio\|talk]]) 15:54, 6 June 2026 (UTC)

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> ? ==

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> ? ==

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/

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)

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)

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.

2021-10-11T03:57:56Z

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