This zfs issue explains why a single send/receive does not work. If the source filesystem were not encrypted, I could compress it and encrypt it with a single send/receive, like this: ssh source sudo zfs send -R | sudo zfs receive -F -o compression=lz4 -x encryption z/enc/aīut if I try this with an encrypted dataset, I get an error: ssh source sudo zfs send -R | sudo zfs receive -F -o compression=lz4 -x encryption z/enc/aĬannot send encrypted dataset z/enc/a may not be sent with properties without the raw flag Zfs list -r -t all -o name,compression,encryption,encryptionroot z/enc/a Ssh source sudo zfs send -I | sudo zfs receive -F z/enc/a This seems to work, where and are the first and last snapshots: ssh source sudo zfs send | sudo zfs receive -o compression=lz4 -x encryption z/enc/a I don't want to use raw send, because I don't want to preserve all properties and the encryption key. It includes the functionality of both traditional file systems and volume manager. I also want to compress it at the same time, and preserve snapshots. OpenZFS is an open-source storage platform. └─981 /usr/bin/dbus-daemon -system -address=systemd: -nofork -nopidfile -systemd-activation -syslog-onlyįeb 27 21:12:52 vmbox dbus-daemon: Activating via systemd: service name='1' unit='' requested by ':1.1' (uid=0 pid=1514 comm="sshd: root " label="unconfined")įeb 27 21:13:17 vmbox dbus-daemon: Failed to activate service ' want to copy an encrypted filesystem (z/enc/a) from one computer (source) to another, and have it inherit the encryption key from the parent filesystem of the target system. Loaded: loaded (/lib/systemd/system/rvice static)Īctive: active (running) since Mon 21:12:35 CET 8h ago įeb 27 21:12:52 vmbox systemd-logind: Failed to connect to system bus: No such file or directoryįeb 27 21:12:52 vmbox systemd-logind: Failed to fully start up daemon: No such file or directory Journal begins at Mon 17:56:12 CET, ends at Mon 21:15:36 CET.
Main PID: 1578 (code=exited, status=1/FAILURE)įeb 27 21:12:52 vmbox systemd: rvice: Scheduled restart job, restart counter is at 5.įeb 27 21:12:52 vmbox systemd: Stopped User Login Management.įeb 27 21:12:52 vmbox systemd: rvice: Start request repeated too quickly.įeb 27 21:12:52 vmbox systemd: rvice: Failed with result 'exit-code'.įeb 27 21:12:52 vmbox systemd: Failed to start User Login Management.
Process: 1578 ExecStart=/lib/systemd/systemd-logind (code=exited, status=1/FAILURE) Loaded: loaded (/lib/systemd/system/rvice static)Īctive: failed (Result: exit-code) since Mon 21:12:52 CET 1min 43s ago
#OPENZFS ENCRYPTION HOW TO#
Zfs send -R | zfs receive -o encryption=on rpool/ROOT/pve-1Īll setup works fine and login to Proxmox is fast, until I run above script to encrypt the ZFS root partition.Īfter having typed zfs_unlock, the login takes +25 seconds to complete due to systemd-logind service which fails to start.Īny ideas why this is or how to fix it? # systemctl status rvice # Copy the files from the copy to the new encrypted zfs root
Zfs create -o encryption=on -o keyformat=passphrase rpool/ROOT # Create a new zfs root, with encryption turned on run for the archive, so that potential users know that theyll need lz4 to extract it. Zfs snapshot -r send -R | zfs receive rpool/copyroot Configured ZFS Encryption using following steps: zpool import -f rpool Used Proxmox 7.3 on a Hetzner baremetal server.
0 kommentar(er)
