You can use sudo systemctl start systemd-cryptsetup@<name> instead of cryptsetup luksOpen UUID=… <name> when you have an entry as follows in your /etc/crypttab: <name> UUID=… none noauto It will prompt you for the passphrase if needed. The corresponding unit file is generated automatically by systemd-cryptsetup-generator. You can list all generated unit files using systemctl list-unit-files| … Read more
LUKS doesn’t actually store the size of the device — it simply discovers it when the volume is opened. It therefore only comes into play if the volume is not closed and reopened during the process (e.g. doing an online grow). In this case the size of the open volume needs to be rediscovered. To … Read more
Yes! It looks like it’s possible. Let’s check how it can be achieved. Note that this doesn’t create a true grow-on-demand filesystem, as when the filesystem reaches the max size of the sparse file, it will report ‘out of space’ errors if more data still needs to be written. Initially, I was investigating Thin Provisioning, … Read more
The exact method depends on how you have setup luks, and if you have LVM on top of luks or if you just have a filesystem within the luks volume. If you don’t have LVM in addition to luks then you would probably do something like this. cryptsetup luksOpen /dev/rawdevice somename fsck /dev/mapper/somename # or … Read more
One of the servers that I administrate runs the type of configuration that you describe. It has six 1TB hard drives with a LUKS-encrypted RAIDZ pool on it. I also have two 3TB hard drives in a LUKS-encrypted ZFS mirror that are swapped out every week to be taken off-site. The server has been using … Read more