ZFS: Difference between revisions

Line 11:

== Known issues ==

* ~~As of 2014-03-04, you~~ shouldn't use a ZVol as a swap device, as it can deadlock under memory pressure

* You shouldn't use a ZVol as a swap device, as it can deadlock under memory pressure

* ~~As of 2014-03-04, you~~ should set the <code>mountpoint</code> property of your ZFS filesystems to be <code>legacy</code> and let NixOS mount them like any other filesystem (such as ext4 or btrfs), otherwise some filesystems may fail to mount due to ordering issues

* You should set the <code>mountpoint</code> property of your ZFS filesystems to be <code>legacy</code> and let NixOS mount them like any other filesystem (such as ext4 or btrfs), otherwise some filesystems may fail to mount due to ordering issues

* ~~As of 2014-03-04, 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.

* 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.

== How to use it ==

{{note|Add all mounts to your as legacy mounts as described in this article instead of zfs's own mount mechanism. Otherwise mount's might be not mounted in the correct order during boot!}}

Just add the following to your <code>configuration.nix</code> file:

@@ Line 11: / Line 11: @@
 == Known issues ==
-* As of 2014-03-04, you shouldn't use a ZVol as a swap device, as it can deadlock under memory pressure
+* You shouldn't use a ZVol as a swap device, as it can deadlock under memory pressure
-* As of 2014-03-04, you should set the <code>mountpoint</code> property of your ZFS filesystems to be <code>legacy</code> and let NixOS mount them like any other filesystem (such as ext4 or btrfs), otherwise some filesystems may fail to mount due to ordering issues
+* You should set the <code>mountpoint</code> property of your ZFS filesystems to be <code>legacy</code> and let NixOS mount them like any other filesystem (such as ext4 or btrfs), otherwise some filesystems may fail to mount due to ordering issues
-* As of 2014-03-04, 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.
+* 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.
 == How to use it ==
+{{note|Add all mounts to your as legacy mounts as described in this article instead of zfs's own mount mechanism. Otherwise mount's might be not mounted in the correct order during boot!}}
 Just add the following to your <code>configuration.nix</code> file: