> 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
> roo
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
vfs.zfs.arc.max:
> 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:
>
> root@
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. i'll do more homework tomorrow and post to questions
or a more
What version is that kernel?
Warner
On Thu, Oct 12, 2023, 9:41 PM Pete Wright wrote:
> hey there - i was curious if anyone has had issues with nvme devices
> recently. i'm chasing down similar issues on my workstation which has a
> physical NVMe zroot, and on a bhyve VM which has a large pool
hey there - i was curious if anyone has had issues with nvme devices
recently. i'm chasing down similar issues on my workstation which has a
physical NVMe zroot, and on a bhyve VM which has a large pool exposed as
a NVMe device (and is backed by a zvol).
on the most recent bhyve issue the VM
On Thu, Oct 12, 2023 at 11:27:49AM -0700, Cy Schubert wrote:
In message , void writes:
Is there a new way to set arc.max in 15-current?
It's no longer settable (except to "0") in main-n265801 (Oct 7th)
while multiuser.
# sysctl vfs.zfs.arc.max=8589934592
vfs.zfs.arc.max: 0
sysctl: vfs.zfs.arc.
In message , void writes:
> Is there a new way to set arc.max in 15-current?
>
> It's no longer settable (except to "0") in main-n265801 (Oct 7th)
> while multiuser.
>
> # sysctl vfs.zfs.arc.max=8589934592
> vfs.zfs.arc.max: 0
> sysctl: vfs.zfs.arc.max=8589934592: Invalid argument
Try reducing you
Is there a new way to set arc.max in 15-current?
It's no longer settable (except to "0") in main-n265801 (Oct 7th)
while multiuser.
# sysctl vfs.zfs.arc.max=8589934592
vfs.zfs.arc.max: 0
sysctl: vfs.zfs.arc.max=8589934592: Invalid argument
--
