Re: nvme timeout issues with hardware and bhyve vm's

On Fri, Oct 13, 2023 at 11:47 AM Pete Wright wrote: > > > On 10/13/23 6:24 AM, Warner Losh wrote: > > > > > > On Thu, Oct 12, 2023, 10:53 PM Pete Wright > > wrote: > > > > > > > > On 10/12/23 8:45 PM, Warner Losh wrote: > > > What version is that kernel? > >

FreeBSD 14.0-RC1 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The first RC build of the 14.0-RELEASE release cycle is now available. Installation images are available for: o 14.0-RC1 amd64 GENERIC o 14.0-RC1 i386 GENERIC o 14.0-RC1 powerpc GENERIC o 14.0-RC1 powerpc64 GENERIC64 o 14.0-RC1 powerpc64le

vfs.zfs.arc.min (was: how to set vfs.zfs.arc.max in 15-current ?)

On 13/10/2023 07:46, Toomas Soome wrote: On 13. Oct 2023, at 09:35, void wrote: On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote: Set also vfs.zfs.arc.min to some value higher than zero. aha! that worked!!! :D root@beer:/root# sysctl vfs.zfs.arc.min=1073741824

Re: nvme timeout issues with hardware and bhyve vm's

On 10/13/23 6:24 AM, Warner Losh wrote: On Thu, Oct 12, 2023, 10:53 PM Pete Wright > wrote: On 10/12/23 8:45 PM, Warner Losh wrote: > What version is that kernel? oh dang i sent this to the wrong list, i'm not running current.  the

Re: issue: poudriere jail update fails after recent changes around certctl

On 13/10/23 17:42, Dag-Erling Smørgrav wrote: Alexander Leidinger writes: some change around certctl (world from 2023-10-09) has broken the poudriere jail update command. The complete install finishes, certctl is run, and then there is an exit code 1. This is because I have some certs listed

Re: issue: poudriere jail update fails after recent changes around certctl

Alexander Leidinger writes: > some change around certctl (world from 2023-10-09) has broken the > poudriere jail update command. The complete install finishes, certctl > is run, and then there is an exit code 1. This is because I have some > certs listed as untrusted, and this seems to give a

Re: nvme timeout issues with hardware and bhyve vm's

On Thu, Oct 12, 2023, 10:53 PM Pete Wright wrote: > > > On 10/12/23 8:45 PM, Warner Losh wrote: > > What version is that kernel? > > oh dang i sent this to the wrong list, i'm not running current. the > hypervisor and vm are both 13.2 and my workstation is a recent 14.0 > pre-release build.

Re: how to set vfs.zfs.arc.max in 15-current ?

On Fri, Oct 13, 2023 at 09:46:08AM +0300, Toomas Soome wrote: That is a bit odd, arc min used to be 64MB as lowest value - that is, it should never be 0. It was the default here (i.e. the value wasn't set in either loader.conf or sysctl.conf) world+kernel was built/installed today the 13th

issue: poudriere jail update fails after recent changes around certctl

Hi, some change around certctl (world from 2023-10-09) has broken the poudriere jail update command. The complete install finishes, certctl is run, and then there is an exit code 1. This is because I have some certs listed as untrusted, and this seems to give a retval of 1 inside certctl.

Re: how to set vfs.zfs.arc.max in 15-current ?

> On 13. Oct 2023, at 09:35, void wrote: > > On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote: > >> Set also vfs.zfs.arc.min to some value higher than zero. > > aha! that worked!!! :D > > root@beer:/root# sysctl vfs.zfs.arc.min=1073741824 > vfs.zfs.arc.min: 0 -> 1073741824 >

Re: how to set vfs.zfs.arc.max in 15-current ?

On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote: Set also vfs.zfs.arc.min to some value higher than zero. aha! that worked!!! :D root@beer:/root# sysctl vfs.zfs.arc.min=1073741824 vfs.zfs.arc.min: 0 -> 1073741824 root@beer:/root# sysctl vfs.zfs.arc.max=8589934592

Re: how to set vfs.zfs.arc.max in 15-current ?

> On 13 Oct 2023, at 00:59, void wrote: > >> Try reducing your arc.max by an order of 10. This suggests that it's >> probably failing in param_set_arc_max() in the val >= arc_all_memory() >> comparison.. > > Hi, thanks for replying. Sadly, your suggestion doesn't work in this case: > >