Re: vfs.zfs.min_auto_ashift and OpenZFS

OpenZFS doesn't have the same ashift optimization logic that FreeBSD has. It's something that needs to be resolved before the code can be integrated downstream. -M On Fri, May 1, 2020 at 11:04 AM Graham Perrin wrote: > > In my sysctl.conf: > > vfs.zfs.min_auto_ashift=12 > > – if I recall

Re: vfs.zfs.min_auto_ashift and OpenZFS

Looks like it should still be there if your using the in tree ZFS: https://svnweb.freebsd.org/base/head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c?revision=358333=markup#l144 On 01/05/2020 19:03, Graham Perrin wrote: In my sysctl.conf: vfs.zfs.min_auto_ashift=12 – if I recall

vfs.zfs.min_auto_ashift and OpenZFS

In my sysctl.conf: vfs.zfs.min_auto_ashift=12 – if I recall correctly, the line was written automatically when I installed FreeBSD-CURRENT a year or so ago. With OpenZFS enabled: root@momh167-gjp4-8570p:~ # sysctl vfs.zfs.min_auto_ashift sysctl: unknown oid 'vfs.zfs.min_auto_ashift' Should

beadm no longer able to destroy, maybe since using OpenZFS

root@momh167-gjp4-8570p:~ # date ; uname -v Fri May  1 18:52:31 BST 2020 FreeBSD 13.0-CURRENT #54 r360237: Fri Apr 24 09:10:37 BST 2020 root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG root@momh167-gjp4-8570p:~ # beadm list BE   Active Mountpoint  Space Created

Re: 32-bit powerpc head -r360311: lock order reversal between: "PROC (UMA zone)" and "kernelpmap (kernelpmap)": Is this expected?

On 2020-Apr-30, at 18:30, Mark Millard wrote: > Using artifact.ci's head -r360311 debug-kernel materials: > > https://artifact.ci.freebsd.org/snapshot/head/r360311/powerpc/powerpc/kernel*.txz > > I got the following notice: > > lock order reversal: > 1st 0x1cbb680 PROC (UMA zone) @