From owner-freebsd-fs@freebsd.org Sun Jan 24 17:00:50 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 703324D226E for ; Sun, 24 Jan 2021 17:00:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DNzlk2Z5Xz3nPx for ; Sun, 24 Jan 2021 17:00:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 581754D22EC; Sun, 24 Jan 2021 17:00:50 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 57E234D226D for ; Sun, 24 Jan 2021 17:00:50 +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 4DNzlk1yyXz3ncV for ; Sun, 24 Jan 2021 17:00:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 369E526F3C for ; Sun, 24 Jan 2021 17:00:50 +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 10OH0o1u004795 for ; Sun, 24 Jan 2021 17:00:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10OH0o5t004794 for fs@FreeBSD.org; Sun, 24 Jan 2021 17:00:50 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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Sun, 24 Jan 2021 17:00:50 +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: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: asomers@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2021 17:00:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 Alan Somers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asomers@FreeBSD.org, | |markj@FreeBSD.org Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Jan 24 21:00:32 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2886C4DA0A3 for ; Sun, 24 Jan 2021 21:00:32 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DP54H6qVwz4Zrn for ; Sun, 24 Jan 2021 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id DEADE4DA295; Sun, 24 Jan 2021 21:00:31 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DE4B04DA09E for ; Sun, 24 Jan 2021 21:00: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 4DP54H4S2hz4b6y for ; Sun, 24 Jan 2021 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 36E361F64 for ; Sun, 24 Jan 2021 21:00:31 +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 10OL0VTt029946 for ; Sun, 24 Jan 2021 21:00:31 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10OL0Vw9029934 for fs@FreeBSD.org; Sun, 24 Jan 2021 21:00:31 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202101242100.10OL0Vw9029934@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, 24 Jan 2021 21:00:31 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2021 21:00:32 -0000 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 ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS Open | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 235665 | panic: handle_written_inodeblock: live inodedep 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 | 244899 | [PATCH] zfs: xattr on a symlink target > 136 caus Open | 251035 | [zfs] Allow 64 bit ZFS to support 32 bit ioctls ( 12 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Jan 25 03:46:34 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 065964E6F03 for ; Mon, 25 Jan 2021 03:46:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DPG4n6bVSz518x for ; Mon, 25 Jan 2021 03:46:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id E0A484E6F02; Mon, 25 Jan 2021 03:46:33 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DF5624E708F for ; Mon, 25 Jan 2021 03:46:33 +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 4DPG4n5nvzz518w for ; Mon, 25 Jan 2021 03:46:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B5C00765E for ; Mon, 25 Jan 2021 03:46:33 +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 10P3kXw3044792 for ; Mon, 25 Jan 2021 03:46:33 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10P3kX3x044791 for fs@FreeBSD.org; Mon, 25 Jan 2021 03:46:33 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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Mon, 25 Jan 2021 03:46:34 +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: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2021 03:46:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |panic --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 25 20:21:56 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 96CC54F0C7C for ; Mon, 25 Jan 2021 20:21:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DPh9J3hVCz3Hx0 for ; Mon, 25 Jan 2021 20:21:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 7EA6B4F0BE2; Mon, 25 Jan 2021 20:21:56 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7E7024F0A39 for ; Mon, 25 Jan 2021 20:21: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 4DPh9J33hwz3J0J for ; Mon, 25 Jan 2021 20:21:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5C4BA1CD05 for ; Mon, 25 Jan 2021 20:21: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 10PKLuhi091443 for ; Mon, 25 Jan 2021 20:21:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10PKLuDk091442 for fs@FreeBSD.org; Mon, 25 Jan 2021 20:21: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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Mon, 25 Jan 2021 20:21:56 +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: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2021 20:21:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #1 from Mark Johnston --- This looks like a bug in zfs_crypto_dispatch() which is only tickled when cryptop dispatch is asynchronous (i.e., a hardware driver is handling the request): it needs to set session->fs_done =3D false earlier. More generally the code is assuming that only one thread is dispatching cry= pto requests for a given freebsd_session_t. From my reading of the code this i= sn't obviously true: zio_do_crypt_data() uses key->zk_session but there doesn't appear to be any mutual exclusion. Again this is only a problem with hw crypto. I think it should be sufficient to make fs_done truly thread local. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 25 22:56:21 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AF6314F52DA for ; Mon, 25 Jan 2021 22:56:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DPlbT4PJXz3nC7 for ; Mon, 25 Jan 2021 22:56:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 96E5D4F5715; Mon, 25 Jan 2021 22:56:21 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 96ABF4F53E8 for ; Mon, 25 Jan 2021 22:56: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 4DPlbT3pmzz3nC6 for ; Mon, 25 Jan 2021 22:56:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 719D51EC73 for ; Mon, 25 Jan 2021 22:56: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 10PMuLjb065092 for ; Mon, 25 Jan 2021 22:56:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10PMuLT5065091 for fs@FreeBSD.org; Mon, 25 Jan 2021 22:56: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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Mon, 25 Jan 2021 22:56: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: CURRENT X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2021 22:56:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 --- Comment #2 from Mark Johnston --- (In reply to Mark Johnston from comment #1) With this fixed I hit the same panic as in the PR title. QAT has some weird constraints around the AAD length for GCM/CCM; in particular, it must be no more than 240 bytes in length. This is implemented in the Intel and DPDK Q= AT drivers as well as ours. ZFS is submitting GCM encryption requests with a large AAD (I think when encrypting a block of dnodes?) and hitting the check in qat_process(), and = it can't tolerate the error. Weirdly, the ZFS QAT stub for Linux has no check= for this case, but it also only uses QAT for data blocks, which I believe have = no AAD. See qat_crypt_use_accel(). So for now we should at least change ZFS to not use hardware crypto since it doesn't work and clearly hasn't been tested (see comment 1). I'm not sure = how hard it would be to permit the use of hardware crypto only for data blocks = (and not for the ZIL and dnode blocks, which requires support for large AAD buff= ers. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 25 23:04:05 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 112694F5962 for ; Mon, 25 Jan 2021 23:04:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DPlmN6wY5z3nkn for ; Mon, 25 Jan 2021 23:04:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id EB6D74F5C08; Mon, 25 Jan 2021 23:04:04 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EB3814F5961 for ; Mon, 25 Jan 2021 23:04:04 +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 4DPlmN6Gvhz3p1g for ; Mon, 25 Jan 2021 23:04:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CAC0A1ECB7 for ; Mon, 25 Jan 2021 23:04:04 +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 10PN44pQ068474 for ; Mon, 25 Jan 2021 23:04:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10PN44jQ068473 for fs@FreeBSD.org; Mon, 25 Jan 2021 23:04:04 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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Mon, 25 Jan 2021 23:04:05 +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: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: asomers@FreeBSD.org 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2021 23:04:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 --- Comment #3 from Alan Somers --- Sounds like qat should refuse to service any consumers that use AAD. Other consumers can use AAD too. I think geli with data integrity verification d= oes, for example. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Jan 25 23:21:42 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A617B4F623E for ; Mon, 25 Jan 2021 23:21:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DPm8k47tLz3pml for ; Mon, 25 Jan 2021 23:21:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8E1DF4F6520; Mon, 25 Jan 2021 23:21:42 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8DE3A4F6327 for ; Mon, 25 Jan 2021 23:21:42 +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 4DPm8k3Yfcz3q18 for ; Mon, 25 Jan 2021 23:21:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 6D8A01F381 for ; Mon, 25 Jan 2021 23:21:42 +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 10PNLgnH074700 for ; Mon, 25 Jan 2021 23:21:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10PNLgD0074699 for fs@FreeBSD.org; Mon, 25 Jan 2021 23:21:42 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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Mon, 25 Jan 2021 23:21:42 +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: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: asomers@FreeBSD.org 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2021 23:21:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 --- Comment #4 from Alan Somers --- Hm, apparently I don't understand the problem with AAD. Because geli with = QAT works fine when I create a device like this: sudo geli onetime -a HMAC/SHA256 -e aes-cbc -l 256 -s 4096 md0 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Jan 26 00:03:47 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BDA854F71EE for ; Tue, 26 Jan 2021 00:03:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DPn5H4r82z3t2D for ; Tue, 26 Jan 2021 00:03:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id A602D4F71ED; Tue, 26 Jan 2021 00:03:47 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A5CC34F76B3 for ; Tue, 26 Jan 2021 00:03: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 4DPn5H4GdLz3tJn for ; Tue, 26 Jan 2021 00:03:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 85C5D1FB86 for ; Tue, 26 Jan 2021 00:03: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 10Q03l20094999 for ; Tue, 26 Jan 2021 00:03:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10Q03ln5094998 for fs@FreeBSD.org; Tue, 26 Jan 2021 00:03: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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Tue, 26 Jan 2021 00:03:47 +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: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2021 00:03:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 --- Comment #5 from Mark Johnston --- (In reply to Alan Somers from comment #3) This constraint only applies to AES-GCM. Other algorithms that provide integrity checking don't have such a limit on the AAD size. IPSec's ESP protocol includes the ESP header itself as AAD, for instance, b= ut because the AAD size is fixed and smaller than the limit, it can use QAT/AES-GCM with no problems. That use-case was the original motivation for the port. (In reply to Alan Somers from comment #4) GELI doesn't appear to authenticate anything that isn't also encrypted, so there is no AAD. Even if it were to use GCM there would be no problem. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Jan 26 00:08:13 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A480E4F7866 for ; Tue, 26 Jan 2021 00:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DPnBP45Kmz3tR1 for ; Tue, 26 Jan 2021 00:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8C6204F7A70; Tue, 26 Jan 2021 00:08:13 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8C2AC4F7AEC for ; Tue, 26 Jan 2021 00:08: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 4DPnBP3RmTz3tc9 for ; Tue, 26 Jan 2021 00:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 693BE1FB28 for ; Tue, 26 Jan 2021 00:08: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 10Q08DPN095622 for ; Tue, 26 Jan 2021 00:08:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10Q08DIL095621 for fs@FreeBSD.org; Tue, 26 Jan 2021 00:08:13 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 252981] panic with ZFS encryption and QAT: VERIFY3(0 == spa_do_crypt_bad(... Date: Tue, 26 Jan 2021 00:08: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: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2021 00:08:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252981 --- Comment #6 from Mark Johnston --- A better solution than disabling the use of hardware crypto in ZFS could be= to extend opencrypto to optionally fall back to a software implementation if t= he request doesn't satisfy some constraints. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Jan 26 10:04:48 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B7E554E7F2F for ; Tue, 26 Jan 2021 10:04:48 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (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 "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQ2Ql3qfjz3KGm for ; Tue, 26 Jan 2021 10:04:47 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 54E242383F7 for ; Tue, 26 Jan 2021 10:04:42 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=uk1; t=1611655482; bh=PUZ1l+dgZt03Ceakn0ZS8xd+HFtzJ2zndS+3tR0EnEk=; h=From:To:Subject:Date; b=LskzuS+oKJ+d/bntL/GDs91R1DejGQru9OSyDgh9NhzWnxjwZcyP/JSL1yZ1ycgPT eRsQbHS1orDBxtpVAZG08jhh6Splun/TKYBd2AXPZjyOlHhVlf3Gg0LZUvfUmYSNg8 yHI3/g9R2IIMacnCBFhH0LpbuRGOUmNpfn8B/mnc= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 26 Jan 2021 10:04:41 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 26 Jan 2021 10:04:41 +0000 From: Matt Churchyard To: "freebsd-fs@freebsd.org" Subject: ashift = 0, can't run zdb on 13-current Thread-Topic: ashift = 0, can't run zdb on 13-current Thread-Index: Adbzyqf36R8BcOV+SzSaiDZv/uU9TA== Date: Tue, 26 Jan 2021 10:04:40 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 X-Rspamd-Queue-Id: 4DQ2Ql3qfjz3KGm X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=userve.net header.s=uk1 header.b=LskzuS+o; dmarc=none; spf=pass (mx1.freebsd.org: domain of matt.churchyard@userve.net designates 217.196.1.22 as permitted sender) smtp.mailfrom=matt.churchyard@userve.net X-Spamd-Result: default: False [-3.50 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.196.1.22:from]; R_DKIM_ALLOW(-0.20)[userve.net:s=uk1]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.196.1.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[userve.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[217.196.1.22:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[userve.net:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20652, ipnet:217.196.0.0/20, country:GB]; MAILMAN_DEST(0.00)[freebsd-fs] X-Mailman-Approved-At: Tue, 26 Jan 2021 11:14:17 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2021 10:04:48 -0000 Hello, I'm currently testing out encryption (using a recent snapshot of 13-CURRENT= ) on a backup system that will eventually go offsite once 13 is released. I have created a pool just using default options but zpool output lists the= ashift as 0: root@:/etc/ssh # uname -a FreeBSD 13.0-CURRENT FreeBSD 13.0-CURRENT #0 main-c255641-gf2b794e1e90: Th= u Jan 7 06:25:26 UTC 2021 root@releng1.nyi.freebsd.org:/usr/obj/usr/sr= c/amd64.amd64/sys/GENERIC amd64 root@:/etc/ssh # zpool get ashift offsite NAME PROPERTY VALUE SOURCE offsite ashift 0 default I'm sure it can't actually be 0. I've seen mentions online that this is a p= roblem, but also that it just means "auto" ashift. Either way it's unnervin= g. I wanted to check with zdb, but this doesn't seem to run at all as I can= find no cache file on the system and passing a pool name just gives "No su= ch file or directory" Is there any way I can run zdb on this system? Regards, Matt From owner-freebsd-fs@freebsd.org Wed Jan 27 13:11:57 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E4B674F8F95 for ; Wed, 27 Jan 2021 13:11:57 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (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 "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQkXD5zmKz4V6j for ; Wed, 27 Jan 2021 13:11:56 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id C99F42384DB for ; Wed, 27 Jan 2021 13:11:54 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=uk1; t=1611753114; bh=0XWZfUsqlu+K9xK8fNNlntFvOfbrTFp5yuUVxm/d4k8=; h=From:To:Subject:Date:References:In-Reply-To; b=oPh5vk4+MGzXqghAUtzkhSbYBtnX/dkZfEhk03bevLW+SdB4RVep390kNsc9S1Fas CD7FeR8nKupQcaJ62mc6uOfYIBpQuxGYmsSeZ/Dc3R2tBAOa6/K8Gm2vOu+CBel5hF Yfcjl4XXBFgozrMA04vZVB715zUn6Bp0ucGMBtf8= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 27 Jan 2021 13:11:54 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Wed, 27 Jan 2021 13:11:53 +0000 From: Matt Churchyard To: "freebsd-fs@freebsd.org" Subject: ZFS issues on 13-current snapshot Thread-Topic: ZFS issues on 13-current snapshot Thread-Index: Adb0kYPUY0NlcoqCRkqDCQZIgZuN1gAHDd6w Date: Wed, 27 Jan 2021 13:11:52 +0000 Message-ID: References: <283b2b0b5df34c4f9b8c78b078a67381@SERVER.ad.usd-group.com> In-Reply-To: <283b2b0b5df34c4f9b8c78b078a67381@SERVER.ad.usd-group.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 X-Rspamd-Queue-Id: 4DQkXD5zmKz4V6j X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=userve.net header.s=uk1 header.b=oPh5vk4+; dmarc=none; spf=pass (mx1.freebsd.org: domain of matt.churchyard@userve.net designates 217.196.1.22 as permitted sender) smtp.mailfrom=matt.churchyard@userve.net X-Spamd-Result: default: False [-3.50 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.196.1.22:from]; R_DKIM_ALLOW(-0.20)[userve.net:s=uk1]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.196.1.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[userve.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[217.196.1.22:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[userve.net:+]; NEURAL_HAM_SHORT(-1.00)[-0.996]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20652, ipnet:217.196.0.0/20, country:GB]; MAILMAN_DEST(0.00)[freebsd-fs] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 13:11:58 -0000 Hello, (Note: sorry moderators, this is a duplicate of an earlier email apparently= held in review as my outbound address isn't the same as the one I original= ly signed up with) I'm testing a 13-current machine for future use as an encrypted offsite bac= kup store. As it's near release I was kind of hoping to get away with using= this 13 snapshot for a few months then switch to a RELEASE bootenv when it= comes out. However, I seem to be having a few issues. First of all I stated noticing that the USED & REFER columns weren't equal = for individual datasets. This system so far has simply received a single sn= apshot of a few datasets, and had readonly set immediately after. Some of t= hem are showing several hundred MB linked to snapshots on datasets that hav= en't been touched. I'm unable to send further snapshots without forcing a r= ollback first. Not the end of the world but this isn't right and has never = happened on previous ZFS systems. The most I've seen is a few KB because I = forgot to set readonly and went into a few directories on a dataset with at= ime=3Don. offsite 446G 6.36T 140K /offsite [...] offsite/secure/cms 359M 6.3= 6T 341M /offsite/secure/cms offsite/secure/cms@26-01-2021 17.6M = - 341M - offsite/secure/company 225G 6.3= 6T 224G /offsite/secure/company offsite/secure/company@25-01-2021 673M = - 224G - offsite/secure is an encrypted dataset using default options. zfs diff will sit for a while (on small datasets - I gave up trying to run = it on anything over a few GB) and eventually output nothing. root@offsite:/etc # uname -a FreeBSD offsite.backup 13.0-CURRENT FreeBSD 13.0-CURRENT #0 main-c255641-gf= 2b794e1e90: Thu Jan 7 06:25:26 UTC 2021 root@releng1.nyi.freebsd.org:/= usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 root@offsite:/etc # zpool version zfs-0.8.0-1 zfs-kmod-0.8.0-1 I then thought I would run a scrub just to see if it found any obvious prob= lems. It started off running fine, estimating about 45-60 minutes for the whole p= rocess of scanning 446GB. (This is 4 basic SATA Ironwolf 4TB disks in raidz= 2) However it appeared to stall at 19.7%. Eventually it hit 19.71, and does ap= pear to be going up, but at this point looks like it may take a days to com= plete (currently says 3 hours but it's skewed by the initial fast progress = and going up every time I check). Gstat shows the disks at 100% doing anywhere between 10-50MB/s. (They were = hitting anywhere up to 170MB/s to start off with. Obviously this varies whe= n having to seek, but even at the rates currently seen I suspect it should = be progressing faster than zpool output shows) root@offsite:/etc # zpool status pool: offsite state: ONLINE scan: scrub in progress since Wed Jan 27 09:29:50 2021 555G scanned at 201M/s, 182G issued at 65.8M/s, 921G total 0B repaired, 19.71% done, 03:11:51 to go config: NAME STATE READ WRITE CKSUM offsite ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gpt/data-ZGY85VKX ONLINE 0 0 0 gpt/data-ZGY88MRY ONLINE 0 0 0 gpt/data-ZGY88NZJ ONLINE 0 0 0 gpt/data-ZGY88QKF ONLINE 0 0 0 errors: No known data errors Update: I've probably spent 30+ minutes writing this email and it's reporti= ng a few more GB read but not a single digit in progress percent. scan: scrub in progress since Wed Jan 27 09:29:50 2021 559G scanned at 142M/s, 182G issued at 46.2M/s, 921G total 0B repaired, 19.71% done, 04:33:08 to go It doesn't inspire a lot of confidence. ZFS had become pretty rock solid in= FreeBSD in recent years and I have many systems running it. This should ha= ve the most efficient scrub code to date and yet is currently taking about = an hour to progress 0.01% on a new system with a fraction of the data it wi= ll hold and 0% fragmentation. As it stands at the moment, I will likely scrap this attempt and retry with= FreeBSD 12. Regards, Matt Churchyard From owner-freebsd-fs@freebsd.org Wed Jan 27 18:15:38 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AE974525259 for ; Wed, 27 Jan 2021 18:15:38 +0000 (UTC) (envelope-from stevenschlansker@gmail.com) Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQsGd5Kxzz4r8C for ; Wed, 27 Jan 2021 18:15:37 +0000 (UTC) (envelope-from stevenschlansker@gmail.com) Received: by mail-io1-xd34.google.com with SMTP id y19so2850831iov.2 for ; Wed, 27 Jan 2021 10:15:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=AVLbdv6Q/tlFqKEWoDW2zRDxO04tRPHGjw5ZapdNiZ0=; b=t2BIyFY3g32XqbueJC3pGMI90yhp3TYgBJtDETtHKMbOmKGYFNh3ER7hPw11xXf5nO DYYkAESIWOU42N+B9ruGCcpAKBBCkHlx3F0EFvDcJYc0f23Q4gMNZcKdLlo1i18KZBDI 5b9zXKZG/WIZHiRGJJcaY4bMZ7CQkHBoasoXh5O2KOZD+V/pkr5sr9kkW38ZaSmVm4ql +VURJLnEPqH/g1s/aBvWbe/fTpvna6qBgW2TSC8f/aUPS4ATEDoQxH9zaB6rt0kmWf8o 0KGudyvUakL5YjFR5hS0Hu/wkCbU4UHlbSLvW4Zu8VHPS9t/NZ0O749wYEteOWnknOwW 0+VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=AVLbdv6Q/tlFqKEWoDW2zRDxO04tRPHGjw5ZapdNiZ0=; b=VE1QhdzW+4y7vofK4oQG5FbNSm9dkos1gPZXuwC1PUPCLzQEtSMovzP3B7q4Pptlml HM/SpuTk4m+izUcF290PWSqVp9FcTveJURKnyhLtc9lQ6V65kOoxKA9BZtArHJcPu3W9 V/rYdcBAPkS8SFkwuJvpo7T8h2M8SUK+Aci1q5oo82AGOX/v0HuJS1M1c9ZzN0Jt5/ZT EVrWjrSCJinr/SJ+dp4yxIfgTDMiF/NAZufPL+p7snpfNRZOalIiN2z+JbhiNRryibPy A0I1Sx9jhhdh5f3a/PEga9vKBg4Rv6xkdl1AhdeDWwr3aOjbxQUOUgSZ5djVXZUkPThd s4xg== X-Gm-Message-State: AOAM531ZSTFwmQ9t5hQTxbGHzY0eFstBGWY65PDR0BuUYyGPdkOhYfU1 zJad8KKd/w8L8zd6HCRCjipjVvOu9KO76yPiiVAQ6MFAzEE= X-Google-Smtp-Source: ABdhPJzSHbDIVvOJvpPhkw9fFaVZUbBhCz3Pxuwm4jMAapbF2cz8/1M5u1yxstgKOUKIN94nxMgo7dQBH930KrqA3nE= X-Received: by 2002:a6b:6a0e:: with SMTP id x14mr8370281iog.57.1611771336179; Wed, 27 Jan 2021 10:15:36 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Steven Schlansker Date: Wed, 27 Jan 2021 10:15:24 -0800 Message-ID: Subject: Re: persistent integer divide fault panic in zfs_rmnode To: freebsd-fs@freebsd.org X-Rspamd-Queue-Id: 4DQsGd5Kxzz4r8C X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=t2BIyFY3; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of stevenschlansker@gmail.com designates 2607:f8b0:4864:20::d34 as permitted sender) smtp.mailfrom=stevenschlansker@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::d34:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::d34:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d34:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 18:15:38 -0000 Does anybody have any suggestions as to what I can try next regarding this panic? At this point the only path forward I see is to declare the zpool corrupt and attempt to move all the data off, destroy, and migrate back, and hope the recreated pool does not tickle this bug. That would be a pretty disappointing end to a long fatal-problem-free run with ZFS. Thanks, Steven On Fri, Jan 8, 2021 at 3:41 PM Steven Schlansker wrote: > Hi freebsd-fs, > > I have a 8-way raidz2 system running FreeBSD 12.2-RELEASE-p1 GENERIC > Approximately since upgrading to FreeBSD 12.2-RELEASE, I receive a nasty > panic when trying to unlink any of a large number of files. > > Fatal trap 18: integer divide fault while in kernel mode > > > The pool reports as healthy: > > pool: universe > state: ONLINE > status: One or more devices are configured to use a non-native block size. > Expect reduced performance. > action: Replace affected devices with devices that support the > configured block size, or migrate data to a properly configured > pool. > scan: resilvered 416M in 0 days 00:08:35 with 0 errors on Thu Jan 7 > 02:16:03 2021 > When some files are unlinked, the system panics with a partial backtrace > of: > > #6 0xffffffff82a148ce at zfs_rmnode+0x5e > #7 0xffffffff82a35612 at zfs_freebsd_reclaim+0x42 > #8 0xffffffff812482db at VOP_RECLAIM_APV+0x7b > #9 0xffffffff80c8e376 at vgonel+0x216 > #10 0xffffffff80c8e9c5 at vrecycle+0x45 > > I captured a dump, and using kgdb extracted a full backtrace, and filed it > as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250784 > > #8 0xffffffff82963725 in get_next_chunk (dn=0xfffff804325045c0, > start=, minimum=0, l1blks=) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:721 > warning: Source file is more recent than executable. > 721 (roundup(*start, iblkrange) - (minimum / iblkrange * > iblkrange)) / > (kgdb) list > 716 * L1 blocks in this range have data. If we can, we use > this > 717 * worst case value as an estimate so we can avoid having > to look > 718 * at the object's actual data. > 719 */ > 720 uint64_t total_l1blks = > 721 (roundup(*start, iblkrange) - (minimum / iblkrange * > iblkrange)) / > 722 iblkrange; > 723 if (total_l1blks <= maxblks) { > 724 *l1blks = total_l1blks; > 725 *start = minimum; > (kgdb) print iblkrange > $1 = 0 > (kgdb) print minimum > $2 = 0 > > It looks like it is attempting to compute 0 / 0, causing the panic. > > How can I restore my zpool to a working state? Thank you for any > assistance. > From owner-freebsd-fs@freebsd.org Wed Jan 27 21:00:02 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 73B534E9F84 for ; Wed, 27 Jan 2021 21:00:02 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQwwK3mv2z3NQS for ; Wed, 27 Jan 2021 21:00:01 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 301BE40023 for ; Wed, 27 Jan 2021 21:59:59 +0100 (CET) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 103D04000B; Wed, 27 Jan 2021 21:59:58 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on bernadotte.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.4.2 X-Spam-Score: -1.0 Received: from [IPv6:2001:9b1:28ff:3b01:40a9:34ae:a67c:6e52] (unknown [IPv6:2001:9b1:28ff:3b01:40a9:34ae:a67c:6e52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id 74FA640003; Wed, 27 Jan 2021 21:59:52 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: persistent integer divide fault panic in zfs_rmnode From: Peter Eriksson In-Reply-To: Date: Wed, 27 Jan 2021 21:59:38 +0100 Cc: FreeBSD FS Content-Transfer-Encoding: quoted-printable Message-Id: <7B373FB5-E907-4880-A24E-DE9F2A173A49@lysator.liu.se> References: To: Steven Schlansker X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 4DQwwK3mv2z3NQS X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=liu.se; spf=pass (mx1.freebsd.org: domain of pen@lysator.liu.se designates 130.236.254.3 as permitted sender) smtp.mailfrom=pen@lysator.liu.se X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:mail.lysator.liu.se]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[130.236.254.3:from]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[liu.se,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2843, ipnet:130.236.0.0/16, country:SE]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 21:00:02 -0000 Have you tried with the OpenZFS port instead in case the problem is = solved there? (Might be easiest to just boot a FreeBSD 13 kernel with your existing = 12.2 user land) - Peter > On 27 Jan 2021, at 19:15, Steven Schlansker = wrote: >=20 > Does anybody have any suggestions as to what I can try next regarding = this > panic? >=20 > At this point the only path forward I see is to declare the zpool = corrupt > and attempt to > move all the data off, destroy, and migrate back, and hope the = recreated > pool does not tickle this bug. >=20 > That would be a pretty disappointing end to a long fatal-problem-free = run > with ZFS. >=20 > Thanks, > Steven >=20 > On Fri, Jan 8, 2021 at 3:41 PM Steven Schlansker = > wrote: >=20 >> Hi freebsd-fs, >>=20 >> I have a 8-way raidz2 system running FreeBSD 12.2-RELEASE-p1 GENERIC >> Approximately since upgrading to FreeBSD 12.2-RELEASE, I receive a = nasty >> panic when trying to unlink any of a large number of files. >>=20 >> Fatal trap 18: integer divide fault while in kernel mode >>=20 >>=20 >> The pool reports as healthy: >>=20 >> pool: universe >> state: ONLINE >> status: One or more devices are configured to use a non-native block = size. >> Expect reduced performance. >> action: Replace affected devices with devices that support the >> configured block size, or migrate data to a properly = configured >> pool. >> scan: resilvered 416M in 0 days 00:08:35 with 0 errors on Thu Jan 7 >> 02:16:03 2021 >> When some files are unlinked, the system panics with a partial = backtrace >> of: >>=20 >> #6 0xffffffff82a148ce at zfs_rmnode+0x5e >> #7 0xffffffff82a35612 at zfs_freebsd_reclaim+0x42 >> #8 0xffffffff812482db at VOP_RECLAIM_APV+0x7b >> #9 0xffffffff80c8e376 at vgonel+0x216 >> #10 0xffffffff80c8e9c5 at vrecycle+0x45 >>=20 >> I captured a dump, and using kgdb extracted a full backtrace, and = filed it >> as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250784 >>=20 >> #8 0xffffffff82963725 in get_next_chunk (dn=3D0xfffff804325045c0, >> start=3D, minimum=3D0, l1blks=3D) >> at = /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:721 >> warning: Source file is more recent than executable. >> 721 (roundup(*start, iblkrange) - (minimum / = iblkrange * >> iblkrange)) / >> (kgdb) list >> 716 * L1 blocks in this range have data. If we can, we = use >> this >> 717 * worst case value as an estimate so we can avoid = having >> to look >> 718 * at the object's actual data. >> 719 */ >> 720 uint64_t total_l1blks =3D >> 721 (roundup(*start, iblkrange) - (minimum / = iblkrange * >> iblkrange)) / >> 722 iblkrange; >> 723 if (total_l1blks <=3D maxblks) { >> 724 *l1blks =3D total_l1blks; >> 725 *start =3D minimum; >> (kgdb) print iblkrange >> $1 =3D 0 >> (kgdb) print minimum >> $2 =3D 0 >>=20 >> It looks like it is attempting to compute 0 / 0, causing the panic. >>=20 >> How can I restore my zpool to a working state? Thank you for any >> assistance. >>=20 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Wed Jan 27 21:00:10 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 837C04EA084 for ; Wed, 27 Jan 2021 21:00:10 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from ste-pvt-msa1.bahnhof.se (ste-pvt-msa1.bahnhof.se [213.80.101.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQwwT3d56z3NYd for ; Wed, 27 Jan 2021 21:00:09 +0000 (UTC) (envelope-from pen@lysator.liu.se) Received: from localhost (localhost [127.0.0.1]) by ste-pvt-msa1.bahnhof.se (Postfix) with ESMTP id 758743F700; Wed, 27 Jan 2021 22:00:06 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at bahnhof.se X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=6.31 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no Received: from ste-pvt-msa1.bahnhof.se ([127.0.0.1]) by localhost (ste-pvt-msa1.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCS8f2kJIyr0; Wed, 27 Jan 2021 22:00:05 +0100 (CET) Received: by ste-pvt-msa1.bahnhof.se (Postfix) with ESMTPA id 7FB663F515; Wed, 27 Jan 2021 22:00:05 +0100 (CET) Received: from [192.168.1.132] ([192.168.1.132]) (authenticated bits=0) by hope.grebo.net (8.16.1/8.16.1) with ESMTPSA id 10RKxw7I040178 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 27 Jan 2021 21:59:58 +0100 (CET) (envelope-from pen@lysator.liu.se) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: persistent integer divide fault panic in zfs_rmnode From: Peter Eriksson In-Reply-To: Date: Wed, 27 Jan 2021 21:59:57 +0100 Cc: FreeBSD FS Content-Transfer-Encoding: quoted-printable Message-Id: <5B326DD1-58E1-4D99-9745-EB3197FC3FE1@lysator.liu.se> References: To: Steven Schlansker X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (hope.grebo.net [10.0.0.3]); Wed, 27 Jan 2021 21:59:58 +0100 (CET) X-Rspamd-Queue-Id: 4DQwwT3d56z3NYd X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=liu.se (policy=none); spf=neutral (mx1.freebsd.org: 213.80.101.70 is neither permitted nor denied by domain of pen@lysator.liu.se) smtp.mailfrom=pen@lysator.liu.se X-Spamd-Result: default: False [-2.60 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_NEUTRAL(0.00)[?all:c]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RBL_DBL_DONT_QUERY_IPS(0.00)[213.80.101.70:from]; SPAMHAUS_ZRD(0.00)[213.80.101.70:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_LOW(-0.10)[213.80.101.70:from]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8473, ipnet:213.80.96.0/19, country:SE]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs]; DMARC_POLICY_SOFTFAIL(0.10)[liu.se : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 21:00:10 -0000 Have you tried with the OpenZFS port instead in case the problem is = solved there? (Might be easiest to just boot a FreeBSD 13 kernel with your existing = 12.2 user land) - Peter > On 27 Jan 2021, at 19:15, Steven Schlansker = wrote: >=20 > Does anybody have any suggestions as to what I can try next regarding = this > panic? >=20 > At this point the only path forward I see is to declare the zpool = corrupt > and attempt to > move all the data off, destroy, and migrate back, and hope the = recreated > pool does not tickle this bug. >=20 > That would be a pretty disappointing end to a long fatal-problem-free = run > with ZFS. >=20 > Thanks, > Steven >=20 > On Fri, Jan 8, 2021 at 3:41 PM Steven Schlansker = > wrote: >=20 >> Hi freebsd-fs, >>=20 >> I have a 8-way raidz2 system running FreeBSD 12.2-RELEASE-p1 GENERIC >> Approximately since upgrading to FreeBSD 12.2-RELEASE, I receive a = nasty >> panic when trying to unlink any of a large number of files. >>=20 >> Fatal trap 18: integer divide fault while in kernel mode >>=20 >>=20 >> The pool reports as healthy: >>=20 >> pool: universe >> state: ONLINE >> status: One or more devices are configured to use a non-native block = size. >> Expect reduced performance. >> action: Replace affected devices with devices that support the >> configured block size, or migrate data to a properly configured >> pool. >> scan: resilvered 416M in 0 days 00:08:35 with 0 errors on Thu Jan 7 >> 02:16:03 2021 >> When some files are unlinked, the system panics with a partial = backtrace >> of: >>=20 >> #6 0xffffffff82a148ce at zfs_rmnode+0x5e >> #7 0xffffffff82a35612 at zfs_freebsd_reclaim+0x42 >> #8 0xffffffff812482db at VOP_RECLAIM_APV+0x7b >> #9 0xffffffff80c8e376 at vgonel+0x216 >> #10 0xffffffff80c8e9c5 at vrecycle+0x45 >>=20 >> I captured a dump, and using kgdb extracted a full backtrace, and = filed it >> as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250784 >>=20 >> #8 0xffffffff82963725 in get_next_chunk (dn=3D0xfffff804325045c0, >> start=3D, minimum=3D0, l1blks=3D) >> at = /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:721 >> warning: Source file is more recent than executable. >> 721 (roundup(*start, iblkrange) - (minimum / = iblkrange * >> iblkrange)) / >> (kgdb) list >> 716 * L1 blocks in this range have data. If we can, we = use >> this >> 717 * worst case value as an estimate so we can avoid = having >> to look >> 718 * at the object's actual data. >> 719 */ >> 720 uint64_t total_l1blks =3D >> 721 (roundup(*start, iblkrange) - (minimum / = iblkrange * >> iblkrange)) / >> 722 iblkrange; >> 723 if (total_l1blks <=3D maxblks) { >> 724 *l1blks =3D total_l1blks; >> 725 *start =3D minimum; >> (kgdb) print iblkrange >> $1 =3D 0 >> (kgdb) print minimum >> $2 =3D 0 >>=20 >> It looks like it is attempting to compute 0 / 0, causing the panic. >>=20 >> How can I restore my zpool to a working state? Thank you for any >> assistance. >>=20 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Wed Jan 27 23:23:24 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A73854ED208 for ; Wed, 27 Jan 2021 23:23:24 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (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 "anubis.delphij.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DR05l6tw1z3m6m for ; Wed, 27 Jan 2021 23:23:23 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from odin.corp.delphij.net (unknown [IPv6:2601:646:8601:f4a:a5f2:21a8:faf2:8198]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id A0AEB374E2; Wed, 27 Jan 2021 15:23:17 -0800 (PST) Reply-To: d@delphij.net Subject: Re: persistent integer divide fault panic in zfs_rmnode To: Steven Schlansker , freebsd-fs@freebsd.org References: From: Xin Li Message-ID: <560ca3ae-82ca-d3f7-ad15-690d74e0a885@delphij.net> Date: Wed, 27 Jan 2021 15:23:16 -0800 User-Agent: Thunderbird MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wsbw9hmkTNwxa3Ff6gqzYMRZHE8zGBIsv" X-Rspamd-Queue-Id: 4DR05l6tw1z3m6m X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.97 / 15.00]; HAS_REPLYTO(0.00)[d@delphij.net]; RCVD_VIA_SMTP_AUTH(0.00)[]; XM_UA_NO_VERSION(0.01)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; HAS_ATTACHMENT(0.00)[]; MIME_BASE64_TEXT_BOGUS(1.00)[]; DKIM_TRACE(0.00)[delphij.net:+]; MIME_BASE64_TEXT(0.10)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.98)[-0.981]; DMARC_POLICY_ALLOW(-0.50)[delphij.net,reject]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:+,4:+,5:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:1:117::25:from]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[delphij.net:s=m7e2]; FREEFALL_USER(0.00)[delphij]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; REPLYTO_DOM_EQ_FROM_DOM(0.00)[]; SPAMHAUS_ZRD(0.00)[2001:470:1:117::25:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 23:23:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wsbw9hmkTNwxa3Ff6gqzYMRZHE8zGBIsv Content-Type: multipart/mixed; boundary="XneqEwXk1LWTeK4jeMQaX0baW6tMGMjaJ"; protected-headers="v1" From: Xin Li Reply-To: d@delphij.net To: Steven Schlansker , freebsd-fs@freebsd.org Message-ID: <560ca3ae-82ca-d3f7-ad15-690d74e0a885@delphij.net> Subject: Re: persistent integer divide fault panic in zfs_rmnode References: In-Reply-To: --XneqEwXk1LWTeK4jeMQaX0baW6tMGMjaJ Content-Type: multipart/mixed; boundary="------------FE979ADD05CA9275BD1DEAB1" Content-Language: en-US This is a multi-part message in MIME format. --------------FE979ADD05CA9275BD1DEAB1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 1/27/21 10:15, Steven Schlansker wrote: > Does anybody have any suggestions as to what I can try next regarding t= his > panic? >=20 > At this point the only path forward I see is to declare the zpool corru= pt > and attempt to > move all the data off, destroy, and migrate back, and hope the recreate= d > pool does not tickle this bug. >=20 > That would be a pretty disappointing end to a long fatal-problem-free r= un > with ZFS. Could you please try the attached patch? (Full context: https://github.com/openzfs/zfs/issues/8778 ) Cheers, --------------FE979ADD05CA9275BD1DEAB1 Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0"; name="580256045b2970778e7543f1c00faa7ac25d3f98.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="580256045b2970778e7543f1c00faa7ac25d3f98.patch" ZGlmZiAtLWdpdCBhL3N5cy9jZGRsL2NvbnRyaWIvb3BlbnNvbGFyaXMvdXRzL2NvbW1vbi9m cy96ZnMvZG11LmMgYi9zeXMvY2RkbC9jb250cmliL29wZW5zb2xhcmlzL3V0cy9jb21tb24v ZnMvemZzL2RtdS5jCmluZGV4IDQ1YWM0Yjc5NmZkLi5iNmE0OTVkMDE3MiAxMDA2NDQKLS0t IGEvc3lzL2NkZGwvY29udHJpYi9vcGVuc29sYXJpcy91dHMvY29tbW9uL2ZzL3pmcy9kbXUu YworKysgYi9zeXMvY2RkbC9jb250cmliL29wZW5zb2xhcmlzL3V0cy9jb21tb24vZnMvemZz L2RtdS5jCkBAIC03MDYsOCArNzA2LDggQEAgZ2V0X25leHRfY2h1bmsoZG5vZGVfdCAqZG4s IHVpbnQ2NF90ICpzdGFydCwgdWludDY0X3QgbWluaW11bSwgdWludDY0X3QgKmwxYmxrcykK IAl1aW50NjRfdCBibGtzOwogCXVpbnQ2NF90IG1heGJsa3MgPSBETVVfTUFYX0FDQ0VTUyA+ PiAoZG4tPmRuX2luZGJsa3NoaWZ0ICsgMSk7CiAJLyogYnl0ZXMgb2YgZGF0YSBjb3ZlcmVk IGJ5IGEgbGV2ZWwtMSBpbmRpcmVjdCBibG9jayAqLwotCXVpbnQ2NF90IGlibGtyYW5nZSA9 Ci0JICAgIGRuLT5kbl9kYXRhYmxrc3ogKiBFUEIoZG4tPmRuX2luZGJsa3NoaWZ0LCBTUEFf QkxLUFRSU0hJRlQpOworCXVpbnQ2NF90IGlibGtyYW5nZSA9ICh1aW50NjRfdClkbi0+ZG5f ZGF0YWJsa3N6ICoKKwkgICAgRVBCKGRuLT5kbl9pbmRibGtzaGlmdCwgU1BBX0JMS1BUUlNI SUZUKTsKIAogCUFTU0VSVDNVKG1pbmltdW0sIDw9LCAqc3RhcnQpOwogCg== --------------FE979ADD05CA9275BD1DEAB1-- --XneqEwXk1LWTeK4jeMQaX0baW6tMGMjaJ-- --wsbw9hmkTNwxa3Ff6gqzYMRZHE8zGBIsv Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEceNg5NEMZIki80nQQHl/fJX0g08FAmAR9eQFAwAAAAAACgkQQHl/fJX0g0/j Tg//VCAoPsVtMZC1DA3T2VivZOZM9Sp0wXfY/W8uk4P0QMc80bfCg61YdFBe+h2VVJtRT9NW31rh WIM1MMuVR8rEIeV72mj32dLEIG8bDA9kTt7r7Ji3zARt5lP7cp6tDOlN3okavjeDGA62es4ephGo N6HGJ65CkQFEm7G1Htbb40HINaZEIsqeCZo6+JLvBLTQo5tBJzTj0LZ0cELyYFJTa4A4i3jquVZZ JG3vsadY2+haqD2ucci8gBBb+rou6vC4+/SPMQNyT98SNEYJvCP0ERZjQKQAXTkSIK2xlS/4FCjl YntDvA2nnCGY8mm8RAb5yAHO2ha6/vEagv1J0jvVpNiTirCx4SXPIIu6qmqTwuFiChnZqTOAHzBd tb8SdD6dPeipok/a0PMRBXLlfxHXXE+fo5OfitT7Ux6QSq5QdoKzMgstfgwYhO59hvemZ3SGj0BF EYJRMAorqk4HkPjHD4pYQ+yYjLWQuOzbDEQ8DO1hOQYUWh6sl+5JYwmi7jPshaTtpUIZTeFu3dO+ 7JAlUzGJsD8nV/+zgGj0ZztndddT7o+bZg5gkoWryyIo37A1OtcPQD6+GBecRR6vjvq++vo4eqDc BPZd2vASDAdvoNipGooh276KV3zINMIugCiW25EmvY3vmXfLckWjIe7OUG5wMup0OKE3RVruNJAm JQg= =FOpJ -----END PGP SIGNATURE----- --wsbw9hmkTNwxa3Ff6gqzYMRZHE8zGBIsv-- From owner-freebsd-fs@freebsd.org Wed Jan 27 23:23:35 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2E3034ECF66 for ; Wed, 27 Jan 2021 23:23:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DR05z0TQrz3m74 for ; Wed, 27 Jan 2021 23:23:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 1020D4ED11D; Wed, 27 Jan 2021 23:23:35 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0FBC64ECEB2 for ; Wed, 27 Jan 2021 23:23:35 +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 4DR05y6x0Jz3m73 for ; Wed, 27 Jan 2021 23:23:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E010425142 for ; Wed, 27 Jan 2021 23:23:34 +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 10RNNYS5003685 for ; Wed, 27 Jan 2021 23:23:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10RNNYXP003684 for fs@FreeBSD.org; Wed, 27 Jan 2021 23:23:34 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 250784] integer divide fault in zfs_rmnode Date: Wed, 27 Jan 2021 23:23:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: panic, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: delphij@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 23:23:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250784 Xin LI changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |delphij@FreeBSD.org --- Comment #9 from Xin LI --- Looks like https://github.com/openzfs/zfs/issues/8778 ? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Jan 27 09:56:01 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 083464F3F0A for ; Wed, 27 Jan 2021 09:56:01 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (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 "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DQfB80T87z3kJy for ; Wed, 27 Jan 2021 09:55:59 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 8E3122384C8 for ; Wed, 27 Jan 2021 09:55:51 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=uk1; t=1611741351; bh=1Nh2Pn20evGeEzkD4sUwfJmtL69TH4aCTI+yqus9lSA=; h=From:To:Subject:Date; b=U6ZfL2MfR5fh0OwcUP8L9ye0iqlHyIQvmRm/Ira2OXJBDkbRAzt0xSDRlbEPsM7R5 A6JMAC+lnls3aIEFVQEEznYpjcalT2Tfhy/okfUhYAeHZdbsauaZmeLWoVTkEEOlux rQLEHrPuNkcr1p9NMnLqbCujyXmOhVJh88yuWoUQ= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 27 Jan 2021 09:55:50 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Wed, 27 Jan 2021 09:55:50 +0000 From: Matt Churchyard To: "freebsd-fs@freebsd.org" Subject: ZFS issues on 13-current snapshot Thread-Topic: ZFS issues on 13-current snapshot Thread-Index: Adb0kYPUY0NlcoqCRkqDCQZIgZuN1g== Date: Wed, 27 Jan 2021 09:55:49 +0000 Message-ID: <283b2b0b5df34c4f9b8c78b078a67381@SERVER.ad.usd-group.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 X-Rspamd-Queue-Id: 4DQfB80T87z3kJy X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=userve.net header.s=uk1 header.b=U6ZfL2Mf; dmarc=none; spf=pass (mx1.freebsd.org: domain of matt.churchyard@userve.net designates 217.196.1.22 as permitted sender) smtp.mailfrom=matt.churchyard@userve.net X-Spamd-Result: default: False [-3.50 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.196.1.22:from]; R_DKIM_ALLOW(-0.20)[userve.net:s=uk1]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.196.1.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[userve.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[217.196.1.22:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[userve.net:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20652, ipnet:217.196.0.0/20, country:GB]; MAILMAN_DEST(0.00)[freebsd-fs] X-Mailman-Approved-At: Thu, 28 Jan 2021 05:38:19 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2021 09:56:01 -0000 Hello, I'm testing a 13-current machine for future use as an encrypted offsite bac= kup store. As it's near release I was kind of hoping to get away with using= this 13 snapshot for a few months then switch to a RELEASE bootenv when it= comes out. However, I seem to be having a few issues. First of all I stated noticing that the USED & REFER columns weren't equal = for individual datasets. This system so far has simply received a single sn= apshot of a few datasets, and had readonly set immediately after. Some of t= hem are showing several hundred MB linked to snapshots on datasets that hav= en't been touched. I'm unable to send further snapshots without forcing a r= ollback first. Not the end of the world but this isn't right and has never = happened on previous ZFS systems. The most I've seen is a few KB because I = forgot to set readonly and went into a few directories on a dataset with at= ime=3Don. offsite 446G 6.36T 140K /offsite [...] offsite/secure/cms 359M 6.3= 6T 341M /offsite/secure/cms offsite/secure/cms@26-01-2021 17.6M = - 341M - offsite/secure/company 225G 6.3= 6T 224G /offsite/secure/company offsite/secure/company@25-01-2021 673M = - 224G - offsite/secure is an encrypted dataset using default options. zfs diff will sit for a while (on small datasets - I gave up trying to run = it on anything over a few GB) and eventually output nothing. root@offsite:/etc # uname -a FreeBSD offsite.backup 13.0-CURRENT FreeBSD 13.0-CURRENT #0 main-c255641-gf= 2b794e1e90: Thu Jan 7 06:25:26 UTC 2021 root@releng1.nyi.freebsd.org:/= usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 root@offsite:/etc # zpool version zfs-0.8.0-1 zfs-kmod-0.8.0-1 I then thought I would run a scrub just to see if it found any obvious prob= lems. It started off running fine, estimating about 45-60 minutes for the whole p= rocess of scanning 446GB. (This is 4 basic SATA Ironwolf 4TB disks in raidz= 2) However it appeared to stall at 19.7%. Eventually it hit 19.71, and does ap= pear to be going up, but at this point looks like it may take a days to com= plete (currently says 3 hours but it's skewed by the initial fast progress = and going up every time I check). Gstat shows the disks at 100% doing anywhere between 10-50MB/s. (They were = hitting anywhere up to 170MB/s to start off with. Obviously this varies whe= n having to seek, but even at the rates currently seen I suspect it should = be progressing faster than zpool output shows) root@offsite:/etc # zpool status pool: offsite state: ONLINE scan: scrub in progress since Wed Jan 27 09:29:50 2021 555G scanned at 201M/s, 182G issued at 65.8M/s, 921G total 0B repaired, 19.71% done, 03:11:51 to go config: NAME STATE READ WRITE CKSUM offsite ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gpt/data-ZGY85VKX ONLINE 0 0 0 gpt/data-ZGY88MRY ONLINE 0 0 0 gpt/data-ZGY88NZJ ONLINE 0 0 0 gpt/data-ZGY88QKF ONLINE 0 0 0 errors: No known data errors Update: I've probably spent 30+ minutes writing this email and it's reporti= ng a few more GB read but not a single digit in progress percent. scan: scrub in progress since Wed Jan 27 09:29:50 2021 559G scanned at 142M/s, 182G issued at 46.2M/s, 921G total 0B repaired, 19.71% done, 04:33:08 to go It doesn't inspire a lot of confidence. ZFS had become pretty rock solid in= FreeBSD in recent years and I have many systems running it. This should ha= ve the most efficient scrub code to date and yet is currently taking about = an hour to progress 0.01% on a new system with a fraction of the data it wi= ll hold and 0% fragmentation. As it stands at the moment, I will likely scrap this attempt and retry with= FreeBSD 12. Regards, Matt Churchyard From owner-freebsd-fs@freebsd.org Thu Jan 28 07:23:12 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CCB5A4FA93B for ; Thu, 28 Jan 2021 07:23:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRBlN5G97z4jQ6 for ; Thu, 28 Jan 2021 07:23:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id B49464FA754; Thu, 28 Jan 2021 07:23:12 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B45904FAB2F for ; Thu, 28 Jan 2021 07:23:12 +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 4DRBlN4Z9wz4jKT for ; Thu, 28 Jan 2021 07:23:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8FC9D37D6 for ; Thu, 28 Jan 2021 07:23:12 +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 10S7NCZW060374 for ; Thu, 28 Jan 2021 07:23:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10S7NCp0060373 for fs@FreeBSD.org; Thu, 28 Jan 2021 07:23: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 224292] processes are hanging in state ufs / possible deadlock in file system Date: Thu, 28 Jan 2021 07:23:12 +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: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ali.abdallah@suse.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: 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 07:23:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224292 Ali Abdallah changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ali.abdallah@suse.com --- Comment #13 from Ali Abdallah --- While upgrading my FreeBSD 13-CURRENT box yesterday, I ran into this issue, when compiling the kernel and then world with -j8, I was ending up always w= ith all the cc processes stuck in biowr and ufs. At the end I've upgraded my box through NFS from my 13-CURRENT server (zfs based). But when upgrading ports from the same server, using pkg upgrade -f, it was also getting stuck with the same symptoms. I've managed to take a kernel du= mp, then booted into single user mode, disabled soft update journaling: (-j), = then booted the system and upgraded my packages, all went ok. Looking at the dump, I see lots of dd processes (launched by pkg I believe), that are in the following state: read 345 (Thread 100752 (PID=3D32594: dd)): #0 sched_switch (td=3D0xfffffe00fdd9be00, flags=3D) at /usr/src/sys/kern/sched_ule.c:2147 #1 0xffffffff803db4be in mi_switch (flags=3Dflags@entry=3D260) at /usr/src/sys/kern/kern_synch.c:542 #2 0xffffffff8042a43d in sleepq_switch (wchan=3Dwchan@entry=3D0x0, pri=3Dpri@entry=3D2122752) at /usr/src/sys/kern/subr_sleepqueue.c:608 #3 0xffffffff8042a327 in sleepq_wait (wchan=3D, pri=3D) at /usr/src/sys/kern/subr_sleepqueue.c:659 #4 0xffffffff803a9f7f in sleeplk (lk=3Dlk@entry=3D0xfffff8000535f810, flags=3Dflags@entry=3D2122752, ilk=3D, ilk@entry=3D0xfffff80= 00535f840, wmesg=3D, wmesg@entry=3D0xffffffff806c8ccb "ufs", pri=3D, pri@entry=3D96, timo=3Dtimo@entry=3D51, queue=3D1) at /usr/src/sys/kern/kern_lock.c:301 #5 0xffffffff803a88e2 in lockmgr_slock_hard (lk=3D0xfffff8000535f810, flags=3Dflags@entry=3D2122752, ilk=3D0xfffff8000535f840, ilk@entry=3D0xfffffe00fdaff658, file=3D, line=3D, lwa=3Dlwa@entry=3D0x0) at /usr/src/sys/kern/kern_lock.c:696 #6 0xffffffff803a84e8 in lockmgr_lock_flags (lk=3D, lk@entry=3D0xfffff8000535f810, flags=3Dflags@entry=3D2122752, ilk=3Dilk@entry=3D0xfffff8000535f840, file=3D, line=3D) at /usr/src/sys/kern/kern_lock.c:1056 #7 0xffffffff805c90e5 in ffs_lock (ap=3D0xfffffe00fdaff658, ap@entry=3D) at /usr/src/sys/ufs/ffs/ffs_vnops.c:494 #8 0xffffffff804be098 in VOP_LOCK1 (vp=3D0xfffff8000535f7a0, flags=3D21063= 68, file=3D0xffffffff806fac3e "/usr/src/sys/kern/vfs_lookup.c", line=3D877) at ./vnode_if.h:1096 #9 _vn_lock (vp=3Dvp@entry=3D0xfffff8000535f7a0, flags=3D2106368, file=3D0xffffffff806fac3e "/usr/src/sys/kern/vfs_lookup.c", line=3Dline@ent= ry=3D877) at /usr/src/sys/kern/vfs_vnops.c:1741 #10 0xffffffff80497a18 in lookup (ndp=3Dndp@entry=3D0xfffffe00fdaff970) at /usr/src/sys/kern/vfs_lookup.c:875 #11 0xffffffff804973dd in namei (ndp=3Dndp@entry=3D0xfffffe00fdaff970) at /usr/src/sys/kern/vfs_lookup.c:631 --Type for more, q to quit, c to continue without paging-- #12 0xffffffff804bd590 in vn_open_cred (ndp=3Dndp@entry=3D0xfffffe00fdaff97= 0, flagp=3D, flagp@entry=3D0xfffffe00fdaffa94, cmode=3D, vn_open_flags=3Dvn_open_flags@entry=3D0, cred=3D, fp=3D0xfffff80003d49140) at /usr/src/sys/kern/vfs_vnops.c:252 #13 0xffffffff804bd44d in vn_open (ndp=3D, ndp@entry=3D0xfffffe00fdaff970, flagp=3D, flagp@entry=3D0xfffffe00fdaffa94, cmode=3D, fp=3D= ) at /usr/src/sys/kern/vfs_vnops.c:193 #14 0xffffffff804b3723 in kern_openat (td=3D0xfffffe00fdd9be00, fd=3D, path=3D, pathseg=3D, flags=3D1539, mode=3D) at /usr/src/sys/kern/vfs_syscalls.c:1143 #15 0xffffffff8068d5cc in syscallenter (td=3D0xfffffe00fdd9be00) at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:189 #16 amd64_syscall (td=3D0xfffffe00fdd9be00, traced=3D0) at /usr/src/sys/amd64/amd64/trap.c:1156 I will enable back -j, and kernel deadlocks debugging features, to hopefully get more debugging information. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 28 08:09:43 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 24C404FC4A3 for ; Thu, 28 Jan 2021 08:09:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRCn30Mspz4mQL for ; Thu, 28 Jan 2021 08:09:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 0AFFD4FC4A2; Thu, 28 Jan 2021 08:09:43 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0ACB34FC341 for ; Thu, 28 Jan 2021 08:09:43 +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 4DRCn26rXFz4m6w for ; Thu, 28 Jan 2021 08:09:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DA427458A for ; Thu, 28 Jan 2021 08:09:42 +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 10S89grH081377 for ; Thu, 28 Jan 2021 08:09:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10S89gHQ081376 for fs@FreeBSD.org; Thu, 28 Jan 2021 08:09:42 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 253048] unionfs shows old file with link count of zero Date: Thu, 28 Jan 2021 08:09:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 08:09:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253048 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 28 11:44:14 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 606B95221F5 for ; Thu, 28 Jan 2021 11:44:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRJXZ201Yz3G2L for ; Thu, 28 Jan 2021 11:44:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 4425A5221F4; Thu, 28 Jan 2021 11:44:14 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 43E8B52243D for ; Thu, 28 Jan 2021 11: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 4DRJXY6PJQz3FxL for ; Thu, 28 Jan 2021 11:44:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CED9A70B4 for ; Thu, 28 Jan 2021 11: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 10SBiD06007189 for ; Thu, 28 Jan 2021 11:44:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10SBiDnj007188 for fs@FreeBSD.org; Thu, 28 Jan 2021 11:44:13 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 250784] integer divide fault in zfs_rmnode Date: Thu, 28 Jan 2021 11: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: 12.2-RELEASE X-Bugzilla-Keywords: panic, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pen@lysator.liu.se X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 11:44:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250784 Peter Eriksson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pen@lysator.liu.se --- Comment #10 from Peter Eriksson --- Definitely looks like the same bug considering that the simple fix from Ope= nZFS is not applied to the FreeBSD zfs code - so that bug is definitely there. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 28 13:09:28 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7F29452509F for ; Thu, 28 Jan 2021 13:09:28 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (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 "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DRLQv4fC7z3Ls9 for ; Thu, 28 Jan 2021 13:09:27 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 1C1592383B2 for ; Thu, 28 Jan 2021 13:09:20 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=uk1; t=1611839360; bh=/jmC8MCzFncgi3f+KxriaD/ZRUdKJuPTk80hOcV2koo=; h=From:To:Subject:Date; b=DiXyKegPOSo28rYlD8djpV/NwLGnYJpYYZlmVg9uGU7F5wFFwY4IQeJ3RzW62KG4W EGBWmtmDOyQ69pEp8jA1Gao6IwwhFQiRy/tj3D9IEaQ7tmcp6VXwukL5VQ/l2IeSS3 KLZ2I/S5icXb87LEGAPqfBYOehhidkY9Ch12eIxE= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Thu, 28 Jan 2021 13:09:18 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Thu, 28 Jan 2021 13:09:17 +0000 From: Matt Churchyard To: "freebsd-fs@freebsd.org" Subject: Re: ZFS issues on 13-current snapshot Thread-Topic: ZFS issues on 13-current snapshot Thread-Index: Adb1dphvm765z7eNRH2Om87F1OUQ0A== Date: Thu, 28 Jan 2021 13:09:17 +0000 Message-ID: <90b46fa559f34d5986d25e98878926c7@SERVER.ad.usd-group.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Rspamd-Queue-Id: 4DRLQv4fC7z3Ls9 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=userve.net header.s=uk1 header.b=DiXyKegP; dmarc=none; spf=pass (mx1.freebsd.org: domain of matt.churchyard@userve.net designates 217.196.1.22 as permitted sender) smtp.mailfrom=matt.churchyard@userve.net X-Spamd-Result: default: False [-2.50 / 15.00]; FAKE_REPLY(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.196.1.22:from]; R_DKIM_ALLOW(-0.20)[userve.net:s=uk1]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.196.1.0/24]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[217.196.1.22:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[userve.net]; DKIM_TRACE(0.00)[userve.net:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20652, ipnet:217.196.0.0/20, country:GB]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 13:09:28 -0000 Hello Just a follow up on my email yesterday about ZFS issues on a 13-current sna= pshot. I have now scrapped the 13 system, reinstalled 12.2 on a new pool, and copi= ed the same ~400GB of data to it. This is the outcome - 1) I no longer see phantom data in snapshots that have been sent to the poo= l. Every snapshot lists 0 usage. "zfs diff" is also much happier and runs i= n seconds on any dataset. 2) I can scrub the entire pool in 30 minutes with the disks pushing 150MBps= + pretty much the entire time. I eventually cancelled the scrub on 13; It s= tayed at 19% for about 4 hours, then made some progress to about 65%, befor= e sitting there for another 6 hours. I gave up in the end and stopped it. # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALT= H ALTROOT offsite 14.5T 906G 13.6T - - 0% 6% 1.00x ONLIN= E - # zpool status pool: offsite state: ONLINE scan: scrub repaired 0 in 0 days 00:27:46 with 0 errors on Thu Jan 28 13:= 44:47 2021 3) Additional minor thing unrelated to ZFS or storage, but I noticed that '= systat -ifstat 1' was showing 23MB/s throughput which let me to believe I m= ust have been running at a gigabit and just getting slow throughput for oth= er reasons. I probably should have looked into this more considering the se= nder showed 11MB/s. On 12.2, I see 11MB/s on both ends, making it very clea= r it was definitely capping at 100Mbps. I eventually tracked down a 100Mbps= link - obviously not a FreeBSD issue, but it seems systat was reporting do= uble on 13. Maybe some of these are due to it being a current dev snapshot and having v= arious debug features active, but I think I will be seeing the general resp= onse when 13 comes out before I go anywhere near it... Regards, Matt Churchyard From owner-freebsd-fs@freebsd.org Thu Jan 28 13:56:48 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 72D3652600C for ; Thu, 28 Jan 2021 13:56:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRMTX2f3Rz3PlF for ; Thu, 28 Jan 2021 13:56:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 5AC0852600B; Thu, 28 Jan 2021 13:56:48 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5A861525FA5 for ; Thu, 28 Jan 2021 13:56:48 +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 4DRMTX2341z3PX6 for ; Thu, 28 Jan 2021 13:56:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3553510FF9 for ; Thu, 28 Jan 2021 13:56:48 +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 10SDum90083557 for ; Thu, 28 Jan 2021 13:56:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10SDumOX083556 for fs@FreeBSD.org; Thu, 28 Jan 2021 13:56:48 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 224292] processes are hanging in state ufs / possible deadlock in file system Date: Thu, 28 Jan 2021 13:56:47 +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: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 13:56:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224292 --- Comment #14 from Konstantin Belousov --- (In reply to Ali Abdallah from comment #13) This is certainly not related to the bug you replied to. That said, your issue _might_ be fixed by the patch series available at https://kib.kiev.ua/git/gitweb.cgi?p=3Ddeviant3.git;a=3Dshortlog;h=3Drefs/h= eads/ufs_needsync I.e. I am sufficiently curious if this patches from the ufs_needsync branch make any difference for your setup. Something similar was reported by Peter Holm as well, I believe. If not, I will look at your report after this branch lands. You would need to follow the 'debugging deadlock' chapter from the developers handbook to gather required information. Or provide a reproduct= ion recipe to Peter Holm. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 28 17:16:11 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C30634E3A1F for ; Thu, 28 Jan 2021 17:16:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRRvb4zBMz3tt6 for ; Thu, 28 Jan 2021 17:16:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id AAB104E3862; Thu, 28 Jan 2021 17:16:11 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AA7C94E374C for ; Thu, 28 Jan 2021 17:16:11 +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 4DRRvb4N7Lz3thr for ; Thu, 28 Jan 2021 17:16:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 88E15138BB for ; Thu, 28 Jan 2021 17:16:11 +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 10SHGB7T000830 for ; Thu, 28 Jan 2021 17:16:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10SHGB1h000829 for fs@FreeBSD.org; Thu, 28 Jan 2021 17:16:11 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 253063] Hanging zfs processes after upgrade from 12.1 to 12.2-stable Date: Thu, 28 Jan 2021 17:16:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 17:16:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253063 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org Keywords| |regression --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 28 18:59:34 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C564D4E738D for ; Thu, 28 Jan 2021 18:59:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRVBt51LPz4WQW for ; Thu, 28 Jan 2021 18:59:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id AC0D54E738C; Thu, 28 Jan 2021 18:59:34 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ABD484E71E8 for ; Thu, 28 Jan 2021 18:59:34 +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 4DRVBt4Ptbz4Wff for ; Thu, 28 Jan 2021 18:59:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 864BB14FCE for ; Thu, 28 Jan 2021 18:59:34 +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 10SIxY1U057853 for ; Thu, 28 Jan 2021 18:59:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10SIxYrb057852 for fs@FreeBSD.org; Thu, 28 Jan 2021 18:59:34 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 253063] Hanging zfs processes after upgrade from 12.1 to 12.2-stable Date: Thu, 28 Jan 2021 18:59:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pen@lysator.liu.se X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 18:59:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253063 Peter Eriksson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pen@lysator.liu.se --- Comment #1 from Peter Eriksson --- (In reply to Markus Wild from comment #0) How much free space is there in the filesystems - any filesystems near quota limits? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 28 19:00:36 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D257F4E70F2; Thu, 28 Jan 2021 19:00:36 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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 4DRVD44C43z4WT3; Thu, 28 Jan 2021 19:00:36 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.94 (FreeBSD)) (envelope-from ) id 1l5CWm-000HFo-Ux; Thu, 28 Jan 2021 20:00:24 +0100 Date: Thu, 28 Jan 2021 20:00:24 +0100 From: Kurt Jaeger To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: zpool upgrade to draid feature: does it require updated zfs boot code ? Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4DRVD44C43z4WT3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; local_wl_from(0.00)[freebsd.org] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 19:00:36 -0000 Hi! Short question: Does a zpool upgrade on 14.0 (current) for the draid feature require a boot code update ? Long version of the same question: I've upgraded my testbox to FreeBSD 14.0-CURRENT #0 main-c256294-g2cf84258922f and the system listed the zfs-feature draid as available if I do an zpool upgrade. The pool resides on two nvme drives: mirror-0 ONLINE 0 0 0 nvd0p4 ONLINE 0 0 0 nvd1p4 ONLINE 0 0 0 Normally, when I do the zpool upgrade for the pool, and the zpool upgrade also requires an upgrade to the bootcode, some message is displayed, reminding me to do so. With the draid update, no message was displayed. Does it require the bootcode update anyway or, if not, why not ? gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd1 -- pi@opsec.eu +49 171 3101372 Now what ? From owner-freebsd-fs@freebsd.org Thu Jan 28 19:41:08 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CB3CB4E999D for ; Thu, 28 Jan 2021 19:41:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRW6r5CvHz4b7h for ; Thu, 28 Jan 2021 19:41:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id B2FA64E9A1F; Thu, 28 Jan 2021 19:41:08 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B2C124E999C for ; Thu, 28 Jan 2021 19:41:08 +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 4DRW6r4d0Pz4b7g for ; Thu, 28 Jan 2021 19:41:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 91CEB15B19 for ; Thu, 28 Jan 2021 19:41: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 10SJf8P5082618 for ; Thu, 28 Jan 2021 19:41:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10SJf8w2082617 for fs@FreeBSD.org; Thu, 28 Jan 2021 19:41: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 253063] Hanging zfs processes after upgrade from 12.1 to 12.2-stable Date: Thu, 28 Jan 2021 19:41:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugs@virtualtec.ch X-Bugzilla-Status: New 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 19:41:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253063 --- Comment #2 from Markus Wild --- (In reply to Peter Eriksson from comment #1) Both data pools are in single digit capacity percentage, and no filesystem = with a=20 quota is anywhere near the limit. I've now rebooted the system, so I can=20 query some more zfs-related info if that helps. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jan 28 23:53:51 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 45F2E4F1259; Thu, 28 Jan 2021 23:53:51 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DRckQ2HYTz4sds; Thu, 28 Jan 2021 23:53:50 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qt1-x830.google.com with SMTP id l23so5477929qtq.13; Thu, 28 Jan 2021 15:53:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=WJFNSvMBdVpfyLl0M2CBNJgNvupOByuSqUd2ep2DIuY=; b=AicjVQWQX5EZReAYxtbRTmS2f8IGhvYvX4Yzkw3v8pSuvrwEXK/uVSRerxegPnnK9/ G/Zu3Oj4fCLtHzjl7WPND+FBHUR54hnafCkca8hd2Ey+VvvCF5yiesmboEKL6w0w6qc+ jiD8xhCFNWsBCdiQsWCZ2one0bJ9bdrkLEZTg9FwXkQB0GrGuv4AyxI8Kh3Y5lOZ+r6j Et7CeULflhyaohJdLjKoKIKGjZ2VYYtuvvRY0arV9ats0Lultx56vgtKWUZHpTYtR52D jfJofOcFB7jml1JnE5mPjv4hYMUmo6WldpNgy/edmIljIUxuPjSCzj6WoDhHJ72F5wUt 8e2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WJFNSvMBdVpfyLl0M2CBNJgNvupOByuSqUd2ep2DIuY=; b=jNNUogTalH0dJTFxnBqMRsIJU+GveZ/5rztXSwT4MUIcBcPTgL+fSh/UzSsPcpwa3N /fkOnD4FQYu59Jm3PRKrkdHI18ObxKJybTrphMyAb8I4nOMFzqs7C/eqcB8EdNIs9Gde fH3fku2ytC1kYY5xD0iaKmdtDYnjsvU2W4yvjXXA58laXIwwCXQ1yZCXMOk170FYQpRW y1bv2CQbO7zwHmM9cIKj56vuT4qkd7GHZ2gMrwoOLbQTbxepeuKqB9sAYTG2Q1ebrf8Z GXr3jxdRUQpJcimWdPbTAq8WeLIynIUgO+t5ifCLA2fSbZkKrDLbkZdUk3ohubz8RG1S u9Qw== X-Gm-Message-State: AOAM531f5oCz0f0i61DnFx5uuXhaaTWaWPHsIF6Ko3MAEzVv7ZNF+u0Y GckeRfa4lUeGTDtpWVwkoHypR0cnLpo5qhsPlhVXSIvT X-Google-Smtp-Source: ABdhPJyeTnxPI1rTfytbUuLgDNMR/j4Kgv7MrErWVw2fpQ/sBWagCmYO1clh/ZwzPb8bCtydX+HO3wTsjBUUR0ntxwo= X-Received: by 2002:ac8:6b44:: with SMTP id x4mr2060459qts.224.1611878028336; Thu, 28 Jan 2021 15:53:48 -0800 (PST) MIME-Version: 1.0 From: Freddie Cash Date: Thu, 28 Jan 2021 15:53:37 -0800 Message-ID: Subject: OpenZFS dRAID questions To: FreeBSD Filesystems , FreeBSD Stable X-Rspamd-Queue-Id: 4DRckQ2HYTz4sds X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=AicjVQWQ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of fjwcash@gmail.com designates 2607:f8b0:4864:20::830 as permitted sender) smtp.mailfrom=fjwcash@gmail.com X-Spamd-Result: default: False [-3.73 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::830:from]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::830:from:127.0.2.255]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::830:from]; NEURAL_HAM_SHORT(-0.73)[-0.725]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-fs,freebsd-stable]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 23:53:51 -0000 [Not sure which list is more applicable for this question, so sending to -fs and -stable. If it should be only one or the other, let me know.] Trying to get an understanding of how the dRAID vdev support works in ZFS, and what a good setup would be for a storage server using multiple JBODs full of SATA drives. Right now, my storage pools are made up of 6-disk raidz2 vdevs. So my 24-bay systems have 4x raidz2 vdevs, my 45-bay systems have 7x raidz2 vdevs with 3 (cold) spares, and my 90-bay systems have 15x raidz2 vdevs (1 vdev uses the 3 extra drives from each 45-drive JBOD). If I'm reading the dRAID docs correctly, instead of having multiple raidz2 vdevs in the pool, I'd have a single draid vdev, configured with children that are configured with similar data/parity devices to "mimic" raidz2? If that's correct, would it make sense to have a single draid vdev per pool (splitting the draid vdev across JBODs)? Or a single draid vdev per JBOD chassis (so 2x draid vdevs)? What's the practical limit for the number of drives in a single draid vdev? I have a brand new storage server sitting in a box with a 44-bay JBOD that will be going into the server room next week, and I'm tempted to try draid on it instead of the multiple-raidz2 setup. This would use 4+2 (data+parity) children with 2 spares, I believe. This server will be replacing a 90-bay system (2x JBODs), which will then be used as another storage server once all the dying drives are replaced. Will be interesting to see how draid works on that one as well, but not sure how to configure it. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@freebsd.org Fri Jan 29 00:20:04 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EEE0F4F290C for ; Fri, 29 Jan 2021 00:20:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRdJh3rLyz3Bt4 for ; Fri, 29 Jan 2021 00:20:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 675A24F26A5; Fri, 29 Jan 2021 00:20:04 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 66F974F2633 for ; Fri, 29 Jan 2021 00:20:04 +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 4DRdJg3y6hz4vtZ for ; Fri, 29 Jan 2021 00:20:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D935618DE3 for ; Fri, 29 Jan 2021 00:19:57 +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 10T0JvEo041174 for ; Fri, 29 Jan 2021 00:19:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10T0JvCd041173 for fs@FreeBSD.org; Fri, 29 Jan 2021 00:19:57 GMT (envelope-from bugzilla-noreply@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: [Bug 244089] lsextattr on a specific UFS file locks system Date: Fri, 29 Jan 2021 00:19:55 +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: 11.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@FreeBSD.org X-Bugzilla-Status: New 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 00:20:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244089 --- Comment #9 from commit-hook@FreeBSD.org --- A commit in branch releng/11.4 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D612e060c036f9328e6c19a3525d33d1d3= 3006e04 commit 612e060c036f9328e6c19a3525d33d1d33006e04 Author: Ed Maste AuthorDate: 2021-01-18 16:58:38 +0000 Commit: Ed Maste CommitDate: 2021-01-29 00:06:55 +0000 ffs: avoid creating corrupt extattrfile This is part of r312416 / e6790841f749, suggested by ml@netfence.it, and will stop the kernel from creating corrupt extattr. PR: 244089 (cherry picked from commit eebccaae36722f62bc8f05e6c71b867d69faca5f) Approved by: so sys/ufs/ffs/ffs_vnops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Jan 29 07:25:52 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 99F8D4E00E5 for ; Fri, 29 Jan 2021 07:25:52 +0000 (UTC) (envelope-from stevenschlansker@gmail.com) Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DRplz4ncdz4Sk9 for ; Fri, 29 Jan 2021 07:25:51 +0000 (UTC) (envelope-from stevenschlansker@gmail.com) Received: by mail-vk1-xa2e.google.com with SMTP id g17so1955398vkk.5 for ; Thu, 28 Jan 2021 23:25:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+Mi+2CC4eDaPw2YxCAQhG9fSA7b90YOBkALwBnBhV/E=; b=dpJnoQqg33lUSRkOlV8nbOoQdTxDAS7wLbPR5wFYx/eumgECEXaFNSSeHAKifMHJA+ UN2QRb1yUVV/lY8yf68VGXxAkZpx2JLSeHJhf6EgwX0RywaiByNkBksYXGDxHaRs/mOL eWeGbnPwpNpK8jyFE0pQT0FYGGRYjVST+Fwl7O10Z9Igc0QstsBS0z6zhUG2aRwbnT2O qQCQ198MbOsOljuztTNecoGgjiqh7c3FQFBBSHiIb//Rw92R7gRKYXe1BPUYbmdpwR9w FDOLE+LLXzB4BqwR4bRc+nvmGPNhOBrSWFrlq1nltpWzMTOcSUfnHtsvS5csFF8Ym8Gj QHHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+Mi+2CC4eDaPw2YxCAQhG9fSA7b90YOBkALwBnBhV/E=; b=N8svwJoGwsNcWeMMYeFPx+awBo+qPl0a4qH1SEaKYnD/PVjnPhZ3LUO2ivcVge0VQT 5wShGxSz/d7gTe5/L/gO6fySPf/mT8Uz0eC0RNXMQgNNLNxpsb6OwSOP/t2tbdYKrdRW sOw7ECUqeEbSvt1Lt6YR8tOifFQyTGB7J4VdUDjcBgQkDGw+aQl7SZ60HaZeVQMlTi2D 5Cea5p7vV31mbOAnZ5Tzz5VC2OfWyXPJszOCnD3Uat8qcavsekdF4wArhBZNFSLP2qmW xF5iMKzptoDFCpIbS8D+DH76F0uWT4ObQqMP1CAUJvvdQpkBBNE3NmBrLQy1ZlvzyXQ0 ixtg== X-Gm-Message-State: AOAM532MFFbOM67PrFbiwLJcXUD4NQFQc1R3YgUvr7fzAe3B7peBWGo6 E/zFJ5PyPCf604Z8f/2+NNwO/CpmsT+WaBMtztkK+D9Yd2E= X-Google-Smtp-Source: ABdhPJyzUF+3JA9kfEwVezlI23eh1A6Oksf6otq4BcEI648jOvYHIn9Rs8WWhgJGBK5gZKXUmt/SqqegbvPz7nGMEpA= X-Received: by 2002:a1f:ab43:: with SMTP id u64mr2090740vke.3.1611905150647; Thu, 28 Jan 2021 23:25:50 -0800 (PST) MIME-Version: 1.0 References: <560ca3ae-82ca-d3f7-ad15-690d74e0a885@delphij.net> In-Reply-To: <560ca3ae-82ca-d3f7-ad15-690d74e0a885@delphij.net> From: Steven Schlansker Date: Thu, 28 Jan 2021 23:25:38 -0800 Message-ID: Subject: Re: persistent integer divide fault panic in zfs_rmnode To: d@delphij.net Cc: freebsd-fs@freebsd.org X-Rspamd-Queue-Id: 4DRplz4ncdz4Sk9 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=dpJnoQqg; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of stevenschlansker@gmail.com designates 2607:f8b0:4864:20::a2e as permitted sender) smtp.mailfrom=stevenschlansker@gmail.com X-Spamd-Result: default: False [-0.05 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::a2e:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.95)[0.954]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::a2e:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::a2e:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 07:25:52 -0000 Thank you Xin, indeed, this patch against 12.2-RELEASE seems to have cleared the issue up entirely! We'll try out openzfs once 13 is released. On Wed, Jan 27, 2021 at 3:23 PM Xin Li wrote: > On 1/27/21 10:15, Steven Schlansker wrote: > > Does anybody have any suggestions as to what I can try next regarding > this > > panic? > > > > At this point the only path forward I see is to declare the zpool corrupt > > and attempt to > > move all the data off, destroy, and migrate back, and hope the recreated > > pool does not tickle this bug. > > > > That would be a pretty disappointing end to a long fatal-problem-free run > > with ZFS. > > Could you please try the attached patch? (Full context: > https://github.com/openzfs/zfs/issues/8778 ) > > Cheers, > From owner-freebsd-fs@freebsd.org Fri Jan 29 07:26:24 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 416604E022D for ; Fri, 29 Jan 2021 07:26:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRpmc1Btfz4Swj for ; Fri, 29 Jan 2021 07:26:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 290C64E01A4; Fri, 29 Jan 2021 07:26:24 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 28D264FFD6B for ; Fri, 29 Jan 2021 07:26: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 4DRpmc0GDcz4Snl for ; Fri, 29 Jan 2021 07:26:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id F002E1EB1C for ; Fri, 29 Jan 2021 07:26: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 10T7QNRi063435 for ; Fri, 29 Jan 2021 07:26:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10T7QN8b063434 for fs@FreeBSD.org; Fri, 29 Jan 2021 07:26: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 250784] integer divide fault in zfs_rmnode Date: Fri, 29 Jan 2021 07:26:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: panic, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: stevenschlansker@gmail.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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 07:26:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250784 --- Comment #11 from Steven Schlansker --- I can confirm, the patch that Xin supplied on freebsd-fs clears this issue = up entirely for us. Thank you! --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Jan 29 07:29:37 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DE5144E01F6 for ; Fri, 29 Jan 2021 07:29:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DRprK5mSnz4T9s for ; Fri, 29 Jan 2021 07:29:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id C42104FFFF6; Fri, 29 Jan 2021 07:29:37 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C3E834E03B8 for ; Fri, 29 Jan 2021 07:29:37 +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 4DRprK57Cdz4T5J for ; Fri, 29 Jan 2021 07:29:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9CEB21EB8F for ; Fri, 29 Jan 2021 07:29:37 +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 10T7TbK8064014 for ; Fri, 29 Jan 2021 07:29:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10T7TbJ2064013 for fs@FreeBSD.org; Fri, 29 Jan 2021 07:29:37 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 253063] Hanging zfs processes after upgrade from 12.1 to 12.2-stable Date: Fri, 29 Jan 2021 07:29:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugs@virtualtec.ch X-Bugzilla-Status: New 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 07:29:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253063 --- Comment #3 from Markus Wild --- Seeing the recent FreeBSD-EN-21:04.zfs advisory about changes to zfs receive, could this have caused different locking behavior, somehow causing deadlocks on a busy system? My 12.2-STABLE system is post this patc= h. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Jan 29 15:24:51 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2E3A34EF262 for ; Fri, 29 Jan 2021 15:24:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DS1Ng0dnfz3H9w for ; Fri, 29 Jan 2021 15:24:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 15E654EF2C9; Fri, 29 Jan 2021 15:24:51 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 15B304EF581 for ; Fri, 29 Jan 2021 15:24:51 +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 4DS1Ng04Xyz3HD9 for ; Fri, 29 Jan 2021 15:24:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E9DD724C5E for ; Fri, 29 Jan 2021 15:24:50 +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 10TFOoVk028961 for ; Fri, 29 Jan 2021 15:24:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10TFOo2N028960 for fs@FreeBSD.org; Fri, 29 Jan 2021 15:24:50 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 253079] assert panic when mounting smb share Date: Fri, 29 Jan 2021 15:24:51 +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: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords assigned_to 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 15:24:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253079 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |panic Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Jan 29 20:10:34 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ED0EE4F810B for ; Fri, 29 Jan 2021 20:10:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DS7kJ0K0Vz3shv for ; Fri, 29 Jan 2021 20:10:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 65D014F7F80; Fri, 29 Jan 2021 20:10:29 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5FBE24F7DA4 for ; Fri, 29 Jan 2021 20:10:29 +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 4DS7kD54Wnz3sTX for ; Fri, 29 Jan 2021 20:10:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0CCF5A83 for ; Fri, 29 Jan 2021 20:10:25 +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 10TKAOcp085687 for ; Fri, 29 Jan 2021 20:10:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10TKAOdA085686 for fs@FreeBSD.org; Fri, 29 Jan 2021 20:10: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 244089] lsextattr on a specific UFS file locks system Date: Fri, 29 Jan 2021 20:10:22 +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: 11.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 20:10:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244089 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Jan 29 20:12:17 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B57E84F7DEA for ; Fri, 29 Jan 2021 20:12:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DS7mK4b3Mz3ssb for ; Fri, 29 Jan 2021 20:12:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 9D5404F7DE9; Fri, 29 Jan 2021 20:12:17 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9D19A4F7D51 for ; Fri, 29 Jan 2021 20:12:17 +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 4DS7mK40gjz3skN for ; Fri, 29 Jan 2021 20:12:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7CA6D94F for ; Fri, 29 Jan 2021 20:12:17 +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 10TKCH7M091080 for ; Fri, 29 Jan 2021 20:12:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10TKCH3K091069 for fs@FreeBSD.org; Fri, 29 Jan 2021 20:12:17 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 244089] lsextattr on a specific UFS file locks system Date: Fri, 29 Jan 2021 20:12:17 +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: 11.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 20:12:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244089 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --- Comment #10 from Ed Maste --- Thank you for your report and investigation! The source of the corruption is now fixed in all supported branches. As it stands the robustness improvemen= ts will appear in 12.3 and 13.0. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Jan 29 21:58:38 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AC5114FA745 for ; Fri, 29 Jan 2021 21:58:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DSB724K17z4TTn for ; Fri, 29 Jan 2021 21:58:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 923E84FA5FC; Fri, 29 Jan 2021 21:58:38 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 920554FA81D for ; Fri, 29 Jan 2021 21:58: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 4DSB723gZCz4Tfb for ; Fri, 29 Jan 2021 21:58:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 70F1A2011 for ; Fri, 29 Jan 2021 21:58: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 10TLwc66050653 for ; Fri, 29 Jan 2021 21:58:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10TLwc5t050652 for fs@FreeBSD.org; Fri, 29 Jan 2021 21:58: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 244089] lsextattr on a specific UFS file locks system Date: Fri, 29 Jan 2021 21:58:37 +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: 11.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cem@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: 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 21:58:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244089 --- Comment #11 from Conrad Meyer --- (In reply to Ed Maste from comment #10) Big +1, thanks Andrea for the report and investigation. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Jan 30 00:25:15 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 508134FDE89; Sat, 30 Jan 2021 00:25:15 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (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 "anubis.delphij.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DSFNB27tVz4ddx; Sat, 30 Jan 2021 00:25:14 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from odin.corp.delphij.net (unknown [IPv6:2601:646:8601:f4a:24cb:affb:858d:bf92]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id E5EEF3A73C; Fri, 29 Jan 2021 16:25:06 -0800 (PST) Reply-To: d@delphij.net To: Kurt Jaeger , freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: From: Xin Li Subject: Re: zpool upgrade to draid feature: does it require updated zfs boot code ? Message-ID: <7a2b946a-636c-5aae-1129-adbf73168b70@delphij.net> Date: Fri, 29 Jan 2021 16:25:05 -0800 User-Agent: Thunderbird MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="hWrMO7rPhdsDJYLDGUj3G9Xg1c1c7Paj8" X-Rspamd-Queue-Id: 4DSFNB27tVz4ddx X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.09 / 15.00]; HAS_REPLYTO(0.00)[d@delphij.net]; RCVD_VIA_SMTP_AUTH(0.00)[]; XM_UA_NO_VERSION(0.01)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:sirius.delphij.net]; HAS_ATTACHMENT(0.00)[]; DKIM_TRACE(0.00)[delphij.net:+]; DMARC_POLICY_ALLOW(-0.50)[delphij.net,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:1:117::25:from]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[delphij.net:s=m7e2]; FREEFALL_USER(0.00)[delphij]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; REPLYTO_DOM_EQ_FROM_DOM(0.00)[]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2001:470:1:117::25:from:127.0.2.255]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jan 2021 00:25:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hWrMO7rPhdsDJYLDGUj3G9Xg1c1c7Paj8 Content-Type: multipart/mixed; boundary="RXtbqnI58ptDH0mlteTjkRmHln3IJszCs"; protected-headers="v1" From: Xin Li Reply-To: d@delphij.net To: Kurt Jaeger , freebsd-current@freebsd.org, freebsd-fs@freebsd.org Message-ID: <7a2b946a-636c-5aae-1129-adbf73168b70@delphij.net> Subject: Re: zpool upgrade to draid feature: does it require updated zfs boot code ? References: In-Reply-To: --RXtbqnI58ptDH0mlteTjkRmHln3IJszCs Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 1/28/21 11:00, Kurt Jaeger wrote: > Hi! >=20 > Short question: >=20 > Does a zpool upgrade on 14.0 (current) for the draid feature > require a boot code update ? >=20 > Long version of the same question: [...] > With the draid update, no message was displayed. >=20 > Does it require the bootcode update anyway or, if not, why not ? This sounded like a bug. Is it your boot pool, or just a regular data po= ol? > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd0 > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd1 To answer your short question: do I need to update bootcode? No if draid is the only feature that you have enabled on an existing pool, but personally I don't recommend upgrading boot pool right now. The reason for that "No" answer is 1) the boot code do not currently support draid, and 2) enabling the feature won't activate it until draid vdev is added to the pool, which is quite unlikely in your case; note that if you do add draid vdev, your bootcode won't be able to boot from it anymore. On my personal laptop, old bootcode would boot pool with draid enabled but not activated just fine (note that the loader.efi on -CURRENT won't boot my P51, which I will start a separate discussion; I used FreeBSD-13.0-CURRENT-amd64-20201231-282381aa53a-255460-memstick.img and fixed my EFI loader and it worked fine with the draid-enabled boot ZFS pool). Hope this helps. Cheers, --RXtbqnI58ptDH0mlteTjkRmHln3IJszCs-- --hWrMO7rPhdsDJYLDGUj3G9Xg1c1c7Paj8 Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEceNg5NEMZIki80nQQHl/fJX0g08FAmAUp2EFAwAAAAAACgkQQHl/fJX0g089 WQ//Uhbo4p3dC3A3D+cbueizilJTEWTSs2i+XhurP2AtlYYlxZPm0JfQA5qnxwAojM3qR+DSc2jK 7ccJk6ThpnoVCb3dd/dOInrgFC0EMjtqr7oeM7hkXTYiQfihSMYx/ZAZzDcFdazxLAwpCC8jHMxa fwxfGFM8sRBQMxwqahCZ/CCxm4AslI4bYykIrFvNZ/kC0kQdxUrD1cl4vIUIn33/vbQ/RKlVbsw1 Nr17js16bBs2FNlGzgng2YahdHzZl915W2iDb1rlYa/kVh2NJYD9oaygzGZl3yOz7N379W4IgMI8 S7CKG6th9xN70evmVNoSaQpZe2tNIcchcojST0Qtpg4Vtd7f+cFeMn5Ze9KBZ54OPBQqYqG5ElVq J+MQxhRY6/TVo5mFgLN5b5q9TmGUTCztZUp6uIX4NaRDS5QTzF7B/mDoKHpDUC8sF/8D2tm8l3iU nbkQqbzuT9lQ79UGnj1LA04CQ2MKas+D1QULqsCO96pKLr+Y2o2dvrWlYqQdNcXAMl0OyPopY2Qt sKcsf+kXX6UWch7wYzGoIsIQgHSnONhLbpRvDlEUn2eEqAc+CyFO/DWtDH7JSVzn5tWT0RczWP6y 0e2FEAWgeEGJhxpfrz/73jxgxL+yg6CLOjUOe7O2EK18I96lwYl+zbEmUUIHgUEr3j399bUxYbEt UD4= =Ka1L -----END PGP SIGNATURE----- --hWrMO7rPhdsDJYLDGUj3G9Xg1c1c7Paj8-- From owner-freebsd-fs@freebsd.org Sat Jan 30 06:34:48 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7C57552692B for ; Sat, 30 Jan 2021 06:34:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DSPZc2jNQz3FYK for ; Sat, 30 Jan 2021 06:34:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 5CE7A52692A; Sat, 30 Jan 2021 06:34:48 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5CB2E526F0A for ; Sat, 30 Jan 2021 06:34:48 +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 4DSPZc1ygcz3F4V for ; Sat, 30 Jan 2021 06:34:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 32CD0110C9 for ; Sat, 30 Jan 2021 06:34:48 +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 10U6YmRC034671 for ; Sat, 30 Jan 2021 06:34:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10U6YmJg034670 for fs@FreeBSD.org; Sat, 30 Jan 2021 06:34:48 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 252240] "zfs send -R -I | zfs receive -F" not destroying snapshots that don't exist on the sending side Date: Sat, 30 Jan 2021 06:34:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: john@sanren.ac.za X-Bugzilla-Status: New 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jan 2021 06:34:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252240 --- Comment #3 from John Hay --- This has been fixed for me in 12.2-RELEASE-p3. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Jan 30 11:14:11 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8C4744E7217; Sat, 30 Jan 2021 11:14:11 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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 4DSWmz1RjGz3m34; Sat, 30 Jan 2021 11:14:11 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.94 (FreeBSD)) (envelope-from ) id 1l5oCW-000LPM-0i; Sat, 30 Jan 2021 12:14:00 +0100 Date: Sat, 30 Jan 2021 12:14:00 +0100 From: Kurt Jaeger To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, Xin Li Subject: Re: zpool upgrade to draid feature: does it require updated zfs boot code ? Message-ID: References: <7a2b946a-636c-5aae-1129-adbf73168b70@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7a2b946a-636c-5aae-1129-adbf73168b70@delphij.net> X-Rspamd-Queue-Id: 4DSWmz1RjGz3m34 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jan 2021 11:14:11 -0000 Hi! > > Short question: > > Does a zpool upgrade on 14.0 (current) for the draid feature > > require a boot code update ? > > Long version of the same question: > > With the draid update, no message was displayed. > > > > Does it require the bootcode update anyway or, if not, why not ? > > This sounded like a bug. Is it your boot pool, or just a regular data pool? Its my boot pool. > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd0 > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd1 > > To answer your short question: do I need to update bootcode? No if > draid is the only feature that you have enabled on an existing pool, but > personally I don't recommend upgrading boot pool right now. The boot pool shows: zroot feature@draid enabled local > The reason for that "No" answer is 1) the boot code do not currently > support draid, and 2) enabling the feature won't activate it until draid > vdev is added to the pool, which is quite unlikely in your case; note > that if you do add draid vdev, your bootcode won't be able to boot from > it anymore. Ok. -- pi@opsec.eu +49 171 3101372 Now what ? From owner-freebsd-fs@freebsd.org Sat Jan 30 16:22:52 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A08EF4F1F11 for ; Sat, 30 Jan 2021 16:22:52 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DSfd75Dvpz4l5j for ; Sat, 30 Jan 2021 16:22:50 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id D0DF78D4A320 for ; Sat, 30 Jan 2021 16:22:42 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 2F2DDE707D8 for ; Sat, 30 Jan 2021 16:22:42 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id Drw4n83lAgST for ; Sat, 30 Jan 2021 16:22:40 +0000 (UTC) Received: from [127.0.0.1] (unknown [IPv6:fde9:577b:c1a9:4902:ddc0:5fd7:79e3:c774]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 38156E707C2 for ; Sat, 30 Jan 2021 16:22:40 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd-fs@freebsd.org Subject: UFS (softdep) deadlock(?) Date: Sat, 30 Jan 2021 16:22:39 +0000 X-Mailer: MailMate (2.0BETAr6151) Message-ID: <24264795-C05C-433C-A57E-87869EA6F0EE@lists.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4DSfd75Dvpz4l5j X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2a01:4f8:13b:39f::9f:25 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:13b:39f::9f:25:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:39f::9f:25]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a01:4f8:13b:39f::9f:25:from:127.0.2.255]; DMARC_NA(0.00)[zabbadoz.net]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_TLS_LAST(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jan 2021 16:22:52 -0000 Hi, while building some packages on arm64/HEAD (this is recursively so don’t ask me how it got there): .. ===> Building for libmspack-0.10.1 I was wondering so I checked on serial console and found this: 65634 1 DN 1:15.69 mkdir mspack/.libs 65640 1 DN 1:16.12 mkdir mspack/.libs 65650 1 DN 1:15.18 mkdir mspack/.libs 65651 1 DN 1:16.31 mkdir mspack/.libs 65652 1 DN 1:15.22 mkdir mspack/.libs 65653 1 DN 1:16.11 mkdir mspack/.libs 65654 1 DN 1:15.13 mkdir mspack/.libs 65705 1 DN 1:15.04 mkdir mspack/.libs 65706 1 DN 1:15.22 mkdir mspack/.libs 65707 1 DN 1:15.87 mkdir mspack/.libs 65708 1 DN 1:15.71 mkdir mspack/.libs 65709 1 DN 1:15.64 mkdir mspack/.libs 65710 1 DN 1:16.39 mkdir mspack/.libs 65711 1 DN 1:15.65 mkdir mspack/.libs 65712 1 DN 1:14.97 mkdir mspack/.libs 65713 1 DN 1:15.04 mkdir mspack/.libs PID TID COMM TDNAME KSTACK 65634 101149 mkdir - mi_switch sleeplk lockmgr_xlock_hard ffs_lock vn_lock_pair softdep_prelink ufs_mkdir VOP_MKDIR_APV kern_mkdirat do_el0_sync handle_el0_sync 65640 101134 mkdir - mi_switch sleeplk lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync 65650 101099 mkdir - 65651 101174 mkdir - 65652 197951 mkdir - 65653 102615 mkdir - mi_switch sleeplk lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync 65654 101140 mkdir - mi_switch sleeplk lockmgr_xlock_hard ffs_lock vn_lock_pair softdep_prelink ufs_mkdir VOP_MKDIR_APV kern_mkdirat do_el0_sync handle_el0_sync 65705 116563 mkdir - mi_switch sleeplk lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync 65706 117852 mkdir - mi_switch sleeplk lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync 65707 101101 mkdir - mi_switch sleeplk lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync 65708 100214 mkdir - mi_switch sleeplk lockmgr_xlock_hard ffs_lock vn_lock_pair softdep_prelink ufs_mkdir VOP_MKDIR_APV kern_mkdirat do_el0_sync handle_el0_sync 65709 105512 mkdir - 65710 101203 mkdir - mi_switch sleeplk lockmgr_xlock_hard ffs_lock _vn_lock lookup namei kern_mkdirat do_el0_sync handle_el0_sync 65711 100180 mkdir - 65712 100218 mkdir - mi_switch sleeplk lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync 65713 100141 mkdir - mi_switch sleeplk lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync I’ll probably have to reboot to get out of this but I’ll let it sit for a few minutes in case someone has questions. /bz From owner-freebsd-fs@freebsd.org Sat Jan 30 18:32:20 2021 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 104C14F5536 for ; Sat, 30 Jan 2021 18:32:20 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DSjVW1NnSz4tkC for ; Sat, 30 Jan 2021 18:32:18 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id DC7F28D4A319 for ; Sat, 30 Jan 2021 18:32:16 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id D048FE707CB for ; Sat, 30 Jan 2021 18:32:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id f_Xj0Cg3Ultd for ; Sat, 30 Jan 2021 18:32:13 +0000 (UTC) Received: from [127.0.0.1] (unknown [IPv6:fde9:577b:c1a9:4902:ddc0:5fd7:79e3:c774]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id B7A17E707C2 for ; Sat, 30 Jan 2021 18:32:13 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd-fs@freebsd.org Subject: Re: UFS (softdep) deadlock(?) Date: Sat, 30 Jan 2021 18:32:12 +0000 X-Mailer: MailMate (2.0BETAr6151) Message-ID: In-Reply-To: <24264795-C05C-433C-A57E-87869EA6F0EE@lists.zabbadoz.net> References: <24264795-C05C-433C-A57E-87869EA6F0EE@lists.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4DSjVW1NnSz4tkC X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2a01:4f8:13b:39f::9f:25 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:13b:39f::9f:25:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:39f::9f:25]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2a01:4f8:13b:39f::9f:25:from:127.0.2.255]; DMARC_NA(0.00)[zabbadoz.net]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_TLS_LAST(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jan 2021 18:32:20 -0000 On 30 Jan 2021, at 16:22, Bjoern A. Zeeb wrote: > Hi, > > while building some packages on arm64/HEAD (this is recursively so > don’t ask me how it got there): > > .. > ===> Building for libmspack-0.10.1 > > > I was wondering so I checked on serial console and found this: > > 65634 1 DN 1:15.69 mkdir mspack/.libs > 65640 1 DN 1:16.12 mkdir mspack/.libs > 65650 1 DN 1:15.18 mkdir mspack/.libs > 65651 1 DN 1:16.31 mkdir mspack/.libs > 65652 1 DN 1:15.22 mkdir mspack/.libs > 65653 1 DN 1:16.11 mkdir mspack/.libs > 65654 1 DN 1:15.13 mkdir mspack/.libs > 65705 1 DN 1:15.04 mkdir mspack/.libs > 65706 1 DN 1:15.22 mkdir mspack/.libs > 65707 1 DN 1:15.87 mkdir mspack/.libs > 65708 1 DN 1:15.71 mkdir mspack/.libs > 65709 1 DN 1:15.64 mkdir mspack/.libs > 65710 1 DN 1:16.39 mkdir mspack/.libs > 65711 1 DN 1:15.65 mkdir mspack/.libs > 65712 1 DN 1:14.97 mkdir mspack/.libs > 65713 1 DN 1:15.04 mkdir mspack/.libs > > > PID TID COMM TDNAME KSTACK > 65634 101149 mkdir - mi_switch sleeplk > lockmgr_xlock_hard ffs_lock vn_lock_pair softdep_prelink ufs_mkdir > VOP_MKDIR_APV kern_mkdirat do_el0_sync handle_el0_sync > 65640 101134 mkdir - mi_switch sleeplk > lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup > vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync > 65650 101099 mkdir - > 65651 101174 mkdir - > 65652 197951 mkdir - > 65653 102615 mkdir - mi_switch sleeplk > lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup > vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync > 65654 101140 mkdir - mi_switch sleeplk > lockmgr_xlock_hard ffs_lock vn_lock_pair softdep_prelink ufs_mkdir > VOP_MKDIR_APV kern_mkdirat do_el0_sync handle_el0_sync > 65705 116563 mkdir - mi_switch sleeplk > lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup > vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync > 65706 117852 mkdir - mi_switch sleeplk > lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup > vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync > 65707 101101 mkdir - mi_switch sleeplk > lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup > vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync > 65708 100214 mkdir - mi_switch sleeplk > lockmgr_xlock_hard ffs_lock vn_lock_pair softdep_prelink ufs_mkdir > VOP_MKDIR_APV kern_mkdirat do_el0_sync handle_el0_sync > 65709 105512 mkdir - > 65710 101203 mkdir - mi_switch sleeplk > lockmgr_xlock_hard ffs_lock _vn_lock lookup namei kern_mkdirat > do_el0_sync handle_el0_sync > 65711 100180 mkdir - > 65712 100218 mkdir - mi_switch sleeplk > lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup > vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync > 65713 100141 mkdir - mi_switch sleeplk > lockmgr_slock_hard ffs_lock _vn_lock vget_finish cache_lookup > vfs_cache_lookup lookup namei kern_mkdirat do_el0_sync handle_el0_sync > > > I’ll probably have to reboot to get out of this but I’ll let it > sit for a few minutes in case someone has questions. was wise to let it there.. wasn’t completely deadlocked. It cleared up after a loooong while. In case anyone has any insights, I’ll be happy to try to repro (or the package build may in a minute anyway). /bz