ZFS: Difference between revisions
imported>Sjau |
imported>Sjau |
||
Line 274: | Line 274: | ||
However this leads to a format change of the encrypted datasets. As a result of this format change, encrypted datasets that were created by older zfs versions can only be mounted as read-only. Encrypted datasets created with the new format cannot be opened at all on older versions. Unencrypted datasets were not altered and work as before. | However this leads to a format change of the encrypted datasets. As a result of this format change, encrypted datasets that were created by older zfs versions can only be mounted as read-only. Encrypted datasets created with the new format cannot be opened at all on older versions. Unencrypted datasets were not altered and work as before. | ||
If you've followed this wiki entry and didn't create an encrypted top-level dataset but a child-dataset, e.g. zroot/root/nixos where zroot is the name of the pool and the top-level dataset and root is the encrypted child-dataset, then you can easily use zfs send/recv to migrate it to the new format. | If you've followed this wiki entry and didn't create an encrypted top-level dataset but a child-dataset, e.g. <code>zroot/root/nixos</code> where <code>zroot</code> is the name of the pool and the top-level dataset and <code>root</code> is the encrypted child-dataset, then you can easily use zfs send/recv to migrate it to the new format. | ||
# Create a custom NixOS iso with crypto stability patch enabled | # Create a custom NixOS iso with crypto stability patch enabled |