ZFS: Difference between revisions
imported>Equirosa m Small grammatical fix |
imported>Tyleroconnell m Adding a solution from Matrix when ZFS doesn't automatically discover zpools after reboot within a VM |
||
| Line 28: | Line 28: | ||
* By default, all ZFS pools available to the system will be forcibly imported during boot, regardless if you had imported them before or not. You should be careful not to have any other system accessing them at the same time, otherwise it will corrupt your pools. Normally (for the common desktop user) this should not be a problem, as a hard disk is usually only directly connected to one machine. This behaviour can be disabled by setting <code>boot.zfs.forceImportAll = false</code>. | * By default, all ZFS pools available to the system will be forcibly imported during boot, regardless if you had imported them before or not. You should be careful not to have any other system accessing them at the same time, otherwise it will corrupt your pools. Normally (for the common desktop user) this should not be a problem, as a hard disk is usually only directly connected to one machine. This behaviour can be disabled by setting <code>boot.zfs.forceImportAll = false</code>. | ||
* If you create a zpool in the installer, make sure you run `zpool export <pool name>` after `nixos-install`, or else when you reboot into your new system, zfs will fail to import the zpool. | * If you create a zpool in the installer, make sure you run `zpool export <pool name>` after `nixos-install`, or else when you reboot into your new system, zfs will fail to import the zpool. | ||
* If you are running within a VM and NixOS fails to import the zpool on reboot, you may need to add <code>boot.zfs.devNodes = "/dev/disk/by-path";</code> to your configuration.nix file. | |||