Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Dec 2023 15:16:48 -0800
From:      John Kennedy <warlock@phouka.net>
To:        Kurt Jaeger <pi@freebsd.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: ZFS problems since recently ?
Message-ID:  <ZZH2YIXm75emBbpp@phouka1.phouka.net>
In-Reply-To: <ZZG0RdFTqfbfPwf7@fc.opsec.eu>
References:  <ZZG0RdFTqfbfPwf7@fc.opsec.eu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 31, 2023 at 07:34:45PM +0100, Kurt Jaeger wrote:
> Hi!
> 
> Short overview:
> - Had CURRENT system from around September
> - Upgrade on the 23th of December
> - crashes in ZFS, see
>   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538
>   for details
> - Reinstalled from scratch with new SSDs drives from
> https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/
> freebsd-openzfs-amd64-2020081900-memstick.img.xz
> - Had one crash with
>   sysctl -a
>   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> - Still see crashes with ZFS (and other) when using poudriere to
>   build ports.
> 
> Problem:
> 
> I happen to run in several cases of crashes in ZFS, some of
> them fatal (zpool non-recoverable).

  I can crash mine with "sysctl -a" as well.

  I seeded my bhyve with:
	FreeBSD-15.0-CURRENT-amd64-20231228-fb03f7f8e30d-267242-disc1.iso

  Rebuilt the kernel (so now at main-n267320-4d08b569a01) and started
crunching through poudriere package builds.  Sorta stock install of encrypted
ZFS.  I didn't get it to crash with poudriere (yet).  Mine lives in bhyve,
so maybe less possible destruction via crashes.

	KDB: stack backtrace:
	db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00fa5f3960
	vpanic() at vpanic+0x131/frame 0xfffffe00fa5f3a90
	panic() at panic+0x43/frame 0xfffffe00fa5f3af0
	sbuf_clear() at sbuf_clear+0xa8/frame 0xfffffe00fa5f3b00
	sbuf_cpy() at sbuf_cpy+0x56/frame 0xfffffe00fa5f3b20
	spa_taskq_write_param() at spa_taskq_write_param+0x85/frame 0xfffffe00fa5f3bd0
	sysctl_root_handler_locked() at sysctl_root_handler_locked+0x9c/frame 0xfffffe00fa5f3c20
	sysctl_root() at sysctl_root+0x21e/frame 0xfffffe00fa5f3ca0
	userland_sysctl() at userland_sysctl+0x184/frame 0xfffffe00fa5f3d50
	sys___sysctl() at sys___sysctl+0x60/frame 0xfffffe00fa5f3e00
	amd64_syscall() at amd64_syscall+0x153/frame 0xfffffe00fa5f3f30
	fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00fa5f3f30
	--- syscall (202, FreeBSD ELF64, __sysctl), rip = 0x22e42167019a, rsp = 0x22e41ee72518, rbp = 0x22e41ee72550 ---
	KDB: enter: panic

  The sysctl died at this point, but who knows if it had pending buffered output or anything...

	...
	vfs.zfs.zio.deadman_log_all: 0
	vfs.zfs.zio.dva_throttle_enabled: 1
	vfs.zfs.zio.requeue_io_start_cut_in_line: 1
	vfs.zfs.zio.slow_io_ms: 30000
	vfs.zfs.zio.taskq_wr_iss_ncpus: 0




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZZH2YIXm75emBbpp>