You need a recent 12-STABLE or 13-CURRENT. It will not work on 12.0-RELEASE as it is missing required kernel features.
root@daemon:~ # freebsd-update -r 13.0-CURRENT upgradeYou need a recent 12-STABLE or 13-CURRENT. It will not work on 12.0-RELEASE as it is missing required kernel features.
freebsd-update(8) only works on -RELEASE versions.
Besides that, -CURRENT is unsupported: Topics about unsupported FreeBSD versions
freebsd-update do not support "stable" and "current", i have to download the ISO image? right?If you have to chose between -CURRENT and -STABLE, chose -STABLE. With -STABLE, you can still use the official repository and it is a supported version on this forum.
thanks very much, i will have a try, this will be very interestingThe instructions to use -SATBLE are :
- for tracking -STABLE : https://www.freebsd.org/doc/handbook/current-stable.html#stable
- for building world and kernel : https://www.freebsd.org/doc/handbook/makeworld.html
To be honest, for building world and kernel, I use a simplified version detailed here : http://www.wonkity.com/~wblock/docs/html/buildworld.html . It has never failed me so far.
/usr/ports/sysutils/zol-kmod does not exist in my 12-STABLE ports.
What is the best way to get ZFS encryption at the moment?
Edit: Nevermind! Got it sysutils/openzfs
root@molly:/usr/ports # grep zol-kmod MOVED
sysutils/zol-kmod|sysutils/openzfs-kmod|2019-06-11|Renamed to match upstream changes
Can you write more details?I can highly recommend using a setup with encrypted geli + FreeBSDs native ZFS ... the performance is by far better than encrypted-openzfs. I mean, really by far!
Are you sure that it is only the encryption that slows it down? I'll give it a try too, but I am working on something else now. It has to wait a few days.I am currently doing loads of benchmarks, the tests are by far not finished and I will publish the results as soon as I have managed to go through all the data and prepare a nice article. However, to grab a random result from my completed tests: FreeBSD geli (blocksize 4096, aes-xts with keysize 128) + native ZFS with ashift=12: READ: 72.2MiB/s, WRITE: 18.1MiB/s from a random-read-write test with 80% read requests, on a 4core AMD machine with 8GB RAM + SSD. Same machine, same test, but with openzfs-kmod, encrypted with aes-128-ccm, ashift=12, gets only 6324KiB/s READ and 1585KiB/s WRITE.
Maybe it would be better to send a bug report too when you are done.I don't think it is the crypto stuff only ... I think openzfs-kmod has some performance issues - it is much slower than the one shipped with the base system.
Can you link the bug report? I'd like to follow it.yes thats what I intend to do, the performance for non-sequential action seems really abnormally bad.