From nobody Sun Feb 26 17:35:29 2023 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 4PPrPb1bVPz3tqkp for ; Sun, 26 Feb 2023 17:35:31 +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 4PPrPZ4c3Rz41lk for ; Sun, 26 Feb 2023 17:35:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677432930; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9h/vrexZzP9BYXjFafpGCB4aoDDKU0Op/p8w0vV33n4=; b=Hel811nnXZqi/ntWYoW5OhattcUUtwUZX9tEkYezlkbuopd20CGhNfp/Ov+n5EgfKDcCZw x0DwfW1NgeCa93HJkXIA4j0BWAqnXNerWn4QmSvsUHtNx2DCDlMFC9wjIIRhMqeXZeEYrD 6iO0S+bxSkndl4h3ycEKrwi60SSdJ5iyWcMbhKqJBh9nSiwMYEqZ75zDjWrVK+96Eiujbu ZHmglptTEYPS6gu4Z0fJ2ZKEqqHHak5A+Rz6KMDsSR6kvjmim0M2+TZ8p582YQUe6Ovkde O68wddll2/ga9WCAVHazKe1/F2/bsT3GhKa8FSgvjn08++A7kkD+h/eK8FSuFQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677432930; a=rsa-sha256; cv=none; b=LZokOuLr3KFTRLLBmu7fCHBsNjW22aqCw+g0ngemNkuJfhHkXohRPjNNsgwX9Dt+tf5squ glUVc+n1nmkBTtIvlh2SdKx19KG4/7EB6ms9CTFvmuqYDBbktmekElcHdp6K7DvMz0vcK8 SBmAY1F7V+cjK18qR0lbgZLTsSQJxe5AG00MOzik8j6YX0iO2CJqmWcAtApxCoXK0NEbdx pmv9sSHpQAvt/H1lLVFegbal1prPHtRRxQn2o8F2mento8gKyC47plkTDFJIN8nKdBacvN gBb/1SLvZhzZ9V30/Rq74OcXdw7vGqasvpsi6jNeifhGTZLLIQo33m651Y8wxA== 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 4PPrPZ3j8lztR3 for ; Sun, 26 Feb 2023 17:35:30 +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 31QHZUH9085621 for ; Sun, 26 Feb 2023 17:35:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31QHZU8i085620 for fs@FreeBSD.org; Sun, 26 Feb 2023 17:35:30 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 267028] kernel panics when booting with ZFS and amdgpu.ko (both are required) Date: Sun, 26 Feb 2023 17:35:29 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: george@m5p.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? X-Bugzilla-Changed-Fields: attachments.created 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=3D267028 --- Comment #80 from George Mitchell --- Created attachment 240427 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D240427&action= =3Dedit New version of the crash, from acpi_wmi Here's another module that doesn't get along well with amdgpu.ko on my syst= em: acpi_wmi.ko. Other than that this crash looks identical to all the earlier ones, as far as I can tell. It's been about a dozen boot-up tries since I put zfs_load=3D"YES" into /boot/loader.conf (so that ZFS gets loaded early to minimize its interaction with amdgpu.ko) and vboxnet_enable=3D"NO" in /etc/rc.conf (so that vboxnetf= lt.ko doesn't get its chance to cause trouble either) until I got this new crash. I'll mention again that this crash always happens within a minute of booting up, or else never. Anyone have any ideas about what acpi_wmi.ko has in com= mon with zfs.ko and vboxnetflt.ko? --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From nobody Sun Feb 26 20:15:09 2023 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 4PPvxp0TDzz3v17y for ; Sun, 26 Feb 2023 20:15:10 +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 4PPvxn6RVkz4HhK for ; Sun, 26 Feb 2023 20:15:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677442509; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=05WW4iQ4Ql0AsWod2X3Vb3IWhVIN3tRTrBwzMuOuqh4=; b=jZ7eB0XayUWvVrR3U7d+RA7kxxnGjirdzyymF1cXET4ysFxrwd/Ng4rSU7vhcmCJ3mMdvI 0gKgid5DMYbhTfb1wMefRK7g7mpEP2+GnoZqjOoFqcy/uHBONDCm44WMMqjR4iDgzGImQp WnQdPcn8HCRc2+TrpcGDnBoXGB7ulMyOISO6oIULrgC+J43Hk2jrKY4Htuvq0z/wUCrAzr v8K/Bdy69eoHGmPG7L9JQFJiouKJsaecuRpiwOaEhWtEwzAJ2wNo17EoR6HqMj/gJFYVNU aAYfv8YLa5mDzX+8cqKnU8WllcFhSjZ2Og3Xubov+Fgf0puXX9EDlPTObEdD/w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677442509; a=rsa-sha256; cv=none; b=yD213Ix9SXuZ2z+Sy3Pc1UdQkmiva2rcCaaBzcnpMn8yvLpzP5xXxQWf6IK/D17wLutAiH HXI6KHxxbmz4/SB2x5lChFQsHb4vSrKtl6TXD3BQS2I8B7ztMp1cIRulJDqUunn2ouAz0d KOq+7rkOqraSsDCYTZibjC/LRZaCP6xI3dbWD1zxVfP5q5OzAAVXuUFWOoq7Rw2FzN64t1 OxKr0WOGwwfVSA70OLIw0Qt8TAHWJyaqnjJEnhsvlN3xRj8qTFEVRTjQWpsX7NZvtAWuuN g2Kfs0NmZYXn0Cl4wboOYXgLeiQKnEc7gRA1dXBodAYdhNLFR2Uq0g7E7h3DaA== 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 4PPvxn5WHvzyLY for ; Sun, 26 Feb 2023 20:15:09 +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 31QKF9eR034064 for ; Sun, 26 Feb 2023 20:15:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31QKF9FB034063 for fs@FreeBSD.org; Sun, 26 Feb 2023 20:15:09 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 267028] kernel panics when booting with ZFS and amdgpu.ko (both are required) Date: Sun, 26 Feb 2023 20:15:09 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #81 from Mark Millard --- (In reply to George Mitchell from comment #80) There are multiple, distinct backtraces in your various examples. This one matches the 4 still-listed-as Obsolete ones and the "Latest crash dump" one, but not the others (if I remember right). So it is another example where there is no mention of dbuf or of zfs in the backtrace's text, unlike some other backtraces. So far as I can tell, there still has been no evidence gathering seeing if the problem can happen absent zfs being loaded or zfs loaded but no pools ever imported. If I gather correctly, we now do have evidence that the specific type of backtrace can happen without vboxnetflt.ko ever having been loaded, proving it is not necessary for that kind of failure. That is a form of progress as far as evidence goes. It also suggests that merely being listed in a backtrace does not mean that fact necessarily tells one much about the basic problem. There is some possibility here that there is more than one basic problem and some of the backtrace variability is associated with that. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From nobody Sun Feb 26 20:56:08 2023 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 4PPws50xc4z3v4BW for ; Sun, 26 Feb 2023 20:56:09 +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 4PPws46jwZz4L48 for ; Sun, 26 Feb 2023 20:56:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677444968; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yt6dFQqzTt8BnondcP6IcETq6GVvZAEZvYLhTrGRIKs=; b=HL2+WISd4WF12jS149lTsE4Chabx0mqHqd1dfRcbK8q+7zgLxuGxNAIARF47Hku/Dm6a5J IFPzpvHkmQuio2QLUSkUkoCkSxqeLV9kYosmopMmZ24DkM29AVmIvXmC0jCYZMgJUIpFp1 N3Ozlr6FIYHS7DT4io99DUGAsvu8/U3sKToAFkx6YnkCLzFleiUuU1dJDCjPS0OCIe1xSD II7zAYulotuyjs4e8r3eLnWf2PnqYvyAA6F7E5FDMgRZemFNVlqILQqFfPNUDqR8oehWfF XMtS3XOMdqaone2wGor2fWsWCtGvfERiMMcd0RA1/LaspfXD0Lh60jucoTv8Ag== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677444968; a=rsa-sha256; cv=none; b=OXH5wKbJ+H4PVGl43lkDIidHbFq02QgHaahXQEz3D6NotjtuMSYyUKGvAWypcVL6qLc6GC b/PPP4kWHZREQT3dJohlDp7X8sq+Ab2ylpJz6+vSTVB9GI34beJYpQzArdB1o+eR9t1Mah /O3PJyCCXtJMl6oR9g7xURqPjbtER3B24gmj1QB6Zfbw+LNel0esK/7+c1cXsN6TporAZr bPqQWV2SwGjZVV/o2H1WgyxRudGDzgirPrRTpX/hgA6VNsXOc2iHOnsYPMxL7jYmXSltYB kjk1jUtuaii6m/Kfsbv8bnPYCmZYQXNYViFomYkPgovsmuvxGOwQ2t7ZdiIPYA== 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 4PPws45hR5z10hx for ; Sun, 26 Feb 2023 20:56:08 +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 31QKu8GT088449 for ; Sun, 26 Feb 2023 20:56:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31QKu8gZ088448 for fs@FreeBSD.org; Sun, 26 Feb 2023 20:56:08 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 267028] kernel panics when booting with ZFS and amdgpu.ko (both are required) Date: Sun, 26 Feb 2023 20:56:08 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #82 from Mark Millard --- Using the gdb-based backtrace information: #8 0xffffffff80be8c5d in modlist_lookup (name=3D0xfffff80006217400 "acpi_w= mi",=20 ver=3D0) at /usr/src/sys/kern/kern_linker.c:1487 is for the strcmp code line in: static modlist_t modlist_lookup(const char *name, int ver) { modlist_t mod; TAILQ_FOREACH(mod, &found_modules, link) { if (strcmp(mod->name, name) =3D=3D 0 && (ver =3D=3D 0 || mod->version =3D=3D ver)) return (mod); } return (NULL); } We also see that strcmp was called via: #6 #7 strcmp (s1=3D, s2=3D) at /usr/src/sys/libkern/strcmp.c:46 We also see name was accessible, as shown in the "#8" line above. We see from #7 that strcmp was considered called, suggesting that the mod->name of itself did not fail. The implication would be that that value of name in mod->name was a bad pointer when strcmp tried to use the value. Nothing says that mod->name was or should have been for acpi_wmi at all. The "acpi_wmi" side of the comparison need not be relevant information. Other backtraces that look similar may well have a similar status for the name in the right had argument to the strcmp. This might be a useful hint to someone with appropriate background or suggest some way of detecting the bad value in mod->name earlier when that earlier context might be of more use for investigations. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From nobody Sun Feb 26 21:01:01 2023 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 4PPwyk2l9Hz3v4SD for ; Sun, 26 Feb 2023 21:01:02 +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 4PPwyj4Bzbz4PcG for ; Sun, 26 Feb 2023 21:01:01 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677445261; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=K1Tu1qHy+Ke6Yh+qyNKSgN7JqrPP2uFkhjvxTpm/W8k=; b=DNfWso3qpc6sogSiD3FFhshL8wd8s7ifFDilq24jH+UaC2p7ubxTOye5tH8eHMuoLneakH fwdyXkYHB/wVAycmna5elIK6qkCxuoCsfHzGdsdPAkd2JVs2lM0xKtaeF7U099WJXs//6s hPRlojpXnKdADbugTG3kqL0RN3TKYto8Is9L1tYmBd8zpSaOi6cEhnWOjuCp5y3WRnSarV ewQfejDBp0CxiTTyW6Hnfeuhfc8AXmvMmCjyeCixB60st6ikCT3jUhWYtsC2MpbwwrRfBU Y6yDJ+1aKw8Ex8Q5+BW8dwURdkdF6kAVLZlKx6rRQ0pVajT04ubxQMC/QX/WjQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677445261; a=rsa-sha256; cv=none; b=wfKcv1ovdc7SXgOUGLM7UWPyxDfbGtt5v8lsfoScfMTNxOiECywQhr5qTA2aVVEw/f3FKS h21DT+CL2sdmKRV/oJlJZlkvPFPWCFanP0xoeVIH29BsxzjA8A4F+EKJi3tCDpwLclTAjy pI8C5AMMi7+ValTwG2yO8zURaLbxvn2nHD03E00Ik7jjH7wj4FEav+eBdQ6GbLHGvyZXFR acbpkTHofEyl7O1NVOOeUd9FHN/FV/4inKKr8HUZbv2DSzjPk4dXu8gtrMtggiRs7HzcDq PfLBsWsL6TU+vAFW4XXNvzlYgrCxRBtGW6cyAREiEDO4Py5S5Poj1wRjNTtq+w== 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 4PPwyj3HmVz10Rf for ; Sun, 26 Feb 2023 21:01:01 +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 31QL11E6097193 for ; Sun, 26 Feb 2023 21:01:01 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31QL11UN097192 for fs@FreeBSD.org; Sun, 26 Feb 2023 21:01:01 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202302262101.31QL11UN097192@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 26 Feb 2023 21:01:01 +0000 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 Content-Type: multipart/alternative; boundary="16774452612.CF447aD6.89831" Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N --16774452612.CF447aD6.89831 Date: Sun, 26 Feb 2023 21:01:01 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 211491 | System hangs after "Uptime" on reboot with ZFS Open | 237067 | ZFS: Crash in vdev_dtl_reassess when using GELI w Open | 240831 | zfs: Panic during snapshot on 12.1-STABLE r352648 Open | 243973 | [zfs] rollback segmentation fault Open | 244656 | zfs: resilver doesn't provide enough information Open | 244692 | gjournal: Does not support TRIM Open | 251035 | ZFS: Allow 64 bit ZFS to support 32 bit ioctls (W Open | 269503 | docs.freebsd.org: default vfs.zfs.arc.meta_limit 8 problems total for which you should take action. --16774452612.CF447aD6.89831 Date: Sun, 26 Feb 2023 21:01:01 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" 
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status      |    Bug Id | Description
------------+-----------+---------------------------------------------------
Open        |    211491 | System hangs after "Uptime" on reboot with ZFS
Open        |    237067 | ZFS: Crash in vdev_dtl_reassess when using GELI w
Open        |    240831 | zfs: Panic during snapshot on 12.1-STABLE r352648
Open        |    243973 | [zfs] rollback segmentation fault
Open        |    244656 | zfs: resilver doesn't provide enough information 
Open        |    244692 | gjournal: Does not support TRIM
Open        |    251035 | ZFS: Allow 64 bit ZFS to support 32 bit ioctls (W
Open        |    269503 | docs.freebsd.org: default vfs.zfs.arc.meta_limit

8 problems total for which you should take action.
--16774452612.CF447aD6.89831-- From nobody Sun Feb 26 21:44:13 2023 X-Original-To: freebsd-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 4PPxwx2fmGz3v6pM for ; Sun, 26 Feb 2023 21:44:33 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic307-55.consmr.mail.gq1.yahoo.com (sonic307-55.consmr.mail.gq1.yahoo.com [98.137.64.31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PPxww07c9z4T8B for ; Sun, 26 Feb 2023 21:44:31 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=I8YwRhJv; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.64.31 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1677447870; bh=Kdenzm6bfxpUZYSDf4jmxplP2d+Tn10iAXvRVoI8sQ0=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=I8YwRhJvHI+vLDBVQDhCo3lp+Gwqnj1bRZCKSbxFL0IPwXfVf+RpnbYYZpg2bncHBnOcUhlqGgod9Q17XRZ4r56HOAss1WY6dORDczOFB+EkvQH/4gZngZ2mho8u+hV1OFC58Ie60Fz+fuRN0OEdnaTTYKE4J4t/LcU1Jk4qzB1DCNgH/Aq69vMcRE8R/BrZtslVA8XlgZjDR4uVPfUJCziG8/VQBQbnfn/Vay7/vb3I3oUSCq4znntRdaJJ27wBVa0Cl1EI9nWrOdioJgeL6hPPWGAf/xg2JBNrU9x16/Ta1iu189Kqtvhb364ReYm3m8WGBC1iMCWT/AoqoxK/0g== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1677447870; bh=HYuUhdOZrUfwxoI70nrF03EwGrN+CV5pn5CRSwA6Lc0=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=tcA2lzwX3BoWN38ftn78qroM+wxj5cv6GTjTL6Ff+9iv2c9P/PGXFEBrajkLXAmiGrT6hj6QFxAx8Hri8DP6MIw/PRil0r6HmoXMd/ylbDXM+UOmHHGq4KseDkmWicUdm7Ee+yrYV3BEulcCUNeFQRUwYaxk67JLl9deV63vS5ld79xiviKFapmQnnTj4PnePkjQ3Gi9mpuDbn0E/z9utu/DU0W95oHtRIgFv5pKzhbuElg7h2Ure9EpFtmFvoASbLqGc/ECqvmPnfde6Ay0rHJ5ULmR1O152sxbLq2AvOu6stG467UtsrkXZK6aSwiy3UsVv0OPczqwY0Ozmxi5tg== X-YMail-OSG: 7jHc_rYVM1nlx3w.BD85VHVYjt6PSsEmM0U_eL2LR.N4FpQnelGp4j9km1_i6jh 87Ixofa1tzH.6_zrn9VdtswrmUJXXjhWMa8k0PPzU3SQ6OET4vJh5o6afgqobuKyNsJf3BMIboKs Z3Mi8R7ITHrkQklcPSybo7pZsLOpXbnYDvAxrTq.DubxTWCQ7kHz1_zSdjQ9cxC4qNNktdfl7p5V XmueNqyDtaynbZiSgyDHapGf01psffUgPHwayQr05gLCKON2jUWyE9NJO_Eh5fk9n.IuiHFHnMZb BJKUflUFb5yAvxqBNOH.t3LMZuiE5B779bi.9yGYDZmQEXFQkJgcOV8umcqPS_AJN3gSAR7AHjaJ MpGGu71qeg9YlkcEIEDByuOYF2BdHyaOOrvNU0SEZ25MkXUfx2uWf2xGH125.3SpvQIH18C1OLtp d0XsmSpzM1TpGyCqDh7kbAyL4TBqJw.dfA_LD5ClW8ibZtHXuPa8Zb7BmHkI9JIO0xLse5JZ_p2p .9_TYFFSHRFwQANEIMu2PiMuXpNbn6UlB2fZ1C69U9adrzXtrNjK.8gxLT_IeoH8HxpgQM.kmCb8 NeoHtJ0RmcVLvz3pZOsTM85_mUTeH43Jt7HkcnE5KMqM9jlArzhT23glMKlLl_rR6jQr4dY5da_1 FSAj2Ta_8i_Dpzu6aoyBfk_kjxuGH.1EwktijKAx2lw7EtTMvC.krepATtFpOsQGmCne7i5fD7ZG 0zT0ra6_HjYsl.rjut5IWYV9vOK6XmToQWSfByzLRLY0sxKuMB2AAXwSbYILRLQcdaP4g8a88XwC UooazDjfpnUjxvi1VtAk5cVLdyMPawWO6n1xyYCCsAwnkb23fxi5NlYB7xNEv9RsNUTAYymxrZsp Og5jJF70tWKdLxdajm5G5iyVAjgmoiIg7XC7wEAnlyiWOOu7Flk6Ga3hpifBV3FZE0jOpjQon8bv pMcBMHAnveCUR3bROSDAwVm6vg7QaIirw2cni3fe7TTDLyyKvMlN1yyPRkl83nKqBaKiW9E87fsg mXdCAgx12Zd4n0OOYSH6F3gSxOHY1813_BzHJe4IP1bbHK0Wn_YBPACVYS6IbP6nk1oLJSQPPtwP 3GE.NCEmHVm6_W3hnk_Wc3tEAnL5hCkitC8C7scu0fNFg2wBh9GCmJFQiR4c5flqzGGC03sEwPhl dJ.2QgfJl1r1yG26MSzJJedGkJz9LrxqI45bXeSZK2foSnkL4OcIeaWotE65RlnTZXtTkcIcvpqW 2Fg1iL.jAVYfDMqMDleyCKc9rYu5iZhIr1pr.fgDUI0MJhWjSoOqncry5rpFr2qKDAjYi3b1yQ_S UwCqRRCUiZuYUFn7CI7QOvnI_R2fGI4J5qbBYeL5mN70DwCHbBh8YPnVpijEpwgtuxUL6JrtLJIM 54L31odJZ0X5856_rgpb4rk3HEi9_S0pHyCxBYOoAoEeU2R_Xw5D7arBXulRBhtNBJzoc7wFf3YS TkU_iWByHXpDxJhU.FLSHFDBREzr1_fJzSU6sRiDM38sxF1_rw2XH0hMaKdHHjd2aN1jJAb8.zKv AzYD57guS1pZYCDodYdnO2kRTPq8Al1hYKmYza9Pa8g7ODMG296flGBtjfBdtwWy_Ymz_HH9q39M JyILMpDmUigf3lsRxFzrjzJ2eaU6kIz8L5TaxzbzxKTEG3ckoQHhF_YcKqmqimNXm5LZadgkixde _yRPcUZU3kb.kbwf10Qxd0jChOVVTuR2QEAZwsNhMYupBB0DJztT4oXzWX0gYhh5c6.6lMFgfxYy q6FmphfTlLcOjOqP4osJQA.0HsCq_KvReeuQ_mGGoHAwRZvMRRKG.vjdzl5DRs8h4KmO4oanXvCa CJ6M7p6jxU1A6IrNfl2aZ8pvm61w8a1OKI0uCukx_x37C6cA3WDMSJtMjWEwKEJcf.X1wAANgIRw G1AU0SNqpcU6qavEQppe0FAnd2Y3qdLUYmhOdhCfG5pk8F60FYrOrJUuVqBjNeBMI9fVCdEZ1.hb NhqLmaCCkcgW56mnuqJY2rjA1ePzeVZUrk6JgZuNIKnmUtTEU3zeR4mmLRtnOLYFTZlkzshYG365 3KMG8OBtOG7Chs7uX3gHYECS7bfcESgcVRg50wtPX4QreRIFclyBirlDc.ABsjhLRpeUhF0PQIbp t93bAKKHqszcE.nDqEwdCKFd.ok701G.MR8uQcjVQo9huU1X3_i9Gbc6ktbsTGARy2.NUpPoUoLA fPFA_gt65alj8ziBkmYR2XQ6S5MKKFzgo5SE27TTH_Wi2QAaHrdqmqEs0OxEdVg-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.gq1.yahoo.com with HTTP; Sun, 26 Feb 2023 21:44:30 +0000 Received: by hermes--production-ne1-746bc6c6c4-b28lr (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 6fb48239348e98d124d0fa33737d466b; Sun, 26 Feb 2023 21:44:25 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Subject: releng/13.1 context: sys/contrib/openzfs/module/avl/avl.c 's avl_destroy_nodes : lack of appropriately locked context for its use? Wild pointer? Message-Id: Date: Sun, 26 Feb 2023 13:44:13 -0800 To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.3731.400.51.1.1) References: X-Spamd-Result: default: False [-2.36 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-0.86)[-0.857]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.31:from]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org] X-Rspamd-Queue-Id: 4PPxww07c9z4T8B X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Note: This question came up while looking at one type of crash backtrace reported in: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 There is the code: void * avl_destroy_nodes(avl_tree_t *tree, void **cookie) { . . . /* * If we just removed a right child or there isn't one, go up to = parent. */ if (child =3D=3D 1 || parent->avl_child[1] =3D=3D NULL) { node =3D parent; parent =3D AVL_XPARENT(parent); goto done; } /* * Do parent's right child, then leftmost descendent. */ node =3D parent->avl_child[1]; while (node->avl_child[0] !=3D NULL) { parent =3D node; node =3D node->avl_child[0]; } . . . some gdb backtraces report that the "while" line above had a "signal handler called" result. If the avl tree were invariant over avl_destroy_nodes it looks like a wild pointer would need to be the value in a accessed node->avl_child[0] in order for the code to fail. But, if the avl tree was being separately updated during the avl_destroy_nodes activity, that could substitute in a NULL that "node =3D node->avl_child[0];" could get a copy of. Does anyone know which of these is a possibility? Both? The information would be good to add to the bugzilla submittal's comments if it helps narrow down anything. (I supposed a failed context synchronization across some context change, say a cpu migration, could be another way to get an odd value.) For reference, one of the example backtraces is: #6 #7 avl_destroy_nodes (tree=3Dtree@entry=3D0xfffff8003fa1bea0,=20 cookie=3Dcookie@entry=3D0xfffffe0075f2fdd0) at /usr/src/sys/contrib/openzfs/module/avl/avl.c:1023 #8 0xffffffff823dd768 in mze_destroy (zap=3D0xfffff8003fa1bd80) at /usr/src/sys/contrib/openzfs/module/zfs/zap_micro.c:402 #9 zap_evict_sync (dbu=3D0xfffff8003fa1bd80) at /usr/src/sys/contrib/openzfs/module/zfs/zap_micro.c:887 #10 0xffffffff822ae74a in dbuf_evict_user (db=3D0xfffff800391f3378) at /usr/src/sys/contrib/openzfs/module/zfs/dbuf.c:570 #11 dbuf_clear_data (db=3D0xfffff800391f3378) at /usr/src/sys/contrib/openzfs/module/zfs/dbuf.c:1131 #12 dbuf_destroy (db=3D0xfffff800391f3378) at /usr/src/sys/contrib/openzfs/module/zfs/dbuf.c:2804 #13 0xffffffff822b4129 in dbuf_evict_one () at /usr/src/sys/contrib/openzfs/module/zfs/dbuf.c:704 #14 0xffffffff822ac43d in dbuf_evict_thread (unused=3Dunused@entry=3D0x0) at /usr/src/sys/contrib/openzfs/module/zfs/dbuf.c:742 #15 0xffffffff80bd8a9e in fork_exit ( callout=3D0xffffffff822ac120 , arg=3D0x0,=20 frame=3D0xfffffe0075f2ff40) at /usr/src/sys/kern/kern_fork.c:1093 #16 #17 mi_startup () at /usr/src/sys/kern/init_main.c:322 #18 0xffffffff80f76c49 in swapper () at /usr/src/sys/vm/vm_swapout.c:755 #19 0xffffffff80385022 in btext () at = /usr/src/sys/amd64/amd64/locore.S:80 =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Sun Feb 26 23:21:09 2023 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 4PQ04Q1nbNz3vCWL for ; Sun, 26 Feb 2023 23:21:10 +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 4PQ04Q0jkFz4c61 for ; Sun, 26 Feb 2023 23:21:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677453670; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dbtALVLyV+VAjZfxVNNTvg/mD4hmGxh0DAuehAnDrU4=; b=VbP3QbQhuWNm0/+jHgiHFvIpJr+5GP19p7YZP01HiFKqtcWSJoHzPq9g6wGDukGoa3Wj+J pFE68Oj2cc9z7Rp6CWhFBF2/ZMfXB5TI6FS+Mz2AB3Nvvnn6Sn8MFFlh8bGmPRCQim0zXm FNV8Qav8+ZVruLv+BmzZMZJgpu4+c+v06haWy0MgQ6gQ1kdAN/yyREsDOf7jeESSprhQoi F6qAAPacr57N+MVIA9rECuJLyplGjZLhhtZILQ6ImrQvsWNfakh0ritfSw31/0YyoYt21U ltO+z6Lk3xkhzoTWrVfGFUWyxqT2JzO8B6kDrv8TOfYeneglTo1ZLXzcGnDsrg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677453670; a=rsa-sha256; cv=none; b=pfCxkWmJneVqwYo82NRuGXOL7Zb0tRkoiAyTUG/jYtclPAY4jsC5QhD2bKWg+ZqYJLT9l+ aNbmwAWE6Z7x2csEA3sYTbeuyenvTfvAZbyL/wv585gBIHgUpNjx/71q7I2qaxLKLAYdNw B1jD4EpYaPxHCW0FtZ8Mv8U5ryrqelXWJP+WVESwVOpmAagNABEHWWGaRMrQIgDNz2xAd7 GewULBnwsWOi4zBwl6RIjBn/BdmalsW6imiQrziBGriVe1mhxjku4TLbD4JHZoVO7Sygkk JGl/1430vUak3oaYV7StxXCxbD0DLpF5Uj5hO2jlN81GYnagxb6VTQ1PXQpl4g== 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 4PQ04P6xdvz142j for ; Sun, 26 Feb 2023 23:21:09 +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 31QNL9lT004261 for ; Sun, 26 Feb 2023 23:21:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31QNL9eV004259 for fs@FreeBSD.org; Sun, 26 Feb 2023 23:21:09 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Sun, 26 Feb 2023 23:21:09 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: george@m5p.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? X-Bugzilla-Changed-Fields: short_desc 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=3D267028 George Mitchell changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|kernel panics when booting |kernel panics when booting |with ZFS and amdgpu.ko |with both (zfs,ko or |(both are required) |vboxnetflt,ko or | |acpi_wmi.ko) and amdgpu.ko --- Comment #83 from George Mitchell --- I have set up a disk with FREEBSD 13.1-RELEASE-p7 and drm-510-kmod 5.10.113= _8 WITHOUT ZFS and vbox-anything. I don't know how to avoid loading acpi-wmi.= ko.=20 So far it hasn't crashed, but I will try a whole bunch of reboots tomorrow = with that disk. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From nobody Sun Feb 26 23:59:06 2023 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 4PQ0wC0GS7z3vFnC for ; Sun, 26 Feb 2023 23:59:07 +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 4PQ0wB5VjTz4lPw for ; Sun, 26 Feb 2023 23:59:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677455946; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GRpL9M1PCgbYZT0qUzmDmW5i7JaWvAr1xlpJ2yVGBnU=; b=pEh/3ybaVL8ZDM86Jhwy0kGYSsBDCLqVHAxkH8P2Lulvpk/gdN4nj9cdI9joPUPDwgiVmw oMrG1Uq9rSKYj0gL6BSZ/JTxvyLGeqJbkClkOYla95ma3CM1oIzStBI1ptxPukG6F0T4wh Az7amM9oC2pVDrVSZcnoZTNfyc3Fgr2Lo43wDxHRO6CYeJFSXcP+5+Y1BYD/Lva+V0S8Bq 0MWiUAhVPq5U2ric0NahGBlPRefG576i+DBjbnkr/5tzijtxnF0P3apxYJYMD3tCRju9/D 5azVnuyUu+xy1FM+eOo1wc6UXCYRfHmPxb1oivZVwlC855K9vrjLDvL95wzUPQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677455946; a=rsa-sha256; cv=none; b=gzUwa5pO1P6aJZPIcYL0QckreX7cXdoPxFM7GL36uHuruNumpJ4iKlzhaE9cr6vedxjr3b BRRc7HelGQMpzqJ5LN8n1jOq6lcSMz5r/XZFCKALUXMfcnlk2irI3NR8tL1iG94m6Ew2IX RONcGdzsWZhPOWbIVfXKgwaRygtJqXCgj7J0SUNUyh/G7R/heGwwFLTJ7KnaJX00RNHuwP S2hVvuPv2sgfvtiIU7DPBV8huSci6FAvSAdepjVOhDXnr4cGWfnKn9PpJhFPFbtuk/sSMg psoZ5yFBXSzMhonovIISs5b/JJgiiaWdu3qI1EqF9pe+Q01b2YjD1fpwD4l7MQ== 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 4PQ0wB4TPzz14r7 for ; Sun, 26 Feb 2023 23:59:06 +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 31QNx6a0057293 for ; Sun, 26 Feb 2023 23:59:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31QNx6lo057292 for fs@FreeBSD.org; Sun, 26 Feb 2023 23:59:06 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Sun, 26 Feb 2023 23:59:06 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #84 from Mark Millard --- (In reply to George Mitchell from comment #83) I found the following text on https://cateee.net/lkddb/web-lkddb/ACPI_WMI.h= tml : QUOTE ACPI-WMI is a proprietary extension to ACPI to expose parts of the ACPI firmware to userspace - this is done through various vendor defined methods= and data blocks in a PNP0C14 device, which are then made available for userspac= e to call. The implementation of this in Linux currently only exposes this to other ke= rnel space drivers. This driver is a required dependency to build the firmware specific drivers needed on many machines, including Acer and HP laptops. END QUOTE So, I expect that if acpi_wmi.ko is being loaded by FreeBSD, it may well be a requirement for that machine to boot and/or operate via ACPI. But I'm not familiar with the details. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From nobody Mon Feb 27 08:38:47 2023 X-Original-To: freebsd-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 4PQDRv3yYqz3tpYH for ; Mon, 27 Feb 2023 08:38:51 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Received: from unimail.uni-dortmund.de (mx1.hrz.uni-dortmund.de [129.217.128.51]) (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 (2048 bits) client-digest SHA256) (Client CN "unimail.tu-dortmund.de", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PQDRt4HF6z4333 for ; Mon, 27 Feb 2023 08:38:50 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tu-dortmund.de header.s=unimail header.b=DJp59A3w; spf=pass (mx1.freebsd.org: domain of alexander.lochmann@tu-dortmund.de designates 129.217.128.51 as permitted sender) smtp.mailfrom=alexander.lochmann@tu-dortmund.de; dmarc=none Received: from [192.168.111.37] (i5C750090.versanet.de [92.117.0.144]) (authenticated bits=0) by unimail.uni-dortmund.de (8.17.1.9/8.17.1) with ESMTPSA id 31R8cmkY025019 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT); Mon, 27 Feb 2023 09:38:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tu-dortmund.de; s=unimail; t=1677487128; bh=piibla1asmdfImOs7ydxbN69/aOPBOl+c/rXeoF8aqg=; h=Date:To:Cc:References:From:Subject:In-Reply-To; b=DJp59A3wFZAQt4KpIog2kDy/P/Yq+zcrZMiBkaidpzr0tbACDWIq9no7StNlHcwxt 0bpaPgpoLq+QmVb8NBSYhjgjkf+PwCpYsbEzd1DznB5EI9B9hpEBqqGYvo6i9GTgJu 1+Ne7gpml2dT8nx/5UAOW2ofktWdrL5KKjJV+iU4= Message-ID: <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> Date: Mon, 27 Feb 2023 09:38:47 +0100 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 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Content-Language: de-DE-1901, en-US To: Konstantin Belousov Cc: freebsd-fs@freebsd.org References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> From: Alexander Lochmann Subject: Re: Understanding locking for buf In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------1K0yL62K0inSR0ruxTeZisgi" X-Spamd-Result: default: False [-7.30 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[tu-dortmund.de:dkim]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_DKIM_ALLOW(-0.20)[tu-dortmund.de:s=unimail]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; R_SPF_ALLOW(-0.20)[+ip4:129.217.128.0/24]; RCVD_IN_DNSWL_MED(-0.20)[129.217.128.51:from]; RWL_MAILSPIKE_GOOD(-0.10)[129.217.128.51:from]; MIME_BASE64_TEXT(0.10)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[tu-dortmund.de]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:680, ipnet:129.217.0.0/16, country:DE]; DKIM_TRACE(0.00)[tu-dortmund.de:+]; HAS_ATTACHMENT(0.00)[]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4PQDRt4HF6z4333 X-Spamd-Bar: ------- X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------1K0yL62K0inSR0ruxTeZisgi Content-Type: multipart/mixed; boundary="------------jRydQZMlaYDmZwf5fxyKbzDW"; protected-headers="v1" From: Alexander Lochmann To: Konstantin Belousov Cc: freebsd-fs@freebsd.org Message-ID: <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> Subject: Re: Understanding locking for buf References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> In-Reply-To: --------------jRydQZMlaYDmZwf5fxyKbzDW Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMjQuMDIuMjMgMjE6NDEsIEtvbnN0YW50aW4gQmVsb3Vzb3Ygd3JvdGU6DQo+PiBWaWV3 aW5nIGl0IGZyb20gYSBkaWZmZXJlbnQgYW5nbGU6IEFyZSBhY2Nlc3NlcyBpbiBnX3Zmc19k b25lIHNhZmUgYmVjYXVzZQ0KPj4gdGhlIGJ1ZiBpbnN0YW5jZSBpcyBhbHJlYWR5IGxvY2tl ZCBmcm9tIGEgZ2xvYmFsIHBlcnNwZWN0aXZlPw0KPj4gSGVuY2UsIG90aGVyIGNvZGUgcGF0 aHMgd291bGQgYmxvY2sgb24gQlVGX0xPQ0soKS4NCj4gZ2VvbSBjb21wbGV0aW9uIGNvZGUg aXMgdGhlIG9ubHkgY29kZSB0aGF0IGFsbG93ZWQgdG8gdG91Y2ggdGhlIGJ1ZmZlcg0KPiBh ZnRlciB0aGUgb3duZXJzaGlwIHdhcyByZWxpbmd1aXNoZWQuDQo+IA0KPiBJIGJlbGlldmUg SSBhbHJlYWR5IHRlbGwgdGhhdCB0byB5b3U6IGNvbnNpZGVyIHRoZSBidWZmZXIgbG9jayBh ZnRlcg0KPiBMS19LRVJOUFJPQyBhcyBhIHNlbWFwaG9yZSBhbmQgbm90IGxvY2suDQpZZWFo LCB5b3UgYWxyZWFkeSBkaWQuIEkgdW5kZXJzdGFuZCBpdC4NCldoZW4gc3luY2hyb25vdXMg SU8gaXMgcGVyZm9ybWVkLCB0aGUgTEtfS0VSTlBST0MgdGhpbmcgaXNuJ3QgdXNlZC4gVGhl IA0KbG9jayBpcyBzdGlsbCBvd25lZCBieSB0aGUgY29udGV4dCB0aGF0IHRyaWdnZXJlZCB0 aGUgSU8gb3BlcmF0aW9uLg0KQW0gSSByaWdodCB0aGF0IGV2ZW4gaW4gdGhpcyBzaXR1YXRp b24gdGhlIGFjY2Vzc2VzIGZyb20gZ192ZnNfZG9uZSBhcmUgDQpwZXJmb3JtZWQ/DQpDYW4g dGhvc2UgYWNjZXNzZXMgYmUgY29uc2lkZXJlZCBhcyB2YWxpZCBleGNlcHRpb25zIG9mIHRo ZSBvdmVyYWxsIA0KbG9ja2luZyBydWxlICd1c2UgYl9sb2NrJyBzaW5jZSB0aGUgYnVmIGlz IGxvY2tlZD8NCg0KLSBBbGV4DQoNCi0tIA0KVGVjaG5pc2NoZSBVbml2ZXJzaXTDpHQgRG9y dG11bmQNCkNvbXB1dGVyIFNjaWVuY2UgWElJIC0gU3lzdGVtIFNvZnR3YXJlIEdyb3VwDQpB bGV4YW5kZXIgTG9jaG1hbm4gICAgICAgICAgICAgICAgUEdQIGtleTogMHhCQzNFRjZGRA0K T3R0by1IYWhuLVN0ci4gMTYgICAgICAgICAgICAgICAgIHBob25lOiAgKzQ5LjIzMS43NTU2 MTQxDQpELTQ0MjI3IERvcnRtdW5kICAgICAgICAgICAgICAgICAgZmF4OiAgICArNDkuMjMx Ljc1NTYxMTYNCmh0dHBzOi8vc3lzLmNzLnR1LWRvcnRtdW5kLmRlL2FsDQo= --------------jRydQZMlaYDmZwf5fxyKbzDW-- --------------1K0yL62K0inSR0ruxTeZisgi Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEElhZsUHzVP0dbkjCRWT7tBbw+9v0FAmP8bBgFAwAAAAAACgkQWT7tBbw+9v0P Sw//eXGNS+FERyB9YdEUMSguHVvtMqlMo4l7QRionJuz/6S+H8aQ6UNYya3ebG0gcK0MJ2NNB72T 1NomYUvo29D372Dt+p9F+TaRBzBVb7LZtSFZhHsszMRuRxSp3kIRIkKO1EFLy2/PbXFw/+zxRo5x i3nh+Y3X78Il44xXPzXy6/mjK7xM3Xh/BtPs6NtUyHqLC6HPBQIAHq1P7WW10+IhDV9YrzHrTpH5 4p5uH9cnW/fifSjd7AYllTivaA5dyOdfvHa7a4XO446lawctzYIcUw4lHC+y7gJwC6F/NN3ncBaP OKAYC5NQ6uTbri6X/7XbCDYvRjYv/CNOzD5py8ZoVfDnAG+MEWNFE1WhfuPxtYnVyhddxIeV31pA 5bnKaox34yjGUvDbQ30aQsHfIk88KWLMxdYmamOXP/SbuQ57/+Mogt6QcrGJhSRQMmwTV4riGPNH cN8bqP6thx0M8V69ME1T7qPd6i45WNzRENViNRqgY80lRA/8u36k9bAtRL3qhQCEfhsAeko1Hxwy l6RgZ2Y3POyI5pDR3NJH3VILHO9RlmyjvlOymvNePsoktA9YtvzWcgvj24W/oSpRHujSMlUzkpuu 34NCelS7YUDm2jthebxM5tj3zCyETslsFWqKSG0HRcvmIX9uH2qaGX7Ug0XGNEXoXqCpeAqhGOSG yGM= =W8cR -----END PGP SIGNATURE----- --------------1K0yL62K0inSR0ruxTeZisgi-- From nobody Mon Feb 27 14:23:47 2023 X-Original-To: freebsd-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 4PQN6F014Zz3v9SS for ; Mon, 27 Feb 2023 14:24:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4PQN6445Ygz3GMG for ; Mon, 27 Feb 2023 14:23:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.17.1/8.17.1) with ESMTPS id 31RENmKU050915 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 27 Feb 2023 16:23:51 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 31RENmKU050915 Received: (from kostik@localhost) by tom.home (8.17.1/8.17.1/Submit) id 31RENlP4050914; Mon, 27 Feb 2023 16:23:47 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 27 Feb 2023 16:23:47 +0200 From: Konstantin Belousov To: Alexander Lochmann Cc: freebsd-fs@freebsd.org Subject: Re: Understanding locking for buf Message-ID: References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on tom.home X-Rspamd-Queue-Id: 4PQN6445Ygz3GMG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 09:38:47AM +0100, Alexander Lochmann wrote: > On 24.02.23 21:41, Konstantin Belousov wrote: > > > Viewing it from a different angle: Are accesses in g_vfs_done safe because > > > the buf instance is already locked from a global perspective? > > > Hence, other code paths would block on BUF_LOCK(). > > geom completion code is the only code that allowed to touch the buffer > > after the ownership was relinguished. > > > > I believe I already tell that to you: consider the buffer lock after > > LK_KERNPROC as a semaphore and not lock. > Yeah, you already did. I understand it. > When synchronous IO is performed, the LK_KERNPROC thing isn't used. The lock > is still owned by the context that triggered the IO operation. Not quite. Sync io (bread()) means that caller performs bufwait() on the buffer. It is still subject to the LK_KERNPROC ownership move. > Am I right that even in this situation the accesses from g_vfs_done are > performed? I hope that the previous note answers this. > Can those accesses be considered as valid exceptions of the overall locking > rule 'use b_lock' since the buf is locked? I am not sure what would be 'valid exceptions'. I explained the locking scheme used. From nobody Mon Feb 27 15:04:30 2023 X-Original-To: freebsd-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 4PQP0x6rfbz3vDcX for ; Mon, 27 Feb 2023 15:04:33 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Received: from unimail.uni-dortmund.de (mx1.hrz.uni-dortmund.de [129.217.128.51]) (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 (2048 bits) client-digest SHA256) (Client CN "unimail.tu-dortmund.de", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PQP0x2Ghvz3LyJ for ; Mon, 27 Feb 2023 15:04:33 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Authentication-Results: mx1.freebsd.org; none Received: from [192.168.111.37] (i5C750090.versanet.de [92.117.0.144]) (authenticated bits=0) by unimail.uni-dortmund.de (8.17.1.9/8.17.1) with ESMTPSA id 31RF4UCg002277 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT); Mon, 27 Feb 2023 16:04:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tu-dortmund.de; s=unimail; t=1677510271; bh=oSfAYsaE5CVL0eOG79gYyczYCwkCuuv1QJinYY1w4Ck=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=TJgRj/qb9QjibniiM5AOLwGhHdKV67+dZBO1ondPvjKuLC4QXMOsjtX0rdbr6f8fc bSkouNGCeGRHr419hSHIzZ5ctWNGVPkzWZ2N1Y1aUBRbskbp+FOFFpQbzLslTQXz6t RsdU7mGCgfXz/dYpSzu9rEpM5CcrzPIXFnePyyjo= Message-ID: <8e9ac2ec-6387-27b0-5cdc-1d61dbe2c831@tu-dortmund.de> Date: Mon, 27 Feb 2023 16:04:30 +0100 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 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Subject: Re: Understanding locking for buf Content-Language: de-DE-1901, en-US To: Konstantin Belousov Cc: freebsd-fs@freebsd.org References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> From: Alexander Lochmann In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------XYy61O4JgH6UBARGPxntVfyw" X-Rspamd-Queue-Id: 4PQP0x2Ghvz3LyJ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:680, ipnet:129.217.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------XYy61O4JgH6UBARGPxntVfyw Content-Type: multipart/mixed; boundary="------------3WnV8a6eNTitMytHJ5lhGVIo"; protected-headers="v1" From: Alexander Lochmann To: Konstantin Belousov Cc: freebsd-fs@freebsd.org Message-ID: <8e9ac2ec-6387-27b0-5cdc-1d61dbe2c831@tu-dortmund.de> Subject: Re: Understanding locking for buf References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> In-Reply-To: --------------3WnV8a6eNTitMytHJ5lhGVIo Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 DQoNCk9uIDI3LjAyLjIzIDE1OjIzLCBLb25zdGFudGluIEJlbG91c292IHdyb3RlOg0KPiBO b3QgcXVpdGUuICBTeW5jIGlvIChicmVhZCgpKSBtZWFucyB0aGF0IGNhbGxlciBwZXJmb3Jt cyBidWZ3YWl0KCkgb24gdGhlDQo+IGJ1ZmZlci4gIEl0IGlzIHN0aWxsIHN1YmplY3QgdG8g dGhlIExLX0tFUk5QUk9DIG93bmVyc2hpcCBtb3ZlLg0KRWhtLiBIYXMgdGhpcyBiZWhhdmlv ciBjaGFuZ2VkIHJlY2VudGx5Pw0KT3VyIGtlcm5lbCB2ZXJzaW9uIHVzZXMgTEtfS0VSTlBS T0MgdG8gZGlzdGluZ3Vpc2ggYmV0d2VlbiBzeW5jIGFuZCANCmFzeW5jIElPLiBIb3cgd291 bGQgdGhhdCBiZSBwb3NzaWJsZSBpZiBvd25lcnNoaXB0IGNoYW5nZXMgaW4gZWl0aGVyIGNh c2U/DQpodHRwczovL2lyaXMuY3MudHUtZG9ydG11bmQuZGUvZnJlZWJzZC1sb2NrZG9jL2xh dGVzdC9zb3VyY2Uvc3lzL2dlb20vZ2VvbV92ZnMuYyNMMTI3DQo+IA0KPj4gQW0gSSByaWdo dCB0aGF0IGV2ZW4gaW4gdGhpcyBzaXR1YXRpb24gdGhlIGFjY2Vzc2VzIGZyb20gZ192ZnNf ZG9uZSBhcmUNCj4+IHBlcmZvcm1lZD8NCj4gSSBob3BlIHRoYXQgdGhlIHByZXZpb3VzIG5v dGUgYW5zd2VycyB0aGlzLg0KPiANCj4+IENhbiB0aG9zZSBhY2Nlc3NlcyBiZSBjb25zaWRl cmVkIGFzIHZhbGlkIGV4Y2VwdGlvbnMgb2YgdGhlIG92ZXJhbGwgbG9ja2luZw0KPj4gcnVs ZSAndXNlIGJfbG9jaycgc2luY2UgdGhlIGJ1ZiBpcyBsb2NrZWQ/DQo+IEkgYW0gbm90IHN1 cmUgd2hhdCB3b3VsZCBiZSAndmFsaWQgZXhjZXB0aW9ucycuICBJIGV4cGxhaW5lZCB0aGUg bG9ja2luZyBzY2hlbWUNCj4gdXNlZC4NCg0KLSBBbGV4DQoNCi0tIA0KVGVjaG5pc2NoZSBV bml2ZXJzaXTDpHQgRG9ydG11bmQNCkNvbXB1dGVyIFNjaWVuY2UgWElJIC0gU3lzdGVtIFNv ZnR3YXJlIEdyb3VwDQpBbGV4YW5kZXIgTG9jaG1hbm4gICAgICAgICAgICAgICAgUEdQIGtl eTogMHhCQzNFRjZGRA0KT3R0by1IYWhuLVN0ci4gMTYgICAgICAgICAgICAgICAgIHBob25l OiAgKzQ5LjIzMS43NTU2MTQxDQpELTQ0MjI3IERvcnRtdW5kICAgICAgICAgICAgICAgICAg ZmF4OiAgICArNDkuMjMxLjc1NTYxMTYNCmh0dHBzOi8vc3lzLmNzLnR1LWRvcnRtdW5kLmRl L2FsDQo= --------------3WnV8a6eNTitMytHJ5lhGVIo-- --------------XYy61O4JgH6UBARGPxntVfyw Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEElhZsUHzVP0dbkjCRWT7tBbw+9v0FAmP8xn4FAwAAAAAACgkQWT7tBbw+9v0e nxAAzCgLV6cKDhVWNXzDdi8jRr9gnaCalByXeuvKls0KTJvtrYPktlF62V2AUsLOygf5wodW5vub KgRb2xtv3jmTZtPfKM0Pxf2PH/fvtjDbIvrXP+9czLxoay/TE2zksXaMGUDgA/igdd/HaJBwuegO JABzMwuzjyGT9VwiQyr0rMPUvGfI/8uP0hArcVqW8jlSarlOFOUxUlzklgr+t/esdfvHIO+vtxbP ey3KkmQ+D6rsueyehQxGJdN0+4zsl8CVK/BvRpqxNbUAmDJShFH1UJKCvPqInUrJDrkBZIRMg/PU oep2Wv0NFEa0lo7qUPfrRGJuabASLMzmdSSnvlsaNPwcePRFe+J6gdm+4EhoSeev4ym5WTomA6BU ayREcBAvJGA/TIjtIx2QatZ9LB8BG3iRZiks3bZq2+qR3pQ5Fpq3VUbuMmtqJVMSsOJlq6hUPcWW bX34sdMKzFAUGwBlHVkgSZkc1gjw5iJ+umegiGzhtpQZLPgCruPKYyRks+lwZ7Nz4GNyhVqUMog5 QJ6PNt0IRbAnhvUifDEuEY57L1xNwTD8ceFys1gpwIbZfZPSZ8mXu/YdbxyC2EuA3GFAMziaUHWx D4Trg6DX6lZ9a2k+EMewAeYxTR34waJLkeS/IKxMcGVsnTb4iITRte09WovMgSnO4XNof/nGXhL8 8z0= =rjhn -----END PGP SIGNATURE----- --------------XYy61O4JgH6UBARGPxntVfyw-- From nobody Mon Feb 27 17:57:55 2023 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 4PQSs06KHDz3vQKV for ; Mon, 27 Feb 2023 17:57:56 +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 4PQSs05Hbqz3twr for ; Mon, 27 Feb 2023 17:57:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677520676; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HZKDZDK0ykcIrJA6RKOwPB2SCrKdQ0v8bXmNXSFIsWY=; b=ks8pP7cPbYPUPnJzuHivqO25dSvvIzbgEgRv+l4nhvdM0EmPF0uDVCMcuTDByFWRY/admg 2J+Ae4blQfyCwhzDp0vIOWCCGtmWX+UbsfSVRQv+XUNQn36nQ5+mj9lrV89wTAKfcVmwcJ 4AVbYb3d1XL4/bvWpgQW0ciw41kRdVLLFbk3myC9Lo64qkEKuh1t4WttYDeD3S6Y3Me+bw YkNPCVDs7URPFBFivGe1ZVl8lM2oGJfpSTpA7//qh7NMuW7AFBLcbU97f2sZamxq9VKuN+ A71MtTx7fWnkwgZHmLc4MefYWzxYxZqhbdAqJbgkMupNf7XNNpg+hpoNOEtlTA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677520676; a=rsa-sha256; cv=none; b=mxt8twZIcaoWOsefUyVby2RglSCRHSnsdh/PE6BrklvJO0dmbv60Y71BQa/0bbT9iZNdF6 ouVDRYgA47rR7pdvr/6YheE34EbKgyceu579WCOpREJEggfrHtA4l7Md6ZtA4qzExphEbd TE1Rta2UUSjN04S3QyYboYTCQAiE5NJOLGVbClOS7axXHRkm37+fTCMBYmOvNMPvAQgsii HHkY+Ug+nDougygwdk9kxGqqEeNLloPYgj77Z0zEqY2FVKsuHsthjt3Qon7LjU3MHdNqtV 09L486ql4KRQC4vDgvLW3o2WWq/9S36cw5qIf8KXqiVLAdF5colHL1UQ/N42ag== 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 4PQSs04M5vzbJD for ; Mon, 27 Feb 2023 17:57:56 +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 31RHvuNC010174 for ; Mon, 27 Feb 2023 17:57:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RHvuou010173 for fs@FreeBSD.org; Mon, 27 Feb 2023 17:57:56 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Mon, 27 Feb 2023 17:57:55 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: george@m5p.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #85 from George Mitchell --- I have a new crash, but I did not get a dump because of an issue I will exp= lain below. For those who came in late, here's a summary of my system. dmesg says I have:CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics (3493.71-MHz K8-c= lass CPU) Origin=3D"AuthenticAMD" Id=3D0x810f10 Family=3D0x17 Model=3D0x11 Step= ping=3D0 =20 Features=3D0x178bfbff =20 Features2=3D0x7ed8320b AMD Features=3D0x2e500800 AMD Features2=3D0x35c233ff Structured Extended Features=3D0x209c01a9 XSAVE Features=3D0xf AMD Extended Feature Extensions ID EBX=3D0x1007 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=3D32768 TSC: P-state invariant, performance statistics My motherboard is a Gigabyte B450M D53H. BIOS is American Megatrends version F4, dated 1/25/2019. pciconf -lv says: vgapci0@pci0:6:0:0: class=3D0x030000 rev=3D0xc8 hdr=3D0x00 vendor=3D0x1= 002 device=3D0x15dd subvendor=3D0x1458 subdevice=3D0xd000 vendor =3D 'Advanced Micro Devices, Inc. [AMD/ATI]' device =3D 'Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Se= ries]' class =3D display subclass =3D VGA Until recently, when I was running FBSD 12-RELEASE, my box had one hard dri= ve.=20 I added a new drive when I upgraded to FBSD 13-RELEASE so I would still have FBSD 12 as an emergency backup. Part of the upgrade is that on the new dis= k I created a small UFS slice for /, /var, and /tmp, and most of the rest of the disk is a ZFS slice for /usr (so I wouldn't have to wait for fsck on reboot after crashes). That means that it isn't practical to do a test without ZF= S on that new disk (I'll call it my regular disk now). So I installed FBSD 13 (= same version as my regular disk) on the old disk (I'll call it the test disk now= ), which had (and still has) a small UFS slice for /, /var, and /tmp and a big= UFS slice for /usr. To boot from the test disk, I use the BIOS boot menu, since (unsurprisingly= ) I have set the default boot disk to my regular disk. I removed all mentions of ZFS and VBOX from /boot/loader.conf and /etc/rc.c= onf on the test disk. Then I booted up a whole bunch of times. On the thirtee= nth try, I got the crash. Unfortunately, I don't have a crash summary from it because the system rebooted from my regular disk instead of the test disk w= hile I was still staring at the crash message on the screen. Subsequently, I bo= oted 20 more times from the test disk without getting the crash again. What I saw (for a few seconds) on the screen from the one crash sure looked like the same old backtrace, and I have to say, to an ignorant yokel like myself, it seemed to be saying that there's a locking problem in amdgpu. T= here was absolutely no virtual terminal switching, because I had not started an X server and I did not type ALT+Fn. I'll try getting a proper crash dump later (possibly tomorrow). My thanks = to all of you for your patience. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From nobody Mon Feb 27 18:05:43 2023 X-Original-To: freebsd-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 4PQT245qv3z3vQjr for ; Mon, 27 Feb 2023 18:05:48 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4PQT234Df4z3vMs for ; Mon, 27 Feb 2023 18:05:47 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=ZF5U4xOp; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="e VKDqOL"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.26 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 936A85C0184 for ; Mon, 27 Feb 2023 13:05:46 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 27 Feb 2023 13:05:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to; s=fm1; t= 1677521146; x=1677607546; bh=xQUhSLv0T4StWftU7qysFWLco5usYikIsQe yr54Wlf0=; b=ZF5U4xOpC8n8Uy1SdxZ8F940086c7RKdUazcFybOLCxKea4/fMn sE+W5BJHpTbGiSMHnZmihr6y0FhacNwVwCiHS6vxNLU24GiVxk5qYH9vGVQj15DV ZkuPhux6jmgKkhoyeFBgXcCF/PDUPKzdl6u2XlCnEBpHgiFjEgdV1peGxpusR7fF CfG43RlVzZcWymLP0lcg1DBymkxk1Gds8RwncNaLCJ0krTyHkwP/RecP/+Kenhua zcEbVYO5v+mtjSAGv4I/kvOcL8O9v2mkLB4dIwRsbWWxdQNVg5yKleyh7T47qOAG ZSwbQrpTm2NyyjjZ0mcpH+UmMrkLSJtYuDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1677521146; x= 1677607546; bh=xQUhSLv0T4StWftU7qysFWLco5usYikIsQeyr54Wlf0=; b=e VKDqOLYXZuZPI9X/aZ03D9bywvHEep9Yvs1pIkqy6BE6un2wNltYFBdtap/cMq3f lnr3YMT2/v0GpK6ToSyK3jeEEUKG+cr9i1XtixmWbiObkF3wSs9cx5WHk0lF1nPK fzGeONP8Ij9ys+PbTbHiWYBtL27jZ1IrHtcILHDBkGpWxgl0ANdQjv5u9TLd9Uao ngYk0wibYoeeTYKDTSM0I0XZW/Mov7vif4V4SVJE3T0VL2AZEJzjKvHpKf0P4BVT 9uf3rD4f9Oxc3ClXhXslgOqnSfFXscXfbhRy3yDB0AKCUOOOSIPL+fTMJlGAsdu1 Tup5IDVSM8xmc1lbTrmCQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeltddguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehttdertd dttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrght thgvrhhnpeevudffiedvffffgffhgeefjeefffdtieetheetkeefhfdvfefgtedtueehge ffueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehv ohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 27 Feb 2023 13:05:45 -0500 (EST) Date: Mon, 27 Feb 2023 18:05:43 +0000 From: void To: freebsd-fs@freebsd.org Subject: can another disk be added to a zfs stripe Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-4.70 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.26:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.26:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PQT234Df4z3vMs X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N Hello fs@ On a 13-stable host I have a 13-stable bhyve guest. The vdisk is a 64GB zvol. In the guest, the filesystem is also zfs. I'd like to add another 64GB zvol to this zfs, and for the resulting zfs system (zroot) to remain a stripe. Is it simply a case of, within the guest (after booting the guest with an additional -d pointing to the unused-at-that-point zvol) and running 'zpool add zroot vtblk1' ? It's important the zpool remains a stripe not a mirror. Or is there a better way of doing this? tia, -- From nobody Mon Feb 27 19:22:35 2023 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 4PQVkh1NZJz3vVt6 for ; Mon, 27 Feb 2023 19:22:36 +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 4PQVkg4FTtz47WK for ; Mon, 27 Feb 2023 19:22:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677525755; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=aNLmhUjeX+gd/+yYDGTE56UJFr5k1PbB0mv9vK1SfN8=; b=gch4eKr6/a+zlxcWU02dJM0t0cq+/SQjhfvCtGlF5wnti0PjYECLPYVYlrNOxbPZ/GPZHt bj+srzL9TXLIUkdJeknCw91VgRb2bCt9QIvjdN9U2Cy/uQhsEZN681ytP0rIO9sxylw3qv oP9hw5IhiR5Zt7l/BuWCI9+ieh0AzVFgUeMEBAr/yVRdbnynFxFOQD8jQqliBTIMSz+k+I 3uLcuQLJtWmelz7Qq8TajHzgDS8K0EKC32Spga479A6idXeACk2GZi+E3D7Urjcp+8zMDW RCA9+NTX7G6b50Q/RGkvCbDVSXgkfXcsMoWql/+MEpKWXebgRFzGEdkyQmxvyg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677525755; a=rsa-sha256; cv=none; b=ZNA44KJryC/zldTvhBMpJ8SxYM/4e58+PNMnkyB+3oAWJtOKM+8hizVAt4wPO+xbWIm8hP da00ngeQkqiCUOxmz7AfHf/3kSJWVmtHJl4xvWjVNDC1j5Uw3MBrtm5uGT4K2T1KBHtxI6 QQv4RAYFyr9gu6zD6AFrhPsG0MLK/dh87ZyuyPT3BlENwoCvBGBxdSBILs8dkuCCiEErdV VZbxdtRl5inH61GX6XMH1sHmyfanss47O90+bck70ZoZ8x48RX4d45JJaiBsW43vUhOVAO coGopb7mPi93yfg6sBdJn4W388c4kAt3gJ4GoUz9+3KVRt8SMnVlZw6brdmg2Q== 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 4PQVkg3JplzdSK for ; Mon, 27 Feb 2023 19:22:35 +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 31RJMZ2a046605 for ; Mon, 27 Feb 2023 19:22:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RJMZDu046604 for fs@FreeBSD.org; Mon, 27 Feb 2023 19:22:35 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 267628] growfs deadlocks if output is redirected to the filesystem being grown Date: Mon, 27 Feb 2023 19:22:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status 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=3D267628 Konstantin Belousov changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Mon Feb 27 20:02:46 2023 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 4PQWd33TWBz3vYJM for ; Mon, 27 Feb 2023 20:02:47 +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 4PQWd31NTsz4GcZ for ; Mon, 27 Feb 2023 20:02:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677528167; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rESW55LG/UPTl6FFvX6/vhh9qpEZnUE1nVomY8PpvlM=; b=yrHr9XCzpSA3sZDIxJuJaNmVLaA0LeVufSJQ0y0W2CFtbOrGPpV8rDGELH/IqeO2r6CNfE pO7Z9/p5QN0JkZiernv5RVOG97v2SY0A5ECXnfT2guzFYO0f46pBuZueWLsgm/plfKBKRY xJpQco1q/rmckbP7Rb7AIOXJUGFn40QvVf00S+oAz6qlP/My97ySnkbPPhiHfudPJlEQgz X5h8Wxc16ze/XpgGPzuq92yX5srIEIHs7FF/3fzxDMWtuS2hJMhsE6o0zZFqMVvcL3/0kG j/3yfAgXktdJ+H1C1qyBe6QMHhfrmP+YfMYVBgTB7lD9vgJKYqZ2Pm4HLmMAvw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677528167; a=rsa-sha256; cv=none; b=CHroxskw9qs4JwT2Ki8WrVQueh4iyNgCrxX3OrVsJ1odImstJITTxewy6BEPwedO8lAw0l 0Yk9XspIuiV3P0CmnSpadntSUZJv67o2F/ECvFfmsbisgrY9s5D5IQ913cDMj7rWzSQu+1 WnCBKsmOtPrzjIfRDCpNF3Q25B/j30r7Y1kmNl8KYnmXIKbRW4GES4EWCaZcRpaysO+jRC BBFLNFg5kzHmACDln8+oYvsn2FOLDKImMhfyO4uWspOd7Wla+tGT0R2Ulc5NAqCWln9r97 WvuNiCOW3dmrRM9NaYrcxfdJ04Ep5lmBG+EYNo07NSZjkUfbyQNKcuIyicUitQ== 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 4PQWd30RwBzfQg for ; Mon, 27 Feb 2023 20:02:47 +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 31RK2la1003024 for ; Mon, 27 Feb 2023 20:02:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RK2loP003023 for fs@FreeBSD.org; Mon, 27 Feb 2023 20:02:47 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Mon, 27 Feb 2023 20:02:46 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #86 from Mark Millard --- (In reply to George Mitchell from comment #85) Where does dumpdev point for "test disk"? Someplace also on the "test disk" that a "regular disk" boot would not change? If yes, the first boot of the "test disk" after the crash should have picked up the dump information, even if the "regular disk" was booted between times. But if the dumpdev place is common to both types of boot, then the regular disk boot would have processed the dump. likely using a different /var/crash/ place to store things. Another question would be if there is sufficient room for /var/crash/ to contain the saved vmcore.* and related files. Yet another question is if the test disk has /usr/local/bin/gdb installed vs. not. ( When present, /usr/local/bin/gdb is used to provides one of the forms of backtrace, the one with source file references and line numbers and such. Much nicer to deal with.) If a vmcore.* was saved but some related information was not for some reason, it should be possible to have the related information produced based on the vmcore.* file. Side note: In case it is relevant, I'll note that defining dumpdev in /boot/loader.conf in a form the kernel chan handle, instead of in /etc/rc.conf , can be used to allow the system to produce dumps for earlier crashes. (But I'm guessing the crash was not that earliy to need such.) --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From nobody Mon Feb 27 20:13:35 2023 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 4PQWsX2wxLz3t595 for ; Mon, 27 Feb 2023 20:13:36 +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 4PQWsX1w5Rz4HmZ for ; Mon, 27 Feb 2023 20:13:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677528816; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xA5LCcjT/JGLPfpu4wphlHSoxQtlwDLsY/XtAsFNahg=; b=qA54eovrmHsMapmhyimFoR62cyRw8DGYduYCvTpxwHQzKGJzZswIdyZz6ksh+IfkPl/65N 9CBh8JYiFGHaJuvZ7sZH6ErNS/Z7U2Knp3HhMsRvIveRbKuBojU6FiTTCULfNR1JJcJzT5 1nFtq9PiZUqNp+AtKbgfbEHDGRe+9X9dK6QbseaPsq+zv5Uh0L+2h+VAlvNCr0gVvPUxAR LYgPMpgAVwXZzDylEIlwmYhU/1HNzU/FFsVVRJ+8XF5M1KYfaJaduxEngWXsfqPzV0bsjP Xf6DbkyxZ2WyDlCQK+MkUloTgYWGZ/oCV8grqDZJKWEXxCJ6AQkOyTTq8q+c1w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677528816; a=rsa-sha256; cv=none; b=aAaccIzmG6+t7tCVC3e19qupmnMUv6ULzC6EfEy8oBi5sQ4LfD3rhwa8QjyrLWpRjwucRv Te3RdSEE2G7+0wmDgtrwQli0vnZM1xN1MXb3nqBko8B2ixiplSwEL3bRMhq178MiLnDcvm DOnYy2nyPLzTit3CbY94TKUwb+qR0HS79dvbkDMvXxLAr3d8K8aIR3lu9gxK3gBV6qaiE5 8xuZ+d9mIZ5BVasN0VpRCIRqgIkKpga/9Y29ecp9zIVATUfdxZ4z1GoA5hsduqt4PqXPa4 RDjZFmYgFYtfz1LEsl0mJFODHKnr+LGRwSnarilUV8Vdyb6piwxrfRZ2g1S+tg== 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 4PQWsX109JzfGK for ; Mon, 27 Feb 2023 20:13:36 +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 31RKDa8D021731 for ; Mon, 27 Feb 2023 20:13:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RKDaTv021730 for fs@FreeBSD.org; Mon, 27 Feb 2023 20:13:36 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Mon, 27 Feb 2023 20:13:35 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #87 from Mark Millard --- (In reply to George Mitchell from comment #85) For booting the test disk, getting the kldstat output from a successful boot might prove useful reference material at some point: it should show what to expect to be loaded by the kernel and in what order. Since you got a crash before starting the X server and had not used ALT+Fn, that would be appropriate context for the kldstat relative to the known UFS-only crash. Other time frames for kldstat may be relevant at some point. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From nobody Mon Feb 27 20:50:05 2023 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 4PQXgf2H5Vz3t6sb for ; Mon, 27 Feb 2023 20:50:06 +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 4PQXgf1FKvz4PkF for ; Mon, 27 Feb 2023 20:50:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677531006; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fRIO85Q2jwJHwhy+plORmx/wgJoMlaZuNWd6yYHKk2w=; b=uPOzHb5xCs94nc+IKeey38dVP4mPGeX1nbNqVnB88UMmgQ3RgsBDnMvuuva/sZACi1eeQ3 mRHUMzus36U6O8jFd1+QQ5M4tOqsIgqalIyvEJM+Hei23G0cVpj7hKq+QahwkibYOdS30R Cu9SlEXvB2pXHBdLpvPCL4qS7AmsCL2oCisz6knl25PdNTk0mTExLXcSYrzDOzTRjtfZ10 ly8IZaYDrIFwznX+Tqa0DYWa0gdWKGCnGt+B8YidWn5co9utFKSMPYsZXyxGTzu7ZX2iPp iIjdv2M4ww3jsN8lzKXOAdLJQERpnYOmkNxt9ZrBL3o+8lc9LZD5lT6oBVVWBQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677531006; a=rsa-sha256; cv=none; b=OGErwPXCpBCCv3zOdNthrRAFyvDsAC7A+gxW4sbcmMktDIgrt2nMzN+UAP0qitqHIdTf4L O2fOzwdCKvRPOfYI1XYSt8qFSBkNCaB6nSA8QycwAOKl0VyrsqnZqRdg0Xg70dAhmF3Xxn 8q76739gbVIs2v9hIBhmvr+Jyq3gGeB1wtnMeL1YaWDsW68Gft2gFo//8SaDYJJdRVED3S VuenZUkEFCgKes/ghEpfcCXXcdlHUfc3FlDJkz47fJkZjcDTHy32nBITDJoXZe99v2fXSE 1cnR9oe6I2U+Ti8ESNFEJxNwL6H2B9lmZYzEJeUBo3XFm3wuOMogXO/vjwhXow== 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 4PQXgf0Mc4zgSh for ; Mon, 27 Feb 2023 20:50:06 +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 31RKo5A4067684 for ; Mon, 27 Feb 2023 20:50:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RKo5wA067683 for fs@FreeBSD.org; Mon, 27 Feb 2023 20:50:05 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Mon, 27 Feb 2023 20:50:05 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #88 from Mark Millard --- I booted a ThreadRipper 1950X system via its UFS-only boot media alternative. The system is not set up for X. For example, no use/installation of amdgpu.ko for use with its video card. For reference: # kldstat Id Refs Address Size Name 1 58 0xffffffff80200000 295a5a0 kernel 2 1 0xffffffff83210000 3370 acpi_wmi.ko 3 1 0xffffffff83214000 3210 intpm.ko 4 1 0xffffffff83218000 2178 smbus.ko 5 1 0xffffffff8321b000 2220 cpuctl.ko 6 1 0xffffffff8321e000 3360 uhid.ko 7 1 0xffffffff83222000 4364 ums.ko 8 1 0xffffffff83227000 33a0 usbhid.ko 9 1 0xffffffff8322b000 32a8 hidbus.ko 10 1 0xffffffff8322f000 4d00 ng_ubt.ko 11 6 0xffffffff83234000 ab28 netgraph.ko 12 2 0xffffffff8323f000 a238 ng_hci.ko 13 4 0xffffffff8324a000 2668 ng_bluetooth.ko 14 1 0xffffffff8324d000 8380 uftdi.ko 15 1 0xffffffff83256000 4e48 ucom.ko 16 1 0xffffffff8325b000 3340 wmt.ko 17 1 0xffffffff8325f000 e250 ng_l2cap.ko 18 1 0xffffffff8326e000 1bf08 ng_btsocket.ko 19 1 0xffffffff8328a000 38b8 ng_socket.ko 20 1 0xffffffff8328e000 2a50 mac_ntpd.ko # uname -apKU FreeBSD amd64_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #61 main-n261026-d04c86717c8c-dirty: Sun Feb 19 15:03:52 PST 2023=20=20=20=20 root@amd64_ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.am= d64/sys/GENERIC-NODBG amd64 amd64 1400081 1400081 --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From nobody Mon Feb 27 22:11:21 2023 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 4PQZTP6f7dz3tDSd for ; Mon, 27 Feb 2023 22:11:21 +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 4PQZTP3mP8z3Pwn for ; Mon, 27 Feb 2023 22:11:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677535881; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2rboWMJVJSs2mTqp7gwIW3rK9Dx0OdSPipQh3nNSkOE=; b=OQutVWA2BU/w9XAEDENaYCUMdIPPQ4kQmFTaDWodPJUVRiwlphHhrUnOJPAkpf1Myb5PQ+ aiatpSrr9pZcHBM/22201nYn0uDiC0WWH8kVITDfgn5Ek7eLLj03sWwH5gB+qBYK5eamEj DcjXAigPrjtBewBYFG0jy0Odj0GdXFT2j3GM8QfpmWbZop9ZOkEOfBvzJcWe6nWB+rYDvT t/pUbRWWbTo6b05N2faHF2iAbonK3HuJqQrbmAnc44pF/RfmdK6EKEth6H+Crp6iZ9t1E+ OQTOeUvgeYp4QPmVzLgHQmxFwjPz9upOXxBRNRmVRhUAwKPT0KYBJPjOKXBEWQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677535881; a=rsa-sha256; cv=none; b=CnKs90lUEf30Uq/FGzsPVqULYzLqMKOYKWDErlQNy7zJm9RsmkG5dNciaeU5XTSQ9uO+GU oLuchGrDMv6xM+DFU1Q+OBAvQNWDwdbQLDqkRMBQeSLLKOniHvR6PtBqUIzgmtgQODkTVN uT9VFBrrAQU0rStT1hQmP/9AUJs2QlkL2uThhTx/Cq1d0LsD6vGskqBmaZUd2mL06YnfbZ KW0JmVDqGRAOtZdLZIrq3po0hN9q5ruLZzF016Tahq/7uQxIRr90eh45AdNB+sodT0Vame ylOFpY5KTT/+nfrq84pP0+f4cc14pT+IE/okOoT2rXtaseUo5SVzSef/VTAWTQ== 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 4PQZTP2r8kzhw6 for ; Mon, 27 Feb 2023 22:11:21 +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 31RMBLu8090340 for ; Mon, 27 Feb 2023 22:11:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RMBLWl090339 for fs@FreeBSD.org; Mon, 27 Feb 2023 22:11:21 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 106107] UFS: fsck_ffs: left-over fsck_snapshot after unfinished background fsck if filesystem clean Date: Mon, 27 Feb 2023 22:11:21 +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: 6.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc 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=3D106107 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #8 from Mark Millard --- (In reply to Kirk McKusick from comment #7) Mostly an FYI that there might still be an oddity possible. Context: # uname -apKU FreeBSD amd64_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #61 main-n261026-d04c86717c8c-dirty: Sun Feb 19 15:03:52 PST 2023=20=20=20=20 root@amd64_ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.am= d64/sys/GENERIC-NODBG amd64 amd64 1400081 1400081 I booted this system and the "df -m" listed 57% Capacity but my du -xsm /* listed more like a 3rd of the capacity (totals of the lines). The du result was more like expected. (Note: This system is normally booted and uses a distinct ZFS media, so today's activity was the first UFS media use in some days.) Turned out there was a /.snap/fsck_snapshot roughly matching the du -xsm /* total. "ls -Tld" indicated today's date on the /.snap/fsck_snapshot . I removed the file after a while (no evidence of it being in use noticed) and rebooted and it did not return. The removal resulted in "df -m" reporting 29% Capacity, both before and after the reboot, more like expected. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Mon Feb 27 22:45:24 2023 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 4PQbDh3H2Kz3tGTs for ; Mon, 27 Feb 2023 22:45: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 4PQbDh24Bcz3p9R for ; Mon, 27 Feb 2023 22:45:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677537924; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bYZ3FD+vJPjB0JCikNvaLmMz3rwvLorvrKsautfLDYc=; b=gVttJXS9Y/InL3+BY9CmdFsBHrNj8CA33SSlNrfvoGZlJm61mjKiuH54LrtHiFm8e2oQwX RB56+PFII+xOAl8OqNSqVVyargzlXw63e8UTUBQydQn86qOVsYMcmrwoURiWdqoQVnCsBn wcLcTMAVzAVG5gXZXAXSNqtzxrftD4mMHyC2di8mG/FVbF958DTPBT8brvHRGhUX6iV5Ck PVh9uAVUKo0MxL1WcLSHgGD0yyaYmkY8yJmiIQLRJ+2ocy2mw4ci8BvAQHUhoVg2ceEx8k ettwl/t3h+QxU/j5P0rBWx/nINWuoglNuCc2VJAuTQqJY9Sc1+xcMfvhXbvVNQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677537924; a=rsa-sha256; cv=none; b=ucAeOEPPuG4sbFJk3g9UFJKU6r3FaBlnp/K2Td+sYvuWoQY0iqE3UqPta1DHiSTCCJjiqO viM3JzMo08S4sQHIZBS//nQPPbJQsfUo6a1tBFMG/5rQdOYrABv8CpNlOc7UGBHvBZZRGG Gxv5GHkxaSZPeQIexZxIpTBSIMIlh/5oJQEDbhuVAJW4+WopO3zjDZBHUnHDAw2eI0BPAJ OFNN4v8ZdM96jR+QvXWmdJbl+Am5zwbMxrxZLj8yr0YReEm9A41HSwmbzJeGCTPr9FaDg0 jbymfm2ACbGJtrVx56LRP+VjBuWq8KpHjAm6q9UJFDXtn4XU5lzcXzLocYRoWg== 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 4PQbDh188czkMy for ; Mon, 27 Feb 2023 22:45: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 31RMjOEs040275 for ; Mon, 27 Feb 2023 22:45:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RMjOvQ040274 for fs@FreeBSD.org; Mon, 27 Feb 2023 22:45: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 106107] UFS: fsck_ffs: left-over fsck_snapshot after unfinished background fsck if filesystem clean Date: Mon, 27 Feb 2023 22:45: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: 6.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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=3D106107 --- Comment #9 from Kirk McKusick --- (In reply to Mark Millard from comment #8) Is this filesystem mounted and having background fsck run on it? Background fsck is the only application that would create .snap/fsck_snapshot. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Mon Feb 27 22:52:46 2023 X-Original-To: freebsd-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 4PQbPS2NZyz3tGXM for ; Mon, 27 Feb 2023 22:53:00 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f42.google.com (mail-vs1-f42.google.com [209.85.217.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PQbPR0y6Cz3rcL for ; Mon, 27 Feb 2023 22:52:59 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.217.42 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=none Received: by mail-vs1-f42.google.com with SMTP id o2so13838272vss.8 for ; Mon, 27 Feb 2023 14:52:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YI077fByBLsxmMh9PDwummKDKdoTfRA5S/djKFBRmvs=; b=NQH15ivDuehBgTnzb9F6y3SSrXvSj4MDjaJcgwgev11+OLb4N447nySfQsYXBuIYO8 vkL/n/z+9WP0tREIhgick02eC2HzDPZx5Bvd/L/mSfDNCVCcyuGW5vicE7U5GUyXETun f929ZKMtApWnSgCJHzloYo9zGehNk9aCvAgy3LhMQhSMTb3FYD9UyuBTle0hC7zTnQ/j H2Qg1oAD2FlCSRbrjsdI1HyBDz+YRRbg2cU44IB+As7W9LAombZ6SaF6vtsQWKOKcIlk fDTKgQvAaQP6L5zGQ9AiQ634U3c+8hPoEhEoh+pJfJNHBe8DVShDOxcygGNFJHw3Al4Y Lp3Q== X-Gm-Message-State: AO0yUKUj8ZMCvhCJmv/oO0vfDu8cf0128Nm+pAfzWUgxtR9VUdwzbol4 JD3YYsMTILkpp3dVIydgsIoaRI4dMnTVk91JqQjeUgaN X-Google-Smtp-Source: AK7set8y3/QX39RxAHLYhRYq1x2R9JgrJ+VBYXn6HNPSlXfU1ecrSiAGxoRlZHiEdJipkm/civHIS1NcgVKLiYzo6oE= X-Received: by 2002:a05:6122:18a4:b0:401:1c83:fba3 with SMTP id bi36-20020a05612218a400b004011c83fba3mr115049vkb.3.1677538377705; Mon, 27 Feb 2023 14:52:57 -0800 (PST) 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 References: In-Reply-To: From: Alan Somers Date: Mon, 27 Feb 2023 15:52:46 -0700 Message-ID: Subject: Re: can another disk be added to a zfs stripe To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_NA(0.00)[freebsd.org]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.42:from]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.42:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[asomers]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4PQbPR0y6Cz3rcL X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 11:05 AM void wrote: > > Hello fs@ > > On a 13-stable host I have a 13-stable bhyve guest. > The vdisk is a 64GB zvol. In the guest, the filesystem is > also zfs. I'd like to add another 64GB zvol to this zfs, and > for the resulting zfs system (zroot) to remain a stripe. > > Is it simply a case of, within the guest (after booting the > guest with an additional -d pointing to the unused-at-that-point > zvol) and running 'zpool add zroot vtblk1' ? > > It's important the zpool remains a stripe not a mirror. > > Or is there a better way of doing this? > > tia, > -- Yes, that should work. But why would you want to? If it's just a matter of adding space to the guest, you'd be better off simply enlarging the zvol. From nobody Mon Feb 27 23:11:11 2023 X-Original-To: freebsd-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 4PQbpX3rDDz3tJ3q for ; Mon, 27 Feb 2023 23:11:16 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4PQbpW2N5Rz3vpZ for ; Mon, 27 Feb 2023 23:11:15 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=bSEgbtmZ; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="A+wF/dKe"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.29 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2DF975C0113 for ; Mon, 27 Feb 2023 18:11:14 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 27 Feb 2023 18:11:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1677539474; x=1677625874; bh=bTDBKpsnAb 1XDsVda3PwJViQKYZ8mZMjXIfp4Nf/eI0=; b=bSEgbtmZRjC5lLuBNppYPrY9m5 GQhZo4groT7kVrGrHMjJd7xR8lh6aEfj7/EJ3PItKoztTvQ/c8xHZUyRXDNU8UYm n6pgr79xUotydtAAvs1VkOATkh55vuErFIHN7MvaZ5dheGMkIrLy0Vjjtv7Fw6hp 6/mihm2ERUaZ+oN2Zh4yelSMDcyfPHspExbd62ZwLDzGYghtKHOOOqu1NvGefH9j xQjdhrNyuZDfKt7IotcK8AzIsoS75h8wfS0mNcpQ2qq9cmJ4cWGwwUSdr9ARCE/W RTm2bdqzyeIIIX5qZgIPznRX0Uuu7eqfc9Cs/C/R7nSEqD8M4PyzT0C5jG0w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1677539474; x=1677625874; bh=bTDBKpsnAb1XDsVda3PwJViQKYZ8 mZMjXIfp4Nf/eI0=; b=A+wF/dKeFKlstXDtwEVKRjjZKQlYzg7XBlzqZGjuZqEb pM4ibyItQ1yFeVwOa8wXi7JnTWF7Fzp1bHh+7zyJXeYXa7DhWnB/jMnF4K0BABXL +iasGFax9WyRZTbq9ApphOODRHOS/DUXnWyk/hU8owOMWPJm7i7KiaNSP1Dk39vf 1Tx3NZcWKSS0Np8UMnuT3aASFFkNO87fx2dHYikJ0SqMXHzhmqE6ulh3gplyuxlJ NEdeeq5IWHXjXEWPFHHRgKiO5sGl9x2UcXbVJuKS7LMwv++xflJyyreT8+6VqXqq hklbP+QJFyi1VCaBG1wLbWs/B6ACXn5W+IHCyxt3FQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeluddgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 27 Feb 2023 18:11:13 -0500 (EST) Date: Mon, 27 Feb 2023 23:11:11 +0000 From: void To: freebsd-fs@freebsd.org Subject: Re: can another disk be added to a zfs stripe Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org References: 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-4.57 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.972]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PQbpW2N5Rz3vpZ X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 03:52:46PM -0700, Alan Somers wrote: >Yes, that should work. But why would you want to? If it's just a >matter of adding space to the guest, you'd be better off simply >enlarging the zvol. I wondered about that. But how would the guest handle it? Would I not have to tell the zfs guest that there's more space, or is it automatic? -- From nobody Mon Feb 27 23:27:40 2023 X-Original-To: freebsd-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 4PQc9k3V48z3tK5w for ; Mon, 27 Feb 2023 23:27:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f44.google.com (mail-vs1-f44.google.com [209.85.217.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PQc9j38D8z3wdB for ; Mon, 27 Feb 2023 23:27:53 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.217.44 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=none Received: by mail-vs1-f44.google.com with SMTP id d7so14047643vsj.2 for ; Mon, 27 Feb 2023 15:27:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=trobtplCUCgSKaDxL8oB/+7wLOiBLA/qXp1xPK/VbYg=; b=CFlci+/iLoQ6Cal5jXSCZAqk9Xd1Iz+y4bzHD9vu18VihKDEomn1a7uueMc0i11jYN lI6DwGYwAkFnI2NVI9YKBdvXOcIggXpHXVvw4vmb4d2GqiG1GQuqQ2HWEl4imBOKG2O4 Uiirxx1p/QV1IQ6Sz1PqLwifFez7vQEWJncKUMQPam1+YscEqvQFse+CX66OngaHvzwA kqm8p2mrGr+nhz/BqfySrwF9rSyk4h90pejCLYjg7ePpVUz6GH6Ac46V9QovTxf7flj7 MIpFsdinTaHxWI7D82OVxDsZXwiy7ArIEmb+eBTBqQOQiZMbdoxKKyJi84uIh8ddy4Dn AYQQ== X-Gm-Message-State: AO0yUKXA5UiM/12ux8GDKvNpEJqsR3lkMj9fiHsx0NW/kJy+bQ2c5iaQ jGC5Sxf7Q34+qlEark6z6UA7CDtDD7BXs2wVXGA160ZCAeM= X-Google-Smtp-Source: AK7set9kyevO/kbcKUV7HBPmV3VH2qyjqmmaLfr4iJbJoE6qkpfK2q0h24tbLaF4QyjuljZ5ipF2cwDBCWTXs1fDAgc= X-Received: by 2002:ab0:5b59:0:b0:68b:9eed:1c7d with SMTP id v25-20020ab05b59000000b0068b9eed1c7dmr456000uae.0.1677540472201; Mon, 27 Feb 2023 15:27:52 -0800 (PST) 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 References: In-Reply-To: From: Alan Somers Date: Mon, 27 Feb 2023 16:27:40 -0700 Message-ID: Subject: Re: can another disk be added to a zfs stripe To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-2.92 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.915]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_NA(0.00)[freebsd.org]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.44:from]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.44:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[asomers]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4PQc9j38D8z3wdB X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 4:11 PM void wrote: > > On Mon, Feb 27, 2023 at 03:52:46PM -0700, Alan Somers wrote: > > >Yes, that should work. But why would you want to? If it's just a > >matter of adding space to the guest, you'd be better off simply > >enlarging the zvol. > > I wondered about that. But how would the guest handle it? > Would I not have to tell the zfs guest that there's more space, > or is it automatic? > -- First, check the partition table in the guest. If ZFS is the last partition, then it isn't hard. The steps are: * Enlarge the zvol in the host * Reboot the guest, if it doesn't automatically see the size change. * Resize the partition in the guest, with a command like "gpart resize -i 3 vtbd0". You may also need to do "gpart recover vtbd0" * Then ZFS should automatically resize, if the pool's autoexpand property is set. If not, do "zpool online -e zroot vtbd0p3". From nobody Mon Feb 27 23:42:38 2023 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 4PQcVk3p6Jz3tZMq for ; Mon, 27 Feb 2023 23:42:38 +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 4PQcVk2lsxz41Tx for ; Mon, 27 Feb 2023 23:42:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677541358; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hqrS+ooUXvKkmDjIoGKBgrvl9W64AKONHeFjWXLfJKU=; b=YqWCPImGmBhFyLtjxNNzsgooDrUHC4NAXgYnH4D13knl11VRRpJfqvgI5tRLpP4dcDHZ3C sT4yoKaSVZVZPdHiXPWaccmPvSEcibYpwzoadjQBB+O+sWWc7PXbSKJu7E0JbBprkC53hW FQlij4o52D9tn27b5e8yHq4CgZlfoceT5DNjhwCgNUp22cPxdv7ybs+4panNzWdqrACHFL omCPAN4x1YOhPQDBrrRot9DWRszoHIKz22GbYkJTIYqBzj7fZ1CwRqntGLDnEvItHI3xfZ kGn2pxqJ2NUNh94uneeZ4lXZlZmz4cFashwm+1n4VCKuC+wjzJ6j46mPT92vKQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677541358; a=rsa-sha256; cv=none; b=ZnpicK2rscIlYsmdF74lCIfWIrg7rMV4hGdAzZFr8YTunv2fuRaM5JolTP6X7GKLGYe9dW o2zOFKQteWpcy5cwy2pnDR4nPbepXDXKd5IsVjFychg4RfS23O6fBQMmd8jgTrjEgpf9vv BkPdLyXmAAjQ1oUz0ltACjHwGl1FBelbWKhYiokL4hUT//pfN5DHWGD3KGabqNEBwnK75h b4QkhRTcntPsBzshVGYNA9sQa7+RkcuYLMA2sqLBI1v5ig4U9jM+PWdkTPL6ft5jkMfmOH 9y3NTQ8hzUQ9oFcV61tpw1buGYuBr0opT6YQ6tM6UNyRcCqyiTZxtAMWiNNArg== 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 4PQcVk1sCfzlqs for ; Mon, 27 Feb 2023 23:42:38 +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 31RNgcAX024048 for ; Mon, 27 Feb 2023 23:42:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RNgcmi024047 for fs@FreeBSD.org; Mon, 27 Feb 2023 23:42:38 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 106107] UFS: fsck_ffs: left-over fsck_snapshot after unfinished background fsck if filesystem clean Date: Mon, 27 Feb 2023 23:42:38 +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: 6.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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=3D106107 --- Comment #10 from Mark Millard --- (In reply to Kirk McKusick from comment #9) I expect that the background fsck ran on the system. But by the time I noticed the high % Capacity and then finally noticed the /.snap/fsck_snapshot , I did not find any evidence of a background fsck still being active. This means that I did not see the background fsck run, unfortunately. But the date/time on /.snap/fsck_snapshot made reasonable sense for time frame. My seeing the file indicates that the unlink did not happen by the time I noticed the file. That, of itself, may be odd. (And is what prompted me to submit the note.) --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Feb 28 00:27:21 2023 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 4PQdVK5vGnz3td0K for ; Tue, 28 Feb 2023 00:27:21 +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 4PQdVK4680z471S for ; Tue, 28 Feb 2023 00:27:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677544041; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yUdEexoIPra5W6pnISKdMLqaoYom/Wx+sCrZLSBK09o=; b=go4ASa3UXdyrA8UCeouIaOMtF5vG5Aqy7mbj9f9ptK3+p+B38luceGkRfA4RhOtjcgt5sM pH3Kx6yJ5hIICesPbqOWb552044Ez1yBAWfFJ3DCs3xVmHGiiEgr9TJWSGRkUdhkSYqDlf 2B9Jwx1ogXERLuVdrn9Ew1D5LECkZQfu2mf4y6yYI+S+JWDDVvO4mNxANjZSw/DVTOnmEA MlQlApzJCsu4QCT9wtzNMyuzXWQqISDV+9lO83z4WcYILjztHNxxDuv9JW6okeEl1kx5A7 3aCYkMN2uOZIsFXoEhacA4xCJy0mqhCd1o2dDcPoJwmCdBN53V0lGMlLSOBkoQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677544041; a=rsa-sha256; cv=none; b=PdkWQaGAtbXm3ANT7wcqocwulZgJeWJYIqqB4iXVTjIW3f0e0eTpOK+bsh5uX5enooddm/ TV1qxSBbMgXetw3J7mBUavBjKDiSbO9jIfuT83ZYFT/LnyhUJmwiyY/OP/NyMiYoqQm4vB GQef0KFnfGC+NWIpWJOAU6Z2UKkUAz/DRLItV0xRoP5aYWI6LFgn1BDIm3uvq6PRwuJ/V4 xV+c6bjG9f2kZeA9rdV8vCiYecPju3LGVnCa7Z1xpPUNJJneUit1vsjjncGVtZGxea9V5N XI1W2mdnHU93oxl+apIds/IFfYoSJc70lbwAONA4FOTOV3F21d3rCuROGBtisg== 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 4PQdVK2txmzmg4 for ; Tue, 28 Feb 2023 00:27:21 +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 31S0RLCT086864 for ; Tue, 28 Feb 2023 00:27:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31S0RLeW086863 for fs@FreeBSD.org; Tue, 28 Feb 2023 00:27:21 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 106107] UFS: fsck_ffs: left-over fsck_snapshot after unfinished background fsck if filesystem clean Date: Tue, 28 Feb 2023 00:27:21 +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: 6.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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=3D106107 --- Comment #11 from Kirk McKusick --- (In reply to Mark Millard from comment #10) There is a brief window when the file exists. The snapshot request is made.= The resulting file is opened by fsck. The file is then unlinked. If fsck exits = or the kernel dies after the snapshot is created and before the unlink is done then the file will remain. It is possible that you somehow hit that window. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Feb 28 01:17:18 2023 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 4PQfbz5MmBz3thQ9 for ; Tue, 28 Feb 2023 01:17:19 +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 4PQfbz4Jpyz4FjD for ; Tue, 28 Feb 2023 01:17:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677547039; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xom6buw5rUGe9Kdx4nrsJ2pCr8RjxpO0dvdfa8kC7PM=; b=di+svcgP/TBvta4tVtWGyotubzAeExeSLjjtFoVEekH1M5zCVv9fagb8SXlrT5Dnzwmazx bm8XvOd6BmhXaF5h/4XBej24zDgxqXnzZOcq5izclB6UojXfH34K/Gqcq8DqMyY1502/5s 7nfUTZOzlrjhQ/vtrID50qd1G5XDu780hnyVpaDQu5eIeFuQzFiybi35vPAHsvEyLORjoq arL4uxz9uWZgh56FjbrJlSGSV4shiBybR+l1Mi6Gco1J3EgFA7Ng95rzVnfEHwePhKXgNV QiJyxtobehNlkssR/y0uZTPPSkimrOIlAca7D2YbsAu5AZ3TZsQfNJ8FAgfgKg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677547039; a=rsa-sha256; cv=none; b=LF7YCTAjMtCHzygocFs2fvpSkll2aP6874MnDSNzqLUoChyXkCk/MlHO3vEX4oyywtOmAw GK3NdJxQvacY6pOcFN3AFn33aRpY4sGD0hb9PA6RZlnkH/87F7kECEsuLODTCzKmRCsxBg MMIf2hKP+rarsnLPRZo4Y41JU1w0yXK41bJUzuHmi5uvndfx/mc9i4gPt+r8QIfw/OSjao h5JDARZJTu9aq1yp8zM2tORFIFGEenb+cXwJ6u5sQYdbKasswoQoxquwFDCCN6gL9UOWMZ 58EW0W8faSgnmxZp1vzZpQ9gHDOhnxJDnDBcXZUXMPT8ULvIARBOqNeDpnRR9A== 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 4PQfbz3Ky5zny1 for ; Tue, 28 Feb 2023 01:17:19 +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 31S1HJGS063053 for ; Tue, 28 Feb 2023 01:17:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31S1HJDJ063052 for fs@FreeBSD.org; Tue, 28 Feb 2023 01:17:19 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 106107] UFS: fsck_ffs: left-over fsck_snapshot after unfinished background fsck if filesystem clean Date: Tue, 28 Feb 2023 01:17:18 +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: 6.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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=3D106107 --- Comment #12 from Mark Millard --- (In reply to Kirk McKusick from comment #11) FYI: There were no kernel crashes before, during, or after. Other than % Capacity and /.snap/fsck_snapshot existence issue, things seemed normal. So it would seem that the fsck probably exited before the unlink was done, leaving the file in place. Sounds like such is an expected possibility. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Feb 28 14:09:06 2023 X-Original-To: freebsd-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 4PQzkb61Tmz3vVHr for ; Tue, 28 Feb 2023 14:09:11 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4PQzkZ5Rfnz4K0l for ; Tue, 28 Feb 2023 14:09:10 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=gjD16u6S; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=dTuvBJgF; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.29 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 150555C009C for ; Tue, 28 Feb 2023 09:09:09 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 28 Feb 2023 09:09:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1677593349; x=1677679749; bh=QsMJVdcalh Dz2s9tQRNIjHHjuRF5DTS5XYtiESt55Ug=; b=gjD16u6SJy6gNbqZajlig4K/ER cRAn3D00tkqwzaUjW1v3396I/KPB8JVYH9HuJk0GqiZA+Do4Wxnfae+QJru85Jnx p/cP98Pre9TT2/VqJk36afKZs8EmMj1E0QkkcZrsPHuC+BXUHCzHNLjXg1hKMXqI zLyNDIyifrQ3yvIZQdzBjOf90T046g0jJWlyhTCJ2uGAn84aF++4KypwfYv8gSgf xUNIvb4hvrtTe/3ArneylAP3ZjvIAlqQ2F5d35e9SHTZFu347ab6i8mCLbuo7XMA SisGB7Tblo04dM9eHX0PffLWaiZ1/+2JgUG9c9Or/nC3G6l70G86HQJluc9w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1677593349; x=1677679749; bh=QsMJVdcalhDz2s9tQRNIjHHjuRF5 DTS5XYtiESt55Ug=; b=dTuvBJgFDEe+ZptVC1oDvjPRZkgHzTu26upCKDz56i7U vrpF1nWQyIAn2CrK+7ynYOwGve8VWNAjTlEIelr9msj14sJ4rifXhy4hH2DHQaTD r/Kt8zw59ItmiYxbB80zMjeRk87fxNReUNBwxXy/pwdT9t05u+JN7soWHIcHCalq D6xv8+Pl+Q1ht3aXnLvVqxP3TkMyFb+IO77B7lWgRXvDIjom8yObI2rxNg6Meu8m 4apOeo034c7esRk2qItNXTDChN0IllunneGF5W8YH8I6QG0Yv5IOnXmScRVEANaj XQCJdnMOMNK5UUPWT4zVsuc8Zui1nLMJViJrhQvjbQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudelvddgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 28 Feb 2023 09:09:08 -0500 (EST) Date: Tue, 28 Feb 2023 14:09:06 +0000 From: void To: freebsd-fs@freebsd.org Subject: Re: can another disk be added to a zfs stripe Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org References: 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-4.60 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PQzkZ5Rfnz4K0l X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 04:27:40PM -0700, Alan Somers wrote: >On Mon, Feb 27, 2023 at 4:11 PM void wrote: >> >> On Mon, Feb 27, 2023 at 03:52:46PM -0700, Alan Somers wrote: >> >> >Yes, that should work. But why would you want to? If it's just a >> >matter of adding space to the guest, you'd be better off simply >> >enlarging the zvol. >> >> I wondered about that. But how would the guest handle it? >> Would I not have to tell the zfs guest that there's more space, >> or is it automatic? >> -- > >First, check the partition table in the guest. If ZFS is the last >partition, then it isn't hard. The steps are: >* Enlarge the zvol in the host >* Reboot the guest, if it doesn't automatically see the size change. >* Resize the partition in the guest, with a command like "gpart resize >-i 3 vtbd0". You may also need to do "gpart recover vtbd0" >* Then ZFS should automatically resize, if the pool's autoexpand >property is set. If not, do "zpool online -e zroot vtbd0p3". > TYVM thats very helpful. I've saved this also to my dir of sysadmin tips because until now the information wasn't all in one place (well it might be but I couldn't find it at the time) thanks again, -- From nobody Tue Feb 28 15:37:51 2023 X-Original-To: freebsd-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 4PR1jH0NQKz3tbK3 for ; Tue, 28 Feb 2023 15:38:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4PR1jF4bV7z3ChQ for ; Tue, 28 Feb 2023 15:38:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.17.1/8.17.1) with ESMTPS id 31SFbqQS017500 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 28 Feb 2023 17:37:55 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 31SFbqQS017500 Received: (from kostik@localhost) by tom.home (8.17.1/8.17.1/Submit) id 31SFbpGx017499; Tue, 28 Feb 2023 17:37:51 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 28 Feb 2023 17:37:51 +0200 From: Konstantin Belousov To: Alexander Lochmann Cc: freebsd-fs@freebsd.org Subject: Re: Understanding locking for buf Message-ID: References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> <8e9ac2ec-6387-27b0-5cdc-1d61dbe2c831@tu-dortmund.de> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8e9ac2ec-6387-27b0-5cdc-1d61dbe2c831@tu-dortmund.de> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on tom.home X-Spamd-Result: default: False [-2.83 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.83)[-0.830]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_SOFTFAIL(0.00)[~all:c]; HAS_XAW(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4PR1jF4bV7z3ChQ X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N On Mon, Feb 27, 2023 at 04:04:30PM +0100, Alexander Lochmann wrote: > > > On 27.02.23 15:23, Konstantin Belousov wrote: > > Not quite. Sync io (bread()) means that caller performs bufwait() on the > > buffer. It is still subject to the LK_KERNPROC ownership move. > Ehm. Has this behavior changed recently? > Our kernel version uses LK_KERNPROC to distinguish between sync and async > IO. How would that be possible if ownershipt changes in either case? > https://iris.cs.tu-dortmund.de/freebsd-lockdoc/latest/source/sys/geom/geom_vfs.c#L127 I think this is simply not _very_ accurate. It would still catch some sync operations. From nobody Tue Feb 28 20:44:14 2023 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 4PR8VQ6kvpz3tvxn for ; Tue, 28 Feb 2023 20:44:14 +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 4PR8VQ3xSWz3xpj for ; Tue, 28 Feb 2023 20:44:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677617054; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GydCrBB2Eqp7J1uUmbZcnCwFbg2aNMJJ1HNpfGWO7Fs=; b=hGn8Jxa589gOzcx9/zhHob1KfsWNDHQR+E+F70kfhn7/MrPUHCOwyBdbnbhVEeCNgXnTvm G9REBeYwYUcnMOIwPvI/tiENIhIRorldO76EgiRc8rmYo1SMn2C+8gc4lo78ZU9G2ROf7A FWN9Idgl76Sehliv4T1As+5G/lNOa0S0QRdqTz8m7HsaetkbVQGua96DbywRApuHXCqnM3 0TErlS6P2HG8IldjPZHxZUtP3suUwwPUCWf5zEEhd62KTYmQnIKqftf7k9iL/XAj8lj/6b erZ48tb7ud78Q/k1JpvcHSdJd3PS5snojXrIrbxLqmlQOXKaqWlY5FIAnfrVVg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677617054; a=rsa-sha256; cv=none; b=enbpkmtYQLNJG6JFhiadjkoe4/qIYOoE5Dhp9tuYXj8g1zK5g3m8Kwbukd7tiKFZ6bRhIP emHkhF+JPz8NoMRzSK2DZYi4Gx6AVhcIX71JQA5H6LgQK5Y3dRCkBL8MS+9+371M3/xRal +pT54qQU9UUb1qph3OujwZNYqEfKg2sYlGLmdjJ+P4yhTEbeqhll+WYPdTjdI30ypInlY6 iOqOgnNO/bHnKPDFKP74QaCEKdpqQq3k0P5+aXfFJTiOTIZf1EtQAOl1o+9GrAyzhhWNyi VsJJ6GrfawlcAFvcPsWqbla4PRWGndH5V4YZ3dK/K3TUgV3HcX5ixIi6407fVw== 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 4PR8VQ32d4z1M1y for ; Tue, 28 Feb 2023 20:44:14 +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 31SKiELA047042 for ; Tue, 28 Feb 2023 20:44:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31SKiEQ0047041 for fs@FreeBSD.org; Tue, 28 Feb 2023 20:44:14 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 106107] UFS: fsck_ffs: left-over fsck_snapshot after unfinished background fsck if filesystem clean Date: Tue, 28 Feb 2023 20:44:14 +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: 6.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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=3D106107 --- Comment #13 from Kirk McKusick --- (In reply to Mark Millard from comment #12) The open of the snapshot also includes the reading of the superblock on the snapshot. Until recently rather few checks were done, so a bad field in the superblock could create a wild pointer that would cause fsck to segment fau= lt. So that would be my best guess of what caused the premature exit with the snapshot still in place. I should reorganize the code to do the unlink immediately after the open to close that window. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Feb 28 21:07:53 2023 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 4PR91k1zNrz3tx1Q for ; Tue, 28 Feb 2023 21:07:54 +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 4PR91k0x9Fz42Wl for ; Tue, 28 Feb 2023 21:07:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677618474; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=W35OI7hy1cqHaKV6shmXfy9aCOXKuLn8tf/YlyXsA4o=; b=nxC9IkOVHzI0n8wMBk+POS+E2jdqMIpVb3tEK4kp0JO1RprXD2eJJCJJo1kkrs8P3D8vy4 M7ssoRl+6Qv/CooF4Sy7BGTeKa7vCOcJkiyPBDSGN+5R+eJNpfK1ZStkDNBMx6+LMCAXDP TnSqi6brlzw7lLeNJaKLrYdyQD74m3YVrSMU8dOHQZswjLR0Fz+2EhtRuOu61zciV/kI2n +VkRKIbMSxITxg3n2eVyRuLkqShr4ZNGErUHtEy7h61mu3+VQoPJUyKrsKXm84dR6bJWYc bvt1E4B5aoOOXyguWa+mpviZJFR2CAzw+eYukKyG6fj6v9nYp5Vs5RF+kN/G+w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677618474; a=rsa-sha256; cv=none; b=tOnmjyEAMnDou/hdqUz/KY8HoLGqiZGzyPDTSi5DAwgVR7IBwL5no4QzbllEloJwZIQRu9 tK61viP05HJR8ifCwGCpYO7bbq9vqK3EHpPKG/gO7Vodws9iP7M1IiZSqJoh3c1eDIcGom TAzxsd3II+ZnSvrnRoYxDEp976+a8FhNJPK8xLxRJG43Lss00oKb+0Nqmkg3jYM+JGeMhG gcxWS51VLGLpqN8yKWU31HH/svTu2BPopr7gcI9bGGIkNeaL5+MuhDbqa3m/5YvxfDme+O najB4IP6j6b/4iXX0Locr9LJWsAqcsg70d1AtEyq+xe5ytcYbt+BYH0lj4LUkA== 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 4PR91j75p5z1Mj5 for ; Tue, 28 Feb 2023 21:07:53 +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 31SL7raW077304 for ; Tue, 28 Feb 2023 21:07:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31SL7rfO077303 for fs@FreeBSD.org; Tue, 28 Feb 2023 21:07:53 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 106107] UFS: fsck_ffs: left-over fsck_snapshot after unfinished background fsck if filesystem clean Date: Tue, 28 Feb 2023 21:07:53 +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: 6.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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=3D106107 --- Comment #14 from Mark Millard --- (In reply to Kirk McKusick from comment #13) FYI: I did not find a .core file for fsck_ffs (or for any other program) when I did a 'find / -name "*.core" -print' . Similarly, looking in /var/log/messages did not show any examples of the likes of messages of the form: pid ???? (????), jid ????, uid ????: exited on signal ???? for that day. Separately: It does sound like moving the unlink to just after the open would be appropriate. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Wed Mar 1 18:03:47 2023 X-Original-To: freebsd-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 4PRhtt6Vknz3v97s for ; Wed, 1 Mar 2023 18:03:50 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Received: from unimail.uni-dortmund.de (mx1.hrz.uni-dortmund.de [129.217.128.51]) (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 (2048 bits) client-digest SHA256) (Client CN "unimail.tu-dortmund.de", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PRhts56m2z443d for ; Wed, 1 Mar 2023 18:03:49 +0000 (UTC) (envelope-from alexander.lochmann@tu-dortmund.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tu-dortmund.de header.s=unimail header.b=oQyE0ZSt; spf=pass (mx1.freebsd.org: domain of alexander.lochmann@tu-dortmund.de designates 129.217.128.51 as permitted sender) smtp.mailfrom=alexander.lochmann@tu-dortmund.de; dmarc=none Received: from [192.168.111.37] (i5C750090.versanet.de [92.117.0.144]) (authenticated bits=0) by unimail.uni-dortmund.de (8.17.1.9/8.17.1) with ESMTPSA id 321I3lm4000551 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT); Wed, 1 Mar 2023 19:03:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tu-dortmund.de; s=unimail; t=1677693827; bh=YCub41V8+9fhLX30Yv0Z0pvdDCIunxuG/kCKjFS1iFw=; h=Date:To:Cc:References:From:Subject:In-Reply-To; b=oQyE0ZStrcEg+5xLKcn4oYUizxff0yUe29mEiwLRGDUMY98ZhRTcNo5Kqg8tI5JbA HKage4ZxY8ixXaNjkTByZJNcfNj9Asix/pqU6InLK0Bbs3wpjUnp4QTZl7sK1vi49+ KM/GlE+jGe4s4uDGWZf2RfY7tI2MJ9fZhIEplyz4= Message-ID: <1743b9f5-69be-b775-fb57-92b8115d4a81@tu-dortmund.de> Date: Wed, 1 Mar 2023 19:03:47 +0100 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 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Content-Language: de-DE-1901, en-US To: Konstantin Belousov Cc: freebsd-fs@freebsd.org References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> <8e9ac2ec-6387-27b0-5cdc-1d61dbe2c831@tu-dortmund.de> From: Alexander Lochmann Subject: Re: Understanding locking for buf In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------RIWHvPG9kSmr2T5vIOhd0fwJ" X-Spamd-Result: default: False [-7.30 / 15.00]; SIGNED_PGP(-2.00)[]; DWL_DNSWL_LOW(-1.00)[tu-dortmund.de:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; R_DKIM_ALLOW(-0.20)[tu-dortmund.de:s=unimail]; RCVD_IN_DNSWL_MED(-0.20)[129.217.128.51:from]; R_SPF_ALLOW(-0.20)[+ip4:129.217.128.0/24]; RWL_MAILSPIKE_GOOD(-0.10)[129.217.128.51:from]; MIME_BASE64_TEXT(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DMARC_NA(0.00)[tu-dortmund.de]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:680, ipnet:129.217.0.0/16, country:DE]; RCPT_COUNT_TWO(0.00)[2]; HAS_ATTACHMENT(0.00)[]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[tu-dortmund.de:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4PRhts56m2z443d X-Spamd-Bar: ------- X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------RIWHvPG9kSmr2T5vIOhd0fwJ Content-Type: multipart/mixed; boundary="------------bLHGYpgfwbv1HtsXKkYk0sh8"; protected-headers="v1" From: Alexander Lochmann To: Konstantin Belousov Cc: freebsd-fs@freebsd.org Message-ID: <1743b9f5-69be-b775-fb57-92b8115d4a81@tu-dortmund.de> Subject: Re: Understanding locking for buf References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> <8e9ac2ec-6387-27b0-5cdc-1d61dbe2c831@tu-dortmund.de> In-Reply-To: --------------bLHGYpgfwbv1HtsXKkYk0sh8 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 DQoNCk9uIDI4LjAyLjIzIDE2OjM3LCBLb25zdGFudGluIEJlbG91c292IHdyb3RlOg0KPiBP biBNb24sIEZlYiAyNywgMjAyMyBhdCAwNDowNDozMFBNICswMTAwLCBBbGV4YW5kZXIgTG9j aG1hbm4gd3JvdGU6DQo+Pg0KPj4NCj4+IE9uIDI3LjAyLjIzIDE1OjIzLCBLb25zdGFudGlu IEJlbG91c292IHdyb3RlOg0KPj4+IE5vdCBxdWl0ZS4gIFN5bmMgaW8gKGJyZWFkKCkpIG1l YW5zIHRoYXQgY2FsbGVyIHBlcmZvcm1zIGJ1ZndhaXQoKSBvbiB0aGUNCj4+PiBidWZmZXIu ICBJdCBpcyBzdGlsbCBzdWJqZWN0IHRvIHRoZSBMS19LRVJOUFJPQyBvd25lcnNoaXAgbW92 ZS4NCj4+IEVobS4gSGFzIHRoaXMgYmVoYXZpb3IgY2hhbmdlZCByZWNlbnRseT8NCj4+IE91 ciBrZXJuZWwgdmVyc2lvbiB1c2VzIExLX0tFUk5QUk9DIHRvIGRpc3Rpbmd1aXNoIGJldHdl ZW4gc3luYyBhbmQgYXN5bmMNCj4+IElPLiBIb3cgd291bGQgdGhhdCBiZSBwb3NzaWJsZSBp ZiBvd25lcnNoaXB0IGNoYW5nZXMgaW4gZWl0aGVyIGNhc2U/DQo+PiBodHRwczovL2lyaXMu Y3MudHUtZG9ydG11bmQuZGUvZnJlZWJzZC1sb2NrZG9jL2xhdGVzdC9zb3VyY2Uvc3lzL2dl b20vZ2VvbV92ZnMuYyNMMTI3DQo+IEkgdGhpbmsgdGhpcyBpcyBzaW1wbHkgbm90IF92ZXJ5 XyBhY2N1cmF0ZS4gIEl0IHdvdWxkIHN0aWxsIGNhdGNoIHNvbWUgc3luYw0KPiBvcGVyYXRp b25zLg0KPiANCkknbSBzb3JyeS4gV2hhdCBkbyB5b3UgbWVhbj8gQ2FuIHlvdSBwbGVhc2Ug Z2l2ZSBtb3JlIGRldGFpbHM/DQoNCllvdSBzYWlkIHRoYXQgdGhlIGJ1ZiBpcyBzdGlsbCBz dWJqZWN0IHRvIHRoZSBMS19LRVJOUFJPQyBvd25lcnNoaXAgbW92ZSANCmV2ZW4gZm9yIHN5 bmMgSU8uDQpCdXQgd2h5IGlzIExLX0tFUk5QUk9DIHVzZWQgdG8gZGlzdGluZ3Vpc2ggYmV0 d2VlbiBzeW5jIGFuZCBhc3luYyBJTz8NCkhhdmUgbG9vayBhdCBnX3Zmc19kb25lOiANCmh0 dHBzOi8vaXJpcy5jcy50dS1kb3J0bXVuZC5kZS9mcmVlYnNkLWxvY2tkb2MvbGF0ZXN0L3Nv dXJjZS9zeXMvZ2VvbS9nZW9tX3Zmcy5jI0wxMjcNCklmIHlvdSBvd25lcnNoaXAgaXMgbW92 ZWQgaW4gZWl0aGVyIGNhc2UsIG5vbmUgb2YgdGhlIGZvbGxvd2luZyBsaW5lcyANCndvdWxk IGJlIGV4ZWN1dGVkOiAnbXAtPm1udF9zdGF0LmZfc3luY3JlYWRzKys7JyANCidtcC0+bW50 X3N0YXQuZl9zeW5jd3JpdGVzKys7Jy4NCg0KLSBBbGV4DQoNCi0tIA0KVGVjaG5pc2NoZSBV bml2ZXJzaXTDpHQgRG9ydG11bmQNCkNvbXB1dGVyIFNjaWVuY2UgWElJIC0gU3lzdGVtIFNv ZnR3YXJlIEdyb3VwDQpBbGV4YW5kZXIgTG9jaG1hbm4gICAgICAgICAgICAgICAgUEdQIGtl eTogMHhCQzNFRjZGRA0KT3R0by1IYWhuLVN0ci4gMTYgICAgICAgICAgICAgICAgIHBob25l OiAgKzQ5LjIzMS43NTU2MTQxDQpELTQ0MjI3IERvcnRtdW5kICAgICAgICAgICAgICAgICAg ZmF4OiAgICArNDkuMjMxLjc1NTYxMTYNCmh0dHBzOi8vc3lzLmNzLnR1LWRvcnRtdW5kLmRl L2FsDQo= --------------bLHGYpgfwbv1HtsXKkYk0sh8-- --------------RIWHvPG9kSmr2T5vIOhd0fwJ Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEElhZsUHzVP0dbkjCRWT7tBbw+9v0FAmP/k4MFAwAAAAAACgkQWT7tBbw+9v3l 3g//T7VPq4tzfkphx5rwBQsoj5A4TSVdvjwz+S2EZyR7IYTIq0j8Uv8BZakUcZJWOECYP7oxQsU1 eCFFl3U76OwNyJeM6K3dDM1+Bion0i6sveIoQ2RPsQUBDdZ9YCQ5A9UL4uwmy5af9ig68Nycej6q LBd2TV5X+p4lyFmfwPu/sOeX1Vf2CbImITi0Cr0YUVZGf4dLoq6zRfNOSim0Uww5DfkvKT9+zXZc 2BrcqBNUIuMAis80eqCIz5K1rUJR2smiPsQIZiQ4tFZ/Ke1P9JaJGkrIykyMN3LhGOLJ0Cn4cUMQ DydC4ct6GAyaqrzjCB2Jvg2XEPmku4scEUfr7mU+e4BZp4ffBZD4725Z0W1+V6pkmx+o7GCTMyFx lEJdyDxbFQdClofnbHYBq2zPBsIEKy6PeqY+40uRNuOiU1Yoz6SV2AElbeGkN73BzMcJEIUH3PiB nrgw5PFiVz4Iwy0MUPvi3EKleh8p4OjYP71Whdfv6pm2u5shXesGS8EoOVFKFQHdyn5uqlzUrRHz sR31zWLVgFhEeB4fZAo4gogmGE12Rzej63iYvKmGN06dbFNi+32sWAL6U/QKQH+Rmlpg0U+kPD4D oLepA5UQjDPmQCWUQsC54+Z0shTLiO13iAKtvkqEUjsWRnN8QXOQdLZ/jIycRtqyU/7NE6xYcizz 4+g= =jrAR -----END PGP SIGNATURE----- --------------RIWHvPG9kSmr2T5vIOhd0fwJ-- From nobody Fri Mar 3 00:19:32 2023 X-Original-To: freebsd-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 4PSTB43R1Tz3wRCK for ; Fri, 3 Mar 2023 00:19:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4PSTB35xsbz4N5P for ; Fri, 3 Mar 2023 00:19:39 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.17.1/8.17.1) with ESMTPS id 3230JWPe041398 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 3 Mar 2023 02:19:35 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 3230JWPe041398 Received: (from kostik@localhost) by tom.home (8.17.1/8.17.1/Submit) id 3230JWsf041397; Fri, 3 Mar 2023 02:19:32 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 3 Mar 2023 02:19:32 +0200 From: Konstantin Belousov To: Alexander Lochmann Cc: freebsd-fs@freebsd.org Subject: Re: Understanding locking for buf Message-ID: References: <45d84dae-0ca9-95ed-f6fd-8243797453ff@tu-dortmund.de> <8e8d9145-9ee1-195e-3dd3-4e3166ac8abb@tu-dortmund.de> <8e9ac2ec-6387-27b0-5cdc-1d61dbe2c831@tu-dortmund.de> <1743b9f5-69be-b775-fb57-92b8115d4a81@tu-dortmund.de> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1743b9f5-69be-b775-fb57-92b8115d4a81@tu-dortmund.de> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on tom.home X-Spamd-Result: default: False [-1.61 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.39)[0.385]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; HAS_XAW(0.00)[]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4PSTB35xsbz4N5P X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Wed, Mar 01, 2023 at 07:03:47PM +0100, Alexander Lochmann wrote: > > > On 28.02.23 16:37, Konstantin Belousov wrote: > > On Mon, Feb 27, 2023 at 04:04:30PM +0100, Alexander Lochmann wrote: > > > > > > > > > On 27.02.23 15:23, Konstantin Belousov wrote: > > > > Not quite. Sync io (bread()) means that caller performs bufwait() on the > > > > buffer. It is still subject to the LK_KERNPROC ownership move. > > > Ehm. Has this behavior changed recently? > > > Our kernel version uses LK_KERNPROC to distinguish between sync and async > > > IO. How would that be possible if ownershipt changes in either case? > > > https://iris.cs.tu-dortmund.de/freebsd-lockdoc/latest/source/sys/geom/geom_vfs.c#L127 > > I think this is simply not _very_ accurate. It would still catch some sync > > operations. > > > I'm sorry. What do you mean? Can you please give more details? > > You said that the buf is still subject to the LK_KERNPROC ownership move > even for sync IO. > But why is LK_KERNPROC used to distinguish between sync and async IO? > Have look at g_vfs_done: https://iris.cs.tu-dortmund.de/freebsd-lockdoc/latest/source/sys/geom/geom_vfs.c#L127 > If you ownership is moved in either case, none of the following lines would > be executed: 'mp->mnt_stat.f_syncreads++;' 'mp->mnt_stat.f_syncwrites++;'. All it means it that the statistic output by mount -v would be somewhat off in the split of io ops by sync/async. The total count is still correct. From nobody Fri Mar 3 04:38:50 2023 X-Original-To: freebsd-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 4PSZxS30lQz3wfv6 for ; Fri, 3 Mar 2023 04:39:08 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-8.consmr.mail.gq1.yahoo.com (sonic316-8.consmr.mail.gq1.yahoo.com [98.137.69.32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PSZxQ5Yhrz3hZJ for ; Fri, 3 Mar 2023 04:39:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=VnuNJ1V1; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.69.32 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1677818344; bh=pRM7xMJQBxvSjbW7nRd5zR+wxBa63ZUZIG2z8T70vy0=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=VnuNJ1V1BeHzIXiRyp+UynKSlZKLPHAIotHnX/GEQMsAHY9SNoMFkxPwBuD+aHVx1uRFEaSRXOl+xR6YQqG67PKLXTTwmMnoSjR2QfE9TxsyDHYba4Iu1/Q8NVjU2vC56H1kcohMQdCDiAYsQewlGeJrh76k4ZsQqgud9aOmhzhBZVi+8I9JXWUFXIPZQ7gs5bmC2o2HA5BujXSQsdN2lNxV8xzIbcYarStGximwYUuE79w3zVbCl/bY9WTBhM02UxOo31cXpO1/Ix71n7m+f23ExkDtoIXqfPOmCHOfI/SGBwwiBbBsoo161poOc1deKof3ZRKofWShnIowMl8iOg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1677818344; bh=h05Y+2xlSuGbTcKnNrGK6w3XWnvUlKyhAJFl+vwGahk=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=ZanPhNrsxUSsV3+eLf4ZuFvUQIoQoEu79cGS5i+RgHS+xvIi3jgxsg4kAAR7omc0CGQjZ0/MSKkEtoGJJJMGIaqAlm9sNkgE45inGDRJQ9DhHM/FCF5mO+W3mPeECgu1vEDG9vkDrQ4E+P9KSvp9NgC9a355i9OEYBiYQzZlvO19Y8Pc4yYza014nVOub3J1B5so6F9Efqn91k2u7VwBoGVs8K/O3DR99S096fAPt1zy9Kkb7B/C/eVM+BVl99A9XB9ZRzoX2d3poj0DlUCTd8FvoOxf4TFlGpnYifNYd+zBW2xZjLmAOyVqBXoF+cDVlZIziLEnfuWSF7XkHiv8rQ== X-YMail-OSG: t5hc3h4VM1kRDdxbNrfLOHJIzx2ecLUtdNE1Xenbc306QN8YgdKxg61Nb1Da2uQ 835AFvV16ZJkQsnjN20xWW.zWrz0fj.nQs4JsPw4ced28nP04VRmc9Cx7QgSa1Ioiqi.3typO7bT 3xPrZiw7KcvK45MGOXJJa3iKB5OaX3pivNQX2Lzz4oBjQPLGIMR.s4MCvBJZ.2osPheSlT9bC1JQ oMiQrknn2_ZnkshS6C8.zqwxmB_fZqDJs2rwlrOCLRJv11DynsFh0jaTawMiw.jpECSpO2C981LQ a3ZFinO8rWfD7R.TWQw2OMnSNmaupVfAsFlPPClnO.0xK18nZYL60b4ScCwXxjM6YMxiL8aT0uz_ ms7V_9nHYEM5EWLgN2qSqP9tC_lyi7PA2NUEgsVgG9nMmHGYO9ozx.yhIWO1AtPO.hKHD4RR80od xhMy7mGZlEy8BcSq3sB0YaUzqD5c_QWS._lUhHepr5zuglZZmlsTKUzNXd..exJCTOqdKhBLcruC 9itLzojWFJayGhcP56j3hSFs681rL_5hElQo3PRqBQPzlOUcKFFPahN7IGF8CRe.EXngYGbVCrvl yrLEmgfOEBExdBQ68hHAm.A5Ga7hcmJj3KAjFmuqWC_y1v4sB0cax3ZJpjXtQdQay5qko7ikWj0I 3MaoXdSyt49ZXBhGTExCzJsRkvWi5prBPzX19S6xigaSWheMCnc.wjDQqYPiMUF5opKDApQZ8dE1 PT1Ve.kxtx.VOA__CnmETEhbi608Fd58nTFjzR7LVDwkj66KfYVgT.rEBO7FSqizLNNuJXPP2NC9 bG_OYwKFxpLDzhp7oXlmfQ.PetHy1Z1aygwgSJ8bzTWI0CekR4psQ23tSg1ToDWITOqRDgSxscPt CUNx1qVILtLqhQYack2pireiGIlnXoNJOVv37.5x.8hr4bH6AUX2aRqNQT0RqDr11Z0iIVjNaVdW BTJys8ZVAY2smS.N99V_DqjLQG6Nj57XJAp54l4oX_3yp7CH4dk2F_RnaWm2FdSpvcYeSyQcDlCa dCQMyivI2yOR0ftEqG4SKXLCjz3kTtqGMeu.alMM4gzvwfzx_SK8PI12dmtpUG1YS0qQBUPXHE.u a.s1LbXY1.OgTSA2npzLVSwHOSS4F_FWRxBn5xJMgN0COLNj_kXZSXQsetMdVtRmzTDUgQmVsHdV LBLJXdje77iOngH1thFCFgfyd5v3UemOHE5EllQf3maI70GWnkMRWXxo4PgBRczMfJntP_p7Xbz8 mEvMTkXYwlHPFoYfdEQG21.ZiFAPqnj1ph50r6uXFDk63rGpnNlypCmOFepViS74PisvGkLISa8Y NOLnT6djiUsMAfpcvDVO6KeZCPAyiwFtqcKbgkUXI2JJiGUz5ziJEuku.cyVMiSH2Mrb5zLID12K J.jFuqw2GPATw39lv9K_rqiQrmtCe5z_A.UtlewucU9TC9uiNzDU1ko96ki7VLdxaqKoLFqjQt0t 2VJgvuZLDHt_wqmomPphM5Ka46iZ2zcf1JXyaT_yQQk9GAoVlEx9bUKqEpPT6ZmK4LVInvPr209Z q_p7P5rx.MBlWnjsijgGY0l5G9SmdUIoeZuuISf3igiBwxUbLG9E0GWhbJof3VPfdzpVp2SeT.0R BPUZl5U.1Dt80BvRc8PA5HPqcW1uZoHO8Voaf2nHLyFOo8HSzXF63iLSdk9Ngaqa_zAEVQG3TclN yOCDeLwSHZhh0fEghhvFZer5Q4OkE.x8uCg5ZjEXy.Hsm6b5VVqzpLz1exP7QSHIuAsYAL00Vhuy bVpfRvmD1PM7rkYkUP4oOpeEyF_gxrcm7Stk2DjXjP.73agUgZuHW8d6omG6yi1BACF7xuDt5So_ 0PrXjniL9v6warBeXL7AaujJ7Q9wrut71xDlbWUZbd46rYVi9U9atxUM1qx2v8Eqn_2ypAS70LHB THVC4Ny0I.nn5hnNxULgvJBoZTzc0TRmX81y3kGCD3XPU9kDiyj2GtGss2SmGAV70pU1BqZQZ5gT _5lbjdC7.MRFY0qZzyCOgQAOZuOHHalPRclohrU5VA.83WzYNaOgzszOG5sRC1XohtwegvpOZBdE sVGs7tDb6TPosKwICBAkbvGnwM5wnd2.iHqM1dp2.2BoxSM3YZ6nkRPCU05NKy4JW6KVHWDWV8vy bt4ygnbo079qgKfhO_8RRWu6JSFeaqxiOb.NUOx2nxmRMJ0jKd7oGXELtXiWD6zlBjfm_Qx3x9Io wjuGyxW2NfwZH_cVpiKQpATHke8dg6urZZpJ67KYhWHOsRhafIa4yURAbFPuvdg-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Fri, 3 Mar 2023 04:39:04 +0000 Received: by hermes--production-gq1-6cf7749bc8-vl5z2 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 5f18695f0362e69694998816a17fe104; Fri, 03 Mar 2023 04:39:01 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Subject: FYI: an example Optane Read failure on a HoneyComb (aarch64), main at e78dc78e517a Message-Id: <9BD87F9E-72FC-4907-862A-28D39872B530@yahoo.com> Date: Thu, 2 Mar 2023 20:38:50 -0800 To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.3731.400.51.1.1) References: <9BD87F9E-72FC-4907-862A-28D39872B530.ref@yahoo.com> X-Spamd-Result: default: False [-3.38 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.88)[-0.879]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.32:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.32:from] X-Rspamd-Queue-Id: 4PSZxQ5Yhrz3hZJ X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N FYI: I got the following error: nvme0: RECOVERY_START 411856860627824 vs 411855426224359 nvme0: Controller in fatal status, resetting nvme0: Resetting controller due to a timeout and possible hot unplug. nvme0: RECOVERY_WAITING nvme0: resetting controller nvme0: failing outstanding i/o nvme0: READ sqid:2 cid:5 nsid:1 lba:537405568 len:16 nvme0: ABORTED - BY REQUEST (00/07) crd:0 m:0 dnr:1 sqid:2 cid:5 cdw0:0 (nda0:nvme0:0:0:1): READ. NCB: opc=3D2 fuse=3D0 nsid=3D1 prp1=3D0 prp2=3D0= cdw=3D20082880 0 f 0 0 0 (nda0:nvme0:0:0:1): CAM status: CCB request completed with an error (nda0:nvme0:0:0:1): Error 5, Retries exhausted g_vfs_done():gpt/CA72optM2ufs[READ(offset=3D65536, length=3D8192)]enda0 = at nvme0 bus 0 scbus4 target 0 lun 1 nda0: rror =3D 5 s/n REDACTED detached (nda0:nvme0:0:0:1): Periph destroyed nvme0: waiting (After rebooting . . .) # gpart show -pl =3D> 40 1875384928 nda0 GPT (894G) 40 532480 nda0p1 CA72optM2efi (260M) 532520 2008 - free - (1.0M) 534528 20971520 nda0p2 CA72optM2swp10 (10G) 21506048 29360128 nda0p4 CA72optM2swp14 (14G) 50866176 33554432 nda0p5 CA72optM2swp16 (16G) 84420608 67108864 nda0p6 CA72optM2swp32 (32G) 151529472 364904448 nda0p7 CA72optM2swp174 (174G) 516433920 7340032 nda0p8 RPi3swp3p5 (3.5G) 523773952 13631488 - free - (6.5G) 537405440 1337979528 nda0p3 CA72optM2ufs (638G) =3D> 40 1875384928 nda1 GPT (894G) 40 532480 nda1p1 CA72opt0EFI (260M) 532520 2008 - free - (1.0M) 534528 515899392 nda1p2 CA72opt0SWP (246G) 516433920 20971520 - free - (10G) 537405440 1337979528 nda1p3 CA72opt0ZFS (638G) nda0 is a U2 Optane used via a M2 adapter. The error is the first that I've seen for it. (nda1 is in the PCIe slot.) # uname -apKU FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #88 = main-n261230-e78dc78e517a-dirty: Wed Mar 1 16:17:45 PST 2023 = root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400081 1400081 =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Fri Mar 3 04:50:50 2023 X-Original-To: freebsd-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 4PSbC66SVDz3wgDm for ; Fri, 3 Mar 2023 04:50:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PSbC64QxHz3jSd for ; Fri, 3 Mar 2023 04:50:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52c.google.com with SMTP id cy23so5546124edb.12 for ; Thu, 02 Mar 2023 20:50:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1677819056; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qAW9LZI6w6U7J/JPrv263mbZdEh6+YzbeEMFOqF/w2k=; b=AtGnptFRBaN3a6Pgtg2VV100hh7Njs9qwe26V2YeHQpQ4EXKf0ULXam/w2Q6+2mAIe IzSsEpsPYWHW7WEW0Tp5AxO7VySJqZ9Hq5ZfrLPV9b6v50ueqbdlsUg6fpaoI/p6uLKQ vgmDsrUSMHgtsuKtHlRXucORUdxU8D0aK3v4y/8s5uhODk//K/Wdhz8nhgYwCDAruJdH j2DPwNYyI7lqrnvwWSRNfIa7aaXoW4C/IzbgoPaLHv2iasaAjgyOWtN2/VZ1vABHY/RH brcg38auvettzHjN8gGn6+QDgZzATjOQ/7bfFuKYq7v80pOxJzOyZ0yndqk6CTSDiWzj RkFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677819056; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qAW9LZI6w6U7J/JPrv263mbZdEh6+YzbeEMFOqF/w2k=; b=Wy+PHWNHf+uZGCOWYsVPqG5uymN0zH5oXuhN9z8P4raoUx4UVnhaz8SEGZuTjqA1uH bSaFE/wLzBYLs28eUAogs94ouT19++s5sb1Ni77T8Y6K5qFQVFV6VzflG7WasQRQ+LBV ZOU2TCUcPWngcLhC2npycZKXv2wrtrdDUWL+ovtyJwMlkF08HH7n/kTbwdD9RnDGj/OS piilRYUIg7jJwj2WZr3TEk8VjyXTa21g5jnzGU42HF6OxHNLGP7quaX/BlcXnb1Dk3MC LjdG2dtfmsGpwRtDwVcTQfFIVJtOzL5AJFP+IgQ/n6+ECsl02dmqp2spVYbQuZcMwXDN kk7w== X-Gm-Message-State: AO0yUKVtI+XrB3J5fuYnpJqtzQBfKkTlTP0vheZHqfmvQP0/GMfQ4abh LUxHfn985POhhYY/waDIoB/BlH6EvRlLcd+2MZ3ngxpZkB+I8Q== X-Google-Smtp-Source: AK7set9Xb7ArDa/2ljeNxDvztF9gnGJG4KYhFe5lRb5tCg33RUXLHdIZEZTSEXKJ6Xn26UNZFX3LqgE2YQauV5lJQTE= X-Received: by 2002:a50:f619:0:b0:4be:f5a0:a80a with SMTP id c25-20020a50f619000000b004bef5a0a80amr406435edn.0.1677819055917; Thu, 02 Mar 2023 20:50:55 -0800 (PST) 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 References: <9BD87F9E-72FC-4907-862A-28D39872B530.ref@yahoo.com> <9BD87F9E-72FC-4907-862A-28D39872B530@yahoo.com> In-Reply-To: <9BD87F9E-72FC-4907-862A-28D39872B530@yahoo.com> From: Warner Losh Date: Thu, 2 Mar 2023 21:50:50 -0700 Message-ID: Subject: Re: FYI: an example Optane Read failure on a HoneyComb (aarch64), main at e78dc78e517a To: Mark Millard Cc: freebsd-fs@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d364e905f5f7b007" X-Rspamd-Queue-Id: 4PSbC64QxHz3jSd X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000d364e905f5f7b007 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 2, 2023 at 9:39=E2=80=AFPM Mark Millard wro= te: > FYI: I got the following error: > > nvme0: RECOVERY_START 411856860627824 vs 411855426224359 > Translation: We submitted transactions to the card and got a timeout waitin= g for them to finish. > nvme0: Controller in fatal status, resetting > The controller status bit indicating failure was on > nvme0: Resetting controller due to a timeout and possible hot unplug. > We read 0xfffffff from the card, indicating often a power glitch reset the card, but sometimes it's a bridge getting messed up so the address we think the card is at it isn't able to get transactions for. Or sometimes it's because the firmware crashes in the card. hard to diagnose for sure, but one thing is for sure: the card is AFU and we can't fix it. > nvme0: RECOVERY_WAITING > nvme0: resetting controller > nvme0: failing outstanding i/o > We reset the controller. > nvme0: READ sqid:2 cid:5 nsid:1 lba:537405568 len:16 > nvme0: ABORTED - BY REQUEST (00/07) crd:0 m:0 dnr:1 sqid:2 cid:5 cdw0:0 > (nda0:nvme0:0:0:1): READ. NCB: opc=3D2 fuse=3D0 nsid=3D1 prp1=3D0 prp2=3D= 0 > cdw=3D20082880 0 f 0 0 0 > (nda0:nvme0:0:0:1): CAM status: CCB request completed with an error > (nda0:nvme0:0:0:1): Error 5, Retries exhausted > g_vfs_done():gpt/CA72optM2ufs[READ(offset=3D65536, length=3D8192)]enda0 a= t > nvme0 bus 0 scbus4 target 0 lun 1 > nda0: rror =3D 5 > We failed enough times that we gave up. > > s/n REDACTED detached > (nda0:nvme0:0:0:1): Periph destroyed > nvme0: waiting > might indicate there's still a reference here, but maybe there's not. The one thing I don't do in recovery is try to power cycle the card. That's now possible with decent APIs in the kernel, but I haven't had the need to do it for our deployment. Warner > (After rebooting . . .) > > # gpart show -pl > =3D> 40 1875384928 nda0 GPT (894G) > 40 532480 nda0p1 CA72optM2efi (260M) > 532520 2008 - free - (1.0M) > 534528 20971520 nda0p2 CA72optM2swp10 (10G) > 21506048 29360128 nda0p4 CA72optM2swp14 (14G) > 50866176 33554432 nda0p5 CA72optM2swp16 (16G) > 84420608 67108864 nda0p6 CA72optM2swp32 (32G) > 151529472 364904448 nda0p7 CA72optM2swp174 (174G) > 516433920 7340032 nda0p8 RPi3swp3p5 (3.5G) > 523773952 13631488 - free - (6.5G) > 537405440 1337979528 nda0p3 CA72optM2ufs (638G) > > =3D> 40 1875384928 nda1 GPT (894G) > 40 532480 nda1p1 CA72opt0EFI (260M) > 532520 2008 - free - (1.0M) > 534528 515899392 nda1p2 CA72opt0SWP (246G) > 516433920 20971520 - free - (10G) > 537405440 1337979528 nda1p3 CA72opt0ZFS (638G) > > nda0 is a U2 Optane used via a M2 adapter. The error is the > first that I've seen for it. (nda1 is in the PCIe slot.) > > # uname -apKU > FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #88 > main-n261230-e78dc78e517a-dirty: Wed Mar 1 16:17:45 PST 2023 > root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/ar= m64.aarch64/sys/GENERIC-NODBG-CA72 > arm64 aarch64 1400081 1400081 > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > > --000000000000d364e905f5f7b007 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Mar 2, 2023 at 9:39=E2=80=AFP= M Mark Millard <marklmi@yahoo.com> wrote:
FY= I: I got the following error:

nvme0: RECOVERY_START 411856860627824 vs 411855426224359

=C2=A0
nvme0: Controller in fatal status, resetting

The controller status bit indicating failure was on
=C2= =A0
nvme0: Resetting controller due to a timeout and possible hot unplug.

We read 0xfffffff from the card, indicating = often a power glitch reset the card, but sometimes it's a bridge gettin= g messed up so the address we think the card is at it isn't able to get= transactions for. Or sometimes it's because the firmware crashes in th= e card. hard to diagnose for sure, but one thing is for sure: the card is A= FU and we can't fix it.
=C2=A0
nvme0: RECOVERY_WAITING
nvme0: resetting controller
nvme0: failing outstanding i/o

We reset= the controller.
=C2=A0
nvme0: READ sqid:2 cid:5 nsid:1 lba:537405568 len:16
nvme0: ABORTED - BY REQUEST (00/07) crd:0 m:0 dnr:1 sqid:2 cid:5 cdw0:0
(nda0:nvme0:0:0:1): READ. NCB: opc=3D2 fuse=3D0 nsid=3D1 prp1=3D0 prp2=3D0 = cdw=3D20082880 0 f 0 0 0
(nda0:nvme0:0:0:1): CAM status: CCB request completed with an error
(nda0:nvme0:0:0:1): Error 5, Retries exhausted
g_vfs_done():gpt/CA72optM2ufs[READ(offset=3D65536, length=3D8192)]enda0 at = nvme0 bus 0 scbus4 target 0 lun 1
nda0: rror =3D 5

We failed enough times= that we gave up.
=C2=A0
<INTEL SSDPE21D960GA E2010480 REDACTED>
=C2=A0s/n REDACTED detached
(nda0:nvme0:0:0:1): Periph destroyed
nvme0: waiting

might indicate there'= ;s still a reference here, but maybe there's not.

<= div>The one thing I don't do in recovery is try to power cycle the card= . That's now possible with decent APIs in the kernel, but I haven't= had the need to do it for our deployment.

War= ner
=C2=A0
(After rebooting . . .)

# gpart show -pl
=3D>=C2=A0 =C2=A0 =C2=A0 =C2=A0 40=C2=A0 1875384928=C2=A0 =C2=A0 nda0=C2= =A0 GPT=C2=A0 (894G)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40=C2=A0 =C2=A0 =C2=A0 532480=C2=A0 nda0= p1=C2=A0 CA72optM2efi=C2=A0 (260M)
=C2=A0 =C2=A0 =C2=A0 532520=C2=A0 =C2=A0 =C2=A0 =C2=A0 2008=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 - free -=C2=A0 (1.0M)
=C2=A0 =C2=A0 =C2=A0 534528=C2=A0 =C2=A0 20971520=C2=A0 nda0p2=C2=A0 CA72op= tM2swp10=C2=A0 (10G)
=C2=A0 =C2=A0 21506048=C2=A0 =C2=A0 29360128=C2=A0 nda0p4=C2=A0 CA72optM2sw= p14=C2=A0 (14G)
=C2=A0 =C2=A0 50866176=C2=A0 =C2=A0 33554432=C2=A0 nda0p5=C2=A0 CA72optM2sw= p16=C2=A0 (16G)
=C2=A0 =C2=A0 84420608=C2=A0 =C2=A0 67108864=C2=A0 nda0p6=C2=A0 CA72optM2sw= p32=C2=A0 (32G)
=C2=A0 =C2=A0151529472=C2=A0 =C2=A0364904448=C2=A0 nda0p7=C2=A0 CA72optM2sw= p174=C2=A0 (174G)
=C2=A0 =C2=A0516433920=C2=A0 =C2=A0 =C2=A07340032=C2=A0 nda0p8=C2=A0 RPi3sw= p3p5=C2=A0 (3.5G)
=C2=A0 =C2=A0523773952=C2=A0 =C2=A0 13631488=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 - free -=C2=A0 (6.5G)
=C2=A0 =C2=A0537405440=C2=A0 1337979528=C2=A0 nda0p3=C2=A0 CA72optM2ufs=C2= =A0 (638G)

=3D>=C2=A0 =C2=A0 =C2=A0 =C2=A0 40=C2=A0 1875384928=C2=A0 =C2=A0 nda1=C2= =A0 GPT=C2=A0 (894G)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40=C2=A0 =C2=A0 =C2=A0 532480=C2=A0 nda1= p1=C2=A0 CA72opt0EFI=C2=A0 (260M)
=C2=A0 =C2=A0 =C2=A0 532520=C2=A0 =C2=A0 =C2=A0 =C2=A0 2008=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 - free -=C2=A0 (1.0M)
=C2=A0 =C2=A0 =C2=A0 534528=C2=A0 =C2=A0515899392=C2=A0 nda1p2=C2=A0 CA72op= t0SWP=C2=A0 (246G)
=C2=A0 =C2=A0516433920=C2=A0 =C2=A0 20971520=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 - free -=C2=A0 (10G)
=C2=A0 =C2=A0537405440=C2=A0 1337979528=C2=A0 nda1p3=C2=A0 CA72opt0ZFS=C2= =A0 (638G)

nda0 is a U2 Optane used via a M2 adapter. The error is the
first that I've seen for it. (nda1 is in the PCIe slot.)

# uname -apKU
FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #88 main-n261230-e7= 8dc78e517a-dirty: Wed Mar=C2=A0 1 16:17:45 PST 2023=C2=A0 =C2=A0 =C2=A0root= @CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aar= ch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400081 1400081

=3D=3D=3D
Mark Millard
marklmi at yahoo.com


--000000000000d364e905f5f7b007-- From nobody Fri Mar 3 23:20:14 2023 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 4PT3q329Kqz3wSZS for ; Fri, 3 Mar 2023 23:20:15 +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 4PT3q317Wgz4LfV for ; Fri, 3 Mar 2023 23:20:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677885615; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=K507Q7HgE/53+eFYUeOP14AezhWtGF5/jd5YpSuVtIQ=; b=GdSOQXWTqYHqVTDAKmEFnmZ13szeeJA0lb79K2PZKB8s27ODr/K4c1O4ZGadRh0KpBqSTp KFHZaakwNE7bv+C6ANzaLkjMq0Vi/d0hsul8JPX07HZ3pCv8rNG2qSurqpF/kr7ex/FJhu 9TliR4zk6BtmLxCFzQRHq0suRCGCc3+Fbq9b21R3Ufvi8BXYB0Mwmf9flsx+cCxzjn6wYk 7tCDioREJzO1OkgWerk5tyFikrfaM9kq2/ABSIklS9DUsp8eF4iUsoq26aL+iNMbXbBtRo u9zfDZMOEqOAyRYqihIdGDY6QZUpniOKj9LTfnsoBOhDTo+qGmwzm2yUT/UGSA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677885615; a=rsa-sha256; cv=none; b=OqwdufKcQV0UE3JRdnI1mG7geqLDW7WjPqmfPgKTvlHEJa0XuGeIq+7M9SVAf04K2IQypl BehRm1OsZ3MtTgEU3CXjGZn2jketCbhWjX9Rdn0/AaOCGH4Auobt/20OLfbeqLtXBI/PsA 02F1U4NdoHZO1bNB7HJqyEDb8Z8Gg+yQRpsgcWc/PtR8PDebP/eLr7IcJsnVnHp4PCY+i3 qsd2I1GcFbX/7cldNGYfqxLl4PnJSHrqnbblXGxJ4XfvMWQvNkyblx0MK12gNrUxHs/Ual wlk6G+suL/ociqG4gAPluz5ZznswbE8Kp+eVO9GjlIkrevgJVhYR18bX1af5yQ== 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 4PT3q30DR9zHNb for ; Fri, 3 Mar 2023 23:20:15 +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 323NKE1s009332 for ; Fri, 3 Mar 2023 23:20:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 323NKEYW009331 for fs@FreeBSD.org; Fri, 3 Mar 2023 23:20:14 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Fri, 03 Mar 2023 23:20:14 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: george@m5p.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #89 from George Mitchell --- After getting another instance of my crash on my test disk and then booting from the correct disk, I got a crash summary that said: Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [= in module /usr/lib/debug/boot/kernel/kernel.debug] It occurred to me that when I updated my test disk from FBSD 12 to 13 I had forgotten to run mergemaster. So I did so today. But I haven't been able = to reproduce the crash in 25 tries since then. I'm convinced that running mergemaster did not fix the crash, which is after all highly random. So I = will try some more tomorrow. I appreciate everybody's patience. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From nobody Sat Mar 4 02:22:23 2023 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 4PT7sD25LKz3wdch for ; Sat, 4 Mar 2023 02:22: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 4PT7sD14vmz4cTD for ; Sat, 4 Mar 2023 02:22:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1677896544; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4qvF01BoUytgLRmbeY6coWxVkybKk33elYnCgk4+t9c=; b=xqbIKzzzHAC+UgZrPagE9KuJxqfL8WzNDZ0w/KgfzPEqdj+1DaeMisP/UB/hPYxWz7jWfo Gm50rrptktxkol9Njeh7yeqX8lUSpWBFLOaY3UxdUYsHnEk142Q90MABlobPIA8+Odq8Fm H+1Lx3qPJRPQb+qb/GNiXKmOTt2Jm7qWc0R3Wp+nfbLmCiqvqwctdZJ/vsCHA0pVho2b0m YJpg8VJNuIgow9mdGK8kN1p1j8qa14sQ+ys6/4ZShGk1xKdfzIn+7hp2RCtQg9hlpSRe5B ZR7dkDOcOw+c7qJFfZFjBRsMazF1NmZVklCYpexE0f/53vYH792GA95eZtxFhw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677896544; a=rsa-sha256; cv=none; b=ULtScWaFefHEbqosrHLCulad0mr0+L8mqfM3OCCpS4DSR4GoTJg8vxghibwGgmgFrj6xpz InmdKp810vOeul+jpA8bIw4qeYir5ucb/4795XKM9tMfG3N9XHprraHd95Ou0/KS4L6zJs IHpHFO+1V6/PkPpvx41skT+zxVE3dEPnjBu7He2L916voGfy4zEH1q/DF2CtxvNmmVni9J iFKxUs9/Y20wAyRADnYk12sWdxOkmrdo22MpUpY5BQ7GycJO+6DBamJ+PGW1lcD5B10D7f T+MDQ5l75fYwpS6YZPkvNhjaJf9p8SQG4mEMKMhfVBU/91Ts0C0SFAPvPEbsgQ== 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 4PT7sC70BrzMY7 for ; Sat, 4 Mar 2023 02:22:23 +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 3242MN8a085065 for ; Sat, 4 Mar 2023 02:22:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3242MNoo085055 for fs@FreeBSD.org; Sat, 4 Mar 2023 02:22:23 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 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Sat, 04 Mar 2023 02:22:23 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? 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=3D267028 --- Comment #90 from Mark Millard --- (In reply to George Mitchell from comment #89) What vintage/version of *gdb was in use? (If it was gdb that complained.) Was it /usr/local/bin/*gdb ? /usr/libexec/*gdb ? Actually, for the backtrace activity, it is kgdb that is used, not gdb. Thus my use of "*gdb" notation. But a core.txt.* file in my context shows: GNU gdb (GDB) 12.1 [GDB v12.1 for FreeBSD] which would be for /usr/local/bin/*gdb ( not /usr/libexec/*gdb ). This is because I have: # pkg info gdb gdb-12.1_3 Name : gdb Version : 12.1_3 . . . installed. (I had to a livecore.* to have something to reference/illustrate with, having no example vmcore.* files around for a long time.) A significantly older gdb might indicate use of an old /usr/libexec/*gdb that had not been cleaned out. I'll note that I got no DWARF complaints from kgdb and: # llvm-dwarfdump -r 1 /usr/lib/debug/boot/kernel/kernel.debug | grep DWARF | head -1 0x00000000: Compile Unit: length =3D 0x000001d3, format =3D DWARF32, versio= n =3D 0x0004, abbr_offset =3D 0x0000, addr_size =3D 0x08 (next unit at 0x000001d7) indicates version =3D 0x0004 . This leads me to expect that you have an old gdb (kgdb) around that is in use. It sounds like you got a savecore into /var/crash/ . It should be possible to try investigating that without having to cause another crash, presuming the system is not updated (so that it matches the crash contents). For example, the same sort of command that crashinfo uses on the saved system-core file could be manually tried, possibly with a more modern kgdb vintage being used that would handle the more recent dwarf version. Attaching your core.txt.* file content might prove useful. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=