From nobody Fri Jul 30 18:14:24 2021 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id BFD9812D41C8 for ; Fri, 30 Jul 2021 18:14:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GbwXJ4zsZz3N09 for ; Fri, 30 Jul 2021 18:14:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8924417C1 for ; Fri, 30 Jul 2021 18:14:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 16UIEOfB005255 for ; Fri, 30 Jul 2021 18:14:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 16UIEOXe005254 for fs@FreeBSD.org; Fri, 30 Jul 2021 18:14:24 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 237067] ZFS: Crash in vdev_dtl_reassess when using GELI with autodetach Date: Fri, 30 Jul 2021 18:14:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, panic X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: johannes@jo-t.de X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable12? mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237067 --- Comment #2 from johannes@jo-t.de --- Just ran into a similar panic, but with ggate and ggate destroy -f, so force-destroying the ggate device that a zfs/zpool command wants to write t= o. There's a ggate specific thing here: because of a bug in ggatec it's possib= le for a read or write request to end of dangling forever. So for example a zpool-create will never finish. To get out of that sticky situation you might be inclined to run `ggatec destroy -f -u 0`. That will trigger the kernel panic. Unread portion of the kernel message buffer: code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 6 (solthread 0xfffffff) trap number =3D 12 panic: page fault cpuid =3D 0 time =3D 1627668025 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00511a8= 720 vpanic() at vpanic+0x17b/frame 0xfffffe00511a8770 panic() at panic+0x43/frame 0xfffffe00511a87d0 trap_fatal() at trap_fatal+0x391/frame 0xfffffe00511a8830 trap_pfault() at trap_pfault+0x66/frame 0xfffffe00511a8880 trap() at trap+0x4f7/frame 0xfffffe00511a8990 calltrap() at calltrap+0x8/frame 0xfffffe00511a8990 --- trap 0xc, rip =3D 0xffffffff803e838c, rsp =3D 0xfffffe00511a8a60, rbp = =3D 0xfffffe00511a8ad0 --- vdev_dtl_reassess() at vdev_dtl_reassess+0x11c/frame 0xfffffe00511a8ad0 vdev_dtl_reassess() at vdev_dtl_reassess+0x89/frame 0xfffffe00511a8b50 spa_vdev_state_exit() at spa_vdev_state_exit+0x127/frame 0xfffffe00511a8b80 spa_async_thread_vd() at spa_async_thread_vd+0xe0/frame 0xfffffe00511a8bb0 fork_exit() at fork_exit+0x85/frame 0xfffffe00511a8bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00511a8bf0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- This is on stable-12, commit 7fa95d69f10827d0b02607682a2c4a1513d658e5, with= a custom stripped down kernel, on amd64, built with DIAGNOSTIC and INVARIANTS= and stuff. I have kgdb on this box/vm. It's very reproducible. --=20 You are receiving this mail because: You are the assignee for the bug.=