Date: Sun, 31 Dec 2023 17:03:31 -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: <ZZIPYzWKZ1R_pMHQ@phouka1.phouka.net> In-Reply-To: <ZZH2YIXm75emBbpp@phouka1.phouka.net> References: <ZZG0RdFTqfbfPwf7@fc.opsec.eu> <ZZH2YIXm75emBbpp@phouka1.phouka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I can crash mine with "sysctl -a" as well. Smaller test, this is sufficient to crash things: root@bsd15:~ # sysctl vfs.zfs.zio vfs.zfs.zio.deadman_log_all: 0 vfs.zfs.zio.dva_throttle_enabled: 1 vfs.zfs.ziopanic: sbuf_clear makes no sense on sbuf 0xfffff8002c8dc300 with drain cpuid = 3 time = 1704069514 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00fa502960 vpanic() at vpanic+0x131/frame 0xfffffe00fa502a90 panic() at panic+0x43/frame 0xfffffe00fa502af0 sbuf_clear() at sbuf_clear+0xa8/frame 0xfffffe00fa502b00 sbuf_cpy() at sbuf_cpy+0x56/frame 0xfffffe00fa502b20 spa_taskq_write_param() at spa_taskq_write_param+0x85/frame 0xfffffe00fa502bd0 sysctl_root_handler_locked() at sysctl_root_handler_locked+0x9c/frame 0xfffffe00fa502c20 sysctl_root() at sysctl_root+0x21e/frame 0xfffffe00fa502ca0 userland_sysctl() at userland_sysctl+0x184/frame 0xfffffe00fa502d50 sys___sysctl() at sys___sysctl+0x60/frame 0xfffffe00fa502e00 amd64_syscall() at amd64_syscall+0x153/frame 0xfffffe00fa502f30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00fa502f30 --- syscall (202, FreeBSD ELF64, __sysctl), rip = 0x3733c1e5619a, rsp = 0x3733bf494538, rbp = 0x3733bf494570 --- KDB: enter: panic [ thread pid 780 tid 100237 ] Stopped at kdb_enter+0x33: movq $0,0xe3a582(%rip) db>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZZIPYzWKZ1R_pMHQ>