From nobody Sun May 07 18:44:13 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 4QDtcY3c1Gz49M13 for ; Sun, 7 May 2023 18:44:13 +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 4QDtcY11GDz4LWg for ; Sun, 7 May 2023 18:44:13 +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=1683485053; 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=FmaNuudrtO8HBea3ZlluOu3Qy96veJUjAqkcJkxBEvw=; b=deumSwzC624lc5ojifEWVaAGkh4pclUUzh6UDTIzZg0Q7fHlspjyVIgmqW7sShfnvO0Sfs oqDoshP3/B0McqynxSZRWTzHyFwZ/F3VgkmfopHXhJ2GX2BMRMEQdLLIEFcD5xzZSCVhvd 5h6OS7sDcsx4k8IfJCTI0vN5UWRCbT4+FiZqQY9Qd0OTRDa+SpxI/qDYhkXWsctz67UfW6 zfphdyTmUpq29cvguTRN3ugO36z+0M69E8CjBSlWooUlBdb68f61zQ51AgpPiCvqrtTQgI 2ljVzMpC84iV3+DHfv+WPbG5ESk28kkKCnWhUn23F5RADPDOVEByKFj5diWp3w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1683485053; a=rsa-sha256; cv=none; b=dstbk2/uYpYWp3nVEgCT+IDRd09/yhlFyUx3xrgXZdAicQFvRKcX2OS+WOosTm5Gu0A5l1 sGDp0f/iGc8mDV9lY+I8XYtrwI5u+Ux3QjCkOnoi7hP2cOVBDs3MmFtRpq13xLOumehWl6 8zcP6YcQbyYwFSBHmGljM1Xp4xx382l5HlgZiESCxkdSL2Zp/d6SU0xLy/RVqX4h+n9tWS iXqD1+/PIE2NqezdC0Ubvq+643xNtI3ea7/4IceZPP54dQi8WHC+VXA8+dAFiEbFURAAlT QuxpqnoWG4qXENZmJbp7NwviAkso1EziFZSbykuXlatrdJGcE0/GRkdMil1U4w== 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 4QDtcY06L9zTfw for ; Sun, 7 May 2023 18:44:13 +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 347IiCGT005374 for ; Sun, 7 May 2023 18:44:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 347IiCTg005373 for fs@FreeBSD.org; Sun, 7 May 2023 18:44:12 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 271292] kernel panic while dd'ing a USB disk to a ZFS directory Date: Sun, 07 May 2023 18:44:13 +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: CURRENT 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: 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=3D271292 --- Comment #6 from Mark Millard --- (In reply to Graham Perrin from comment #4) zpool get should report disabled vs. enabled vs. active. But I'll note that I referenced it because of it being a pool level issue, not just zfs, and one that also leads to incompatibility with older openzfs vintages. Even if it is just enabled, there is no way back to disabled, unless one has a zpool checkpoint that predates the zpool upgrade and can revert to the checkpoint. (snapshots need not be sufficient for pool feature problems.) However, this openzfs import also had other corruption generation problems not involving the block cloning feature misbehavior. If one has snapshots predating the corruptions that one can revert to being based on, these may allow avoiding those specific corruptions. But that will not deal with block cloning problems if some occured. --=20 You are receiving this mail because: You are the assignee for the bug.=