Date: Sat, 13 Jan 2024 12:26:36 +0100 From: Lev Serebryakov <lev@FreeBSD.org> To: freebsd-fs <freebsd-fs@freebsd.org>, freebsd-stable <freebsd-stable@freebsd.org>, Warner Losh <imp@bsdimp.com>, Dimitry Andric <dim@FreeBSD.org> Subject: vfs.zfs.compressed_arc_enabled=0 is INCOMPATIBLE with L2ARC at least in FreeBSD 13 (Was: Crash on adding L2ARC to raidz1 pool) Message-ID: <aabed885-79ed-4a2d-9304-c56282f2f631@FreeBSD.org> In-Reply-To: <22167ed4-887d-4fe0-b0a6-36312ae38fea@FreeBSD.org> References: <22167ed4-887d-4fe0-b0a6-36312ae38fea@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08.01.2024 18:34, Lev Serebryakov wrote: I've found that all my L2ARC problems (live-locks and crashes) are result of OpenZFS bug which can not support L2ARC with un-compressed ARC (vfs.zfs.compressed_arc_enabled=0). It is NOT hardware-depended (and my NVMe is perfectly Ok and healthy) and could be easily reproduced under VM with all-virtual disks. I've opened the ticket in OpenZFS project (https://github.com/openzfs/zfs/issues/15764). Maybe, FreeBSD need ERRATA entry? Previous threads: [1] ZFS pool hangs (live-locks?) after adding L2ARC [2] Crash on adding L2ARC to raidz1 pool -- // Lev Serebryakov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aabed885-79ed-4a2d-9304-c56282f2f631>