You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if I am posting in the wrong thread: I don't have an issue, but rather a suggestion.
Is it possible to include the provision for your zfs plugin to create zpools on luks disks (i.e. dev/mapper devices)? As of now, it only shows actual disks.
I for one prefer not to use zfs' built-in encryption. And I always encrypt my data. Luks is very convenient given that keyfiles can be stored in a decrypted /root, and I can even use clevis to provide auto-boot-decryption options.
The way I create zpools on luks now is to manually create the zpool at the command line, then I can log into Houston and your module instantly sees the new pool (so I can mod/add datasets etc.). I wonder if would be cleaner/better(?) to even perform the creation from within your plugin (?) It's by no means essential since there is an easy workaround, but I thought it's easy to suggest.
THANK YOU for the excellent app. V/R
Andrew
The text was updated successfully, but these errors were encountered:
Apologies if I am posting in the wrong thread: I don't have an issue, but rather a suggestion.
Is it possible to include the provision for your zfs plugin to create zpools on luks disks (i.e. dev/mapper devices)? As of now, it only shows actual disks.
I for one prefer not to use zfs' built-in encryption. And I always encrypt my data. Luks is very convenient given that keyfiles can be stored in a decrypted /root, and I can even use clevis to provide auto-boot-decryption options.
The way I create zpools on luks now is to manually create the zpool at the command line, then I can log into Houston and your module instantly sees the new pool (so I can mod/add datasets etc.). I wonder if would be cleaner/better(?) to even perform the creation from within your plugin (?) It's by no means essential since there is an easy workaround, but I thought it's easy to suggest.
THANK YOU for the excellent app. V/R
Andrew
The text was updated successfully, but these errors were encountered: