zfs tests: wait for gnop devices to disappear after "gnop destroy"
Apparently that process is asynchronous now, or maybe it's just slower
than it used to be.
MFC after: 2 weeks
Pull Request: Axcient
zfsd: listen for sysevent.fs.zfs instead of misc.fs.zfs
At some point the names of these devd events changed. Probably it
happened when importing OpenZFS. Before that, FreeBSD's sysevent_alloc
method didn't create a "class" nvpair in the event, which led to
log_sysevent using the event's ev_subclass field as its type.
MFC after: 2 weeks
Sponsored by: Axcient
The zfsd tests no longer require camcontrol
This was a harmless oversight from
11ed0a95bfa76791dc6428eb2d47a986c0c6f8a3
MFC after: 2 weeks
MFC with: 11ed0a95bfa76791dc6428eb2d47a986c0c6f8a3
Sponsored by: Axcient
Fix the zfsd_degrade_001_pos test for recent zfs versions.
It seems that ZFS now rate limits checksum errors to about 20 per
second. But zfsd's threshold for degrading a disk is 50 per minute. So
we must alternately corrupt and scrub the pool to ensure that checksum
errors are generated in multiple 1-second windows, so that zfsd will see
enough of them.
MFC after: 2 weeks
Sponsored by: Axcient
Fix the zfsd_fault_001_pos test in VMs
And, for that matter, when using NVME or SATA disks. As originally
written, the test used the da driver to inject errors. Rewrite it to
use gnop vdevs. gnop can also inject errors. It works on top of any
disk device, and it's also faster than using da.
MFC after: 2 weeks
Sponsored by: Axcient