summaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authorasomers <asomers@FreeBSD.org>2016-01-29 17:08:26 +0000
committerasomers <asomers@FreeBSD.org>2016-01-29 17:08:26 +0000
commit94b986ee45d924260f255854d8022435a559b674 (patch)
tree12a6f4e164f2fa781297a7b8f06198ae869750a2 /UPDATING
parenta6dbee3943e27268eda39568d19621ea61955211 (diff)
downloadFreeBSD-src-94b986ee45d924260f255854d8022435a559b674.zip
FreeBSD-src-94b986ee45d924260f255854d8022435a559b674.tar.gz
Add a sysctl to allow ZFS pools backed by zvols
Change 294329 removed the ability to build ZFS pools that are backed by zvols, because having that ability (even if it's not used) leads to deadlocks. By popular demand, I'm adding an off-by-default sysctl to reenable that ability. Reviewed by: lidl, delphij MFC after: Never Sponsored by: Spectra Logic Corp Differential Revision: https://reviews.freebsd.org/D4998
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING7
1 files changed, 7 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 1b98e40..123c05a 100644
--- a/UPDATING
+++ b/UPDATING
@@ -31,6 +31,13 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
disable the most expensive debugging functionality run
"ln -s 'abort:false,junk:false' /etc/malloc.conf".)
+20160129:
+ Building ZFS pools on top of zvols is prohibited by default. That
+ feature has never worked safely; it's always been prone to deadlocks.
+ Using a zvol as the backing store for a VM guest's virtual disk will
+ still work, even if the guest is using ZFS. Legacy behavior can be
+ restored by setting vfs.zfs.vol.recursive=1.
+
20160119:
The NONE and HPN patches has been removed from OpenSSH. They are
still available in the security/openssh-portable port.
OpenPOWER on IntegriCloud