From owner-freebsd-fs@freebsd.org Sun Oct 7 20:26:25 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 474D010CBA7D for ; Sun, 7 Oct 2018 20:26:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D914A930EB for ; Sun, 7 Oct 2018 20:26:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9CEB310CBA7C; Sun, 7 Oct 2018 20:26:24 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B9BB10CBA7B for ; Sun, 7 Oct 2018 20:26:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D414930E9 for ; Sun, 7 Oct 2018 20:26:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7A9111D907 for ; Sun, 7 Oct 2018 20:26:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w97KQNlR095662 for ; Sun, 7 Oct 2018 20: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 w97KQN5e095661 for fs@FreeBSD.org; Sun, 7 Oct 2018 20: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 229614] ZFS lockup in zil_commit_impl Date: Sun, 07 Oct 2018 20:26: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.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: allanjude@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2018 20:26:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 Allan Jude changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --- Comment #21 from Allan Jude --- This patch has been tested in my reproduction setup and prevents the hang. I am not confident in the lack of locking before reading zp->z_unlinked yet though. Waiting on review from those more familiar with VFS locking than myself. However, if you feel comfortable testing this patch, please do: https://reviews.freebsd.org/D17460 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 7 21:01:19 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8287410CC8E2 for ; Sun, 7 Oct 2018 21:01:19 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2C9F39432F for ; Sun, 7 Oct 2018 21:01:19 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id E59F610CC8CC; Sun, 7 Oct 2018 21:01:18 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3F1810CC8CA for ; Sun, 7 Oct 2018 21:01:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84E769431F for ; Sun, 7 Oct 2018 21:01:18 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id BA6CE1DE5E for ; Sun, 7 Oct 2018 21:01:17 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w97L1Hoh084386 for ; Sun, 7 Oct 2018 21:01:17 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w97L1H3G084381 for fs@FreeBSD.org; Sun, 7 Oct 2018 21:01:17 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201810072101.w97L1H3G084381@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, 7 Oct 2018 21:01:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2018 21:01:19 -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 New | 217062 | for file systems mounted with -o noexec, exec=off New | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Oct 8 22:36:00 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8ACD810CE21D for ; Mon, 8 Oct 2018 22:36:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2881E82DA9 for ; Mon, 8 Oct 2018 22:36:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E0EED10CE21C; Mon, 8 Oct 2018 22:35:59 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFD9B10CE21B for ; Mon, 8 Oct 2018 22:35:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7278182DA4 for ; Mon, 8 Oct 2018 22:35:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D0D5F3477 for ; Mon, 8 Oct 2018 22:35:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w98MZwX9083152 for ; Mon, 8 Oct 2018 22:35:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w98MZwm2083149 for fs@FreeBSD.org; Mon, 8 Oct 2018 22:35:58 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 229614] ZFS lockup in zil_commit_impl Date: Mon, 08 Oct 2018 22:35:54 +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.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: simon@zethos.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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2018 22:36:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 Simon Coggins changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon@zethos.org --- Comment #22 from Simon Coggins --- I've just recently upgraded my HPE Microserver Gen8 to 11.2 ( bare metal) a= nd I appear to be consistently hitting this bug every night during backups.=20 Testing the patch now to see if it helps my issue. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 9 15:50:06 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D63AA10B0FB6 for ; Tue, 9 Oct 2018 15:50:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6EDA08EFFC for ; Tue, 9 Oct 2018 15:50:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 304FB10B0FB0; Tue, 9 Oct 2018 15:50:06 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E4BA10B0FAE for ; Tue, 9 Oct 2018 15:50:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B10D88EFF9 for ; Tue, 9 Oct 2018 15:50:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EDE5B14B06 for ; Tue, 9 Oct 2018 15:50:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w99Fo4ee001616 for ; Tue, 9 Oct 2018 15:50:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w99Fo4Xu001615 for fs@FreeBSD.org; Tue, 9 Oct 2018 15:50: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 231251] [ZFS assfail] 12-ALPHA5 r338529 panic Date: Tue, 09 Oct 2018 15:50:04 +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: 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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 15:50:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231251 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linimon@FreeBSD.org --- Comment #12 from Mark Linimon --- Is this a regression from an earlier install, or is this a new install? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 9 20:49:32 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88AD910BC457 for ; Tue, 9 Oct 2018 20:49:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 25B657C72C for ; Tue, 9 Oct 2018 20:49:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DEBD910BC453; Tue, 9 Oct 2018 20:49:31 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD6BC10BC452 for ; Tue, 9 Oct 2018 20:49:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E6C67C725 for ; Tue, 9 Oct 2018 20:49:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A3C90174C8 for ; Tue, 9 Oct 2018 20:49:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w99KnU4A010110 for ; Tue, 9 Oct 2018 20:49:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w99KnUNX010109 for fs@FreeBSD.org; Tue, 9 Oct 2018 20:49:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 231251] [ZFS assfail] 12-ALPHA5 r338529 panic Date: Tue, 09 Oct 2018 20:49:30 +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: gldisater@gmail.com 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 20:49:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231251 --- Comment #13 from Jeremy Faulkner --- This system was upgraded from 11.2-RELENG branch to 12-ALPHA by cloning the boot environment, and then building from source. I forget exactly which ALP= HA 4, or 5 but it's currently at 8. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 9 20:55:41 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDA5210BC9F0 for ; Tue, 9 Oct 2018 20:55:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7AE9E7D099 for ; Tue, 9 Oct 2018 20:55:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3F8EF10BC9EF; Tue, 9 Oct 2018 20:55:41 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E1CA10BC9EE for ; Tue, 9 Oct 2018 20:55:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C41277D094 for ; Tue, 9 Oct 2018 20:55:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1D61617640 for ; Tue, 9 Oct 2018 20:55:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w99Ktdqu026087 for ; Tue, 9 Oct 2018 20:55:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w99Ktdd6026086 for fs@FreeBSD.org; Tue, 9 Oct 2018 20:55:39 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 231251] [ZFS assfail] 12-ALPHA5 r338529 panic Date: Tue, 09 Oct 2018 20:55:40 +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: 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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 20:55:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231251 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 9 21:21:31 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7CEF10BDADC for ; Tue, 9 Oct 2018 21:21:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4429D7E8CE for ; Tue, 9 Oct 2018 21:21:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 08C9210BDADB; Tue, 9 Oct 2018 21:21:31 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBD4310BDADA for ; Tue, 9 Oct 2018 21:21:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B5C77E8CB for ; Tue, 9 Oct 2018 21:21:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E34CD17A4B for ; Tue, 9 Oct 2018 21:21:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w99LLT9h089563 for ; Tue, 9 Oct 2018 21:21:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w99LLTgJ089562 for fs@FreeBSD.org; Tue, 9 Oct 2018 21:21:29 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 220105] boot1.efi does not detect ZFS pools on whole disks Date: Tue, 09 Oct 2018 21:21:29 +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: 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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 21:21:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220105 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linimon@FreeBSD.org --- Comment #3 from Mark Linimon --- Is this still a problem on 12-ALPHA? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 00:06:26 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2F7010C2DA1 for ; Wed, 10 Oct 2018 00:06:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7A82585AA0 for ; Wed, 10 Oct 2018 00:06:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3BB4D10C2D9B; Wed, 10 Oct 2018 00:06:25 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A61410C2D9A for ; Wed, 10 Oct 2018 00:06:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6475985A8B for ; Wed, 10 Oct 2018 00:06:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id AAEDF19144 for ; Wed, 10 Oct 2018 00:06:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9A06Ni4019464 for ; Wed, 10 Oct 2018 00:06:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9A06N1l019452 for fs@FreeBSD.org; Wed, 10 Oct 2018 00:06: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 229007] [zfs] kernel crashes on remove disk Date: Wed, 10 Oct 2018 00:06:23 +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 Some People X-Bugzilla-Who: gldisater@gmail.com 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 00:06:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 --- Comment #4 from Jeremy Faulkner --- October 2018 OpenZFS Leadership Meeting listed mav@ as maintainer for zfs device removal. CC'd --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 02:26:10 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C45210C554E for ; Wed, 10 Oct 2018 02:26:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 04F468AA9F for ; Wed, 10 Oct 2018 02:26:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id BA34910C554D; Wed, 10 Oct 2018 02:26:09 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9636410C554C for ; Wed, 10 Oct 2018 02:26:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 29BAF8AA9A for ; Wed, 10 Oct 2018 02:26:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6E6E71A4B9 for ; Wed, 10 Oct 2018 02:26:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9A2Q8Zl084349 for ; Wed, 10 Oct 2018 02:26:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9A2Q8Ok084344 for fs@FreeBSD.org; Wed, 10 Oct 2018 02:26: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 229007] [zfs] kernel crashes on remove disk Date: Wed, 10 Oct 2018 02:26:07 +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 Some People X-Bugzilla-Who: allanjude@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 02:26:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 --- Comment #5 from Allan Jude --- I crashed differently. Fatal trap 9: general protection fault while in kernel mode cpuid =3D 3; apic id =3D 03 instruction pointer =3D 0x20:0xffffffff827ccc3f stack pointer =3D 0x28:0xfffffe002d962390 frame pointer =3D 0x28:0xfffffe002d962390 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (zio_write_issue_1) #10 0xffffffff827ccc3f in vdev_queue_offset_compare (x1=3D0xfffff800843ea83= 0, x2=3D0xdeadc0dedeadbe8e) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:320 z1 =3D 0xfffff800843ea830 z2 =3D 0xdeadc0dedeadbe8e cmp =3D #11 0xffffffff826fc174 in avl_find (tree=3D0xfffff80005f28740, value=3D0xfffff800843ea830, where=3D) at /usr/src/sys/cddl/contrib/opensolaris/common/avl/avl.c:268 node =3D 0xfffff80003d98a80 off =3D 592 prev =3D 0xdeadc0dedeadc0de diff =3D #12 avl_add (tree=3D0xfffff80005f28740, new_node=3D0xfffff800843ea830) at /usr/src/sys/cddl/contrib/opensolaris/common/avl/avl.c:644 where =3D #13 0xffffffff827cdbbc in vdev_queue_pending_add (vq=3D0xfffff80005f285b8, zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:472 spa =3D __right =3D __left =3D and Fatal trap 9: general protection fault while in kernel mode cpuid =3D 1; apic id =3D 01 instruction pointer =3D 0x20:0xffffffff826fbd1f stack pointer =3D 0x28:0xfffffe002d8e09d8 frame pointer =3D 0x28:0xfffffe002d8e0a10 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (zio_write_intr_3) #10 0xffffffff826fbd1f in avl_rotation (tree=3D0xfffff8000d01f740, node=3D0xfffff80003d8b668, balance=3D) at /usr/src/sys/cddl/contrib/opensolaris/common/avl/avl.c:379 right =3D 0 left =3D left_heavy =3D right_heavy =3D parent =3D 0xdeadc0dedeadc0d8 child =3D 0xfffff80003dd9250 which_child =3D 1 child_bal =3D -1 gchild =3D gleft =3D gright =3D cright =3D 0x0 #11 0xffffffff826fc3e3 in avl_remove (tree=3D0xfffff8000d01f740, data=3D0xfffff80006fd4830) at /usr/src/sys/cddl/contrib/opensolaris/common/avl/avl.c:818 off =3D delete =3D left =3D right =3D node =3D 0xdeadc0dedeadc0d8 parent =3D 0xfffff80003d8b668 which_child =3D old_balance =3D new_balance =3D 0 tmp =3D #12 0xffffffff827cdd42 in vdev_queue_pending_remove (vq=3D0xfffff8000d01f5b= 8, zio=3D0xfffff80006fd4830) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:490 spa =3D __right =3D __left =3D #13 vdev_queue_io_done (zio=3D0xfffff80006fd4830) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:937 vq =3D 0xfffff8000d01f5b8 nio =3D #14 0xffffffff827fe7f1 in zio_vdev_io_done (zio=3D0xfffff80006fd4830) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3366 vd =3D 0xfffff8000d01f000 unexpected_error =3D ops =3D #15 0xffffffff827f903c in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1784 pipeline =3D stage =3D --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 09:15:37 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09A1910CDA8B for ; Wed, 10 Oct 2018 09:15:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9CE2375DBF for ; Wed, 10 Oct 2018 09:15:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5DF0410CDA8A; Wed, 10 Oct 2018 09:15:36 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C8D410CDA89 for ; Wed, 10 Oct 2018 09:15:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2F5475DBE for ; Wed, 10 Oct 2018 09:15:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 35F301DD74 for ; Wed, 10 Oct 2018 09:15:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9A9FZpL067096 for ; Wed, 10 Oct 2018 09:15:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9A9FZ90067093 for fs@FreeBSD.org; Wed, 10 Oct 2018 09:15:35 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 220105] boot1.efi does not detect ZFS pools on whole disks Date: Wed, 10 Oct 2018 09:15:32 +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: tech-lists@zyxst.net 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 09:15:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220105 tech-lists@zyxst.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tech-lists@zyxst.net --- Comment #4 from tech-lists@zyxst.net --- yes this still happens on 12.0-ALPHA8 r339251 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 15:15:36 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3116A10B3BD6 for ; Wed, 10 Oct 2018 15:15:36 +0000 (UTC) (envelope-from felix@audiofair.de) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD84F84806 for ; Wed, 10 Oct 2018 15:15:35 +0000 (UTC) (envelope-from felix@audiofair.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1539184533; s=strato-dkim-0002; d=audiofair.de; h=In-Reply-To:Date:Message-ID:From:References:To:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=HKQFcMfv9xZQe6cnHhA6wq2fmVTmEWtmKzdU5LALYco=; b=KkC6lavqjtx/BteCzA0U7uyzKtEAoroKLQTpfEYimnFd/U/sOyCN8H5cfkLubWLdBe HnWC2wRyYA54lQEas+8o+idnf0mcGwgAMQ1aQAw1UN9vhDaVAy18rZRsw38I6qwOpwdd gMSOc8yKYg4/UbqaiEl4ifQ63W09Dajm7ukufKAqsm4Lo02L4b0CMQp7jUo3netAVxkW aRrcu6hogPQpvZrmCbKzd7RAs9hbo5AV6h791CAs9k3AdrUKN4qhy7NUMK48jdiDao1f 1m2+VdIZ6MOYpiLCANEbkC0oyHfGkBfscEC3xZWYzPGudqPebxRRxFZGt1Rps5ZZEC8B MC7A== X-RZG-AUTH: ":KmkIfFiIeuobF0ryGDOmdGJTFqaolieRUBb8W7m+IlV8fTgVa1I1Nqqo7krB5f1Lh7qYsj9h" X-RZG-CLASS-ID: mo00 Received: from [131.188.166.118] by smtp.strato.de (RZmta 44.2 AUTH) with ESMTPSA id k02759u9AFFVUsy (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Wed, 10 Oct 2018 17:15:31 +0200 (CEST) Subject: Re: NFSv4 Kerberos mount from Linux To: Rick Macklem , "freebsd-fs@freebsd.org" References: <30f6446c-6fed-4b1e-9cae-9c417974ec46@audiofair.de> From: Felix Winterhalter Message-ID: Date: Wed, 10 Oct 2018 17:15:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: de-DE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 15:15:36 -0000 On 10/4/18 5:21 PM, Rick Macklem wrote: > Felix Winterhalter wrote: >> Hello everyone, >> >> I've been trying to get a kerberized nfsv4 mount to work from a Debian >> Stretch client to a FreeBSD 11.2 server. >> >> My export file looks like: >> >> V4: / -sec=krb5p clients >> >> /testexport -maproot=root -sec=krb5p clients >> > Btw, if you only mounting "/testexport", you can specify the "V4:" as > V4: /testexport -sec=krb5p clients > and then the mount on the client uses "/" as the server mountpoint, like > # mount -t nfs -o nfsvers=4 :/ /mnt > (This avoids the server having to search for "testexport" in the "/" directory > during mounting and might avoid some problems when "/" isn't an exported > file system. There are "hooks" in the FreeBSD server to make the search work, > but I've never been 100% certain they will work for Kerberos and/or ZFS.) > > Btw, in case the Linux client is falling back on using AUTH_SYS at some point > during the mount, you could try allowing both krb5 and auth_sys by setting > "-sec=sys,krb5,krb5i,krb5p" for both of the above lines. (I'd also suggest you > try krb5 or krb5i until you get it working, since any packet traces are > easier to decode, although once one krb5 variant works, they all should.) True, however I had multiple exports below / set up as tests. > >> I am now trying to mount this directory as root first without having to >> deal with user keytabs or tickets. >> >> This works fine with -sec=sys and nfsv4.1 and nfsv3 and -sec=krb5p. >> This does not however work with nfsv4 and krb5p or any other krb5 flavor. > Sorry, I'm not sure what you are saying here. Is it > 1 - no version of NFS works for krb5p or > 2 - NFSv4.1 works for krb5p, but NFSv4.0 does not or > 3 - only nfsv3 works for krb5p [snipped lots of text] #3 is indeed what was happening. I could mount with krb5p for nfsv3 (which I was not aware was even doable) however nfsv4 would stubbornly refuse to do any mounting. I have now after a lot of try and error figured out what I need to do in order to make it work. To start with I have kerberos credentials with both host/ and nfs/ on both client and server. Mounting nfsv4 shares with krb5p from a linux server has also worked in this context. I leave you to judge whether what I found out is intended behaviour or if something weird is going on. My exports file originally looked something like this: /nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=root -sec=krb5p clients V4: /nfsTests -sec=krb5p clients Which allowed me to do nfsv3 krb5p mounts but not nfsv4 krb5p mounts. Changing the exports file to this: /nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=root -sec=krb5p clients V4: /nfsTests -sec=krb5p,krb5i clients Allows nfsv4 krb5p mounts to work for some reason I do not understand. Not setting the -sec option on the V4 line apparently defaults to -sec=sys and doesn't allow any krb5 mounts. I'm not sure that this is a good default as I wasn't even aware that the -sec option needed to be set on this line. I've got packet traces of the nfsv3 krb5 and krb5i mounts and I'll make traces of the two nfsv4 mount attempts and send them to you if you're interested. I'm still not sure what exactly is happening here. From owner-freebsd-fs@freebsd.org Wed Oct 10 16:39:21 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36DA910B5F3D for ; Wed, 10 Oct 2018 16:39:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C517B88500 for ; Wed, 10 Oct 2018 16:39:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 84FF310B5F3C; Wed, 10 Oct 2018 16:39:20 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72FC110B5F3B for ; Wed, 10 Oct 2018 16:39:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 113A5884F8 for ; Wed, 10 Oct 2018 16:39:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3A79421A8E for ; Wed, 10 Oct 2018 16:39:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9AGdJaY072015 for ; Wed, 10 Oct 2018 16:39:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9AGdJG0072014 for fs@FreeBSD.org; Wed, 10 Oct 2018 16:39:19 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 227784] zfs: Fatal trap 9: general protection fault while in kernel mode on shutdown Date: Wed, 10 Oct 2018 16:39:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: panic, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 16:39:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227784 --- Comment #12 from Mark Johnston --- Is this still occurring on recent 12.0-ALPHA builds? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 16:42:55 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0EDA10B61A2 for ; Wed, 10 Oct 2018 16:42:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5607E8887A for ; Wed, 10 Oct 2018 16:42:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 18B6010B61A1; Wed, 10 Oct 2018 16:42:55 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06A2310B619F for ; Wed, 10 Oct 2018 16:42:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 953AD88870 for ; Wed, 10 Oct 2018 16:42:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id DCBDB21C05 for ; Wed, 10 Oct 2018 16:42:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9AGgrMc083638 for ; Wed, 10 Oct 2018 16:42:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9AGgrD6083637 for fs@FreeBSD.org; Wed, 10 Oct 2018 16:42:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 212168] [panic] [UFS] use-after-free panic (0xdeadc0dedeadc0de) Date: Wed, 10 Oct 2018 16:42:52 +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.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: emaste@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: rep_platform 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 16:42:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212168 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Any |arm64 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 17:00:09 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 359AA10B670C for ; Wed, 10 Oct 2018 17:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C6A7688E7F for ; Wed, 10 Oct 2018 17:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8B86F10B670B; Wed, 10 Oct 2018 17:00:08 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A40310B670A for ; Wed, 10 Oct 2018 17:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1757F88E76 for ; Wed, 10 Oct 2018 17:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5E6C721D79 for ; Wed, 10 Oct 2018 17:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9AH07nH013314 for ; Wed, 10 Oct 2018 17:00:07 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9AH0750013313 for fs@FreeBSD.org; Wed, 10 Oct 2018 17:00:07 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 227784] zfs: Fatal trap 9: general protection fault while in kernel mode on shutdown Date: Wed, 10 Oct 2018 17:00: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, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wulf@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 17:00:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227784 --- Comment #13 from Vladimir Kondratyev --- (In reply to Mark Johnston from comment #12) > Is this still occurring on recent 12.0-ALPHA builds? I will try to update my box to latest current and leave it powered for a ni= ght. The bug requires several hours of uptime to be triggered. ALPHA6 is affected by it. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 19:40:55 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50A0B10BA3AE for ; Wed, 10 Oct 2018 19:40:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0E0D28F1EC for ; Wed, 10 Oct 2018 19:40:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C56CF10BA3A5; Wed, 10 Oct 2018 19:40:54 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3F7F10BA3A2 for ; Wed, 10 Oct 2018 19:40:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BAEC8F1D4 for ; Wed, 10 Oct 2018 19:40:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 992CF23514 for ; Wed, 10 Oct 2018 19:40:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9AJerWE096521 for ; Wed, 10 Oct 2018 19:40:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9AJerPA096518 for fs@FreeBSD.org; Wed, 10 Oct 2018 19:40:53 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 229614] ZFS lockup in zil_commit_impl Date: Wed, 10 Oct 2018 19:40: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: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 19:40:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 --- Comment #23 from commit-hook@freebsd.org --- A commit references this bug: Author: allanjude Date: Wed Oct 10 19:39:47 UTC 2018 New revision: 339289 URL: https://svnweb.freebsd.org/changeset/base/339289 Log: Resolve a hang in ZFS during vnode reclaimation This is caused by a deadlock between zil_commit() and zfs_zget() Add a way for zfs_zget() to break out of the retry loop in the common case PR: 229614 Reported by: grembo, Andreas Sommer, many others Tested by: Andreas Sommer, Vicki Pfau Reviewed by: avg (no objection) Approved by: re (gjb) MFC after: 2 months Sponsored by: Klara Systems Differential Revision: https://reviews.freebsd.org/D17460 Changes: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_znode.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 20:32:28 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20A0E10BB4E0 for ; Wed, 10 Oct 2018 20:32:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B188D70D30 for ; Wed, 10 Oct 2018 20:32:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 75C6610BB4DE; Wed, 10 Oct 2018 20:32:27 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6455C10BB4DC for ; Wed, 10 Oct 2018 20:32:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0628970D25 for ; Wed, 10 Oct 2018 20:32:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 4CEB123C5E for ; Wed, 10 Oct 2018 20:32:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9AKWQv5029977 for ; Wed, 10 Oct 2018 20:32:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9AKWQr7029975 for fs@FreeBSD.org; Wed, 10 Oct 2018 20:32:26 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 229614] ZFS lockup in zil_commit_impl Date: Wed, 10 Oct 2018 20:32: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: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: simon@zethos.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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 20:32:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 --- Comment #24 from Simon Coggins --- (In reply to Simon Coggins from comment #22) Please ignore my comment. My issue was ZFS Dedup/ARC/Bhyve memory exhaustion issue. Disabling dedup and destructing mac ARC solved my issue so it was unrelated to this issue/fix. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Oct 10 21:47:08 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EBE510BD699 for ; Wed, 10 Oct 2018 21:47:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670088.outbound.protection.outlook.com [40.107.67.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16AD4734DB for ; Wed, 10 Oct 2018 21:47:07 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM (52.132.44.160) by YTOPR0101MB1561.CANPRD01.PROD.OUTLOOK.COM (52.132.50.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.22; Wed, 10 Oct 2018 21:47:06 +0000 Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::65af:417a:161f:f4eb]) by YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::65af:417a:161f:f4eb%3]) with mapi id 15.20.1228.020; Wed, 10 Oct 2018 21:47:06 +0000 From: Rick Macklem To: Felix Winterhalter , "freebsd-fs@freebsd.org" Subject: Re: NFSv4 Kerberos mount from Linux Thread-Topic: NFSv4 Kerberos mount from Linux Thread-Index: AQHUW9DS+OLl3kMYEUaTZ7pIOOpJR6UPKibngAl2Y4CAAGctbg== Date: Wed, 10 Oct 2018 21:47:06 +0000 Message-ID: References: <30f6446c-6fed-4b1e-9cae-9c417974ec46@audiofair.de> , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1561; 6:1SqGw2wYu17AGtoXYHQFHzPZXbJkZL+7iruSf5mPvc3iLgFYB6uA0zZ2g/VjpqSr0NV5jXLoEVopHypt3UbOnYwpfpOB0Glob06/EsVnFxPNP5QAUGi6zN6AFiAjX2xMwo2wtEnJJgSKIX3VA87kr2hJ29B2/PZ0P0/YNq+2rlU/hn0lx1po/7K8fhmDNcIQcWrUzx/AVcIaySjGOSB7GR9iMO+XS1ZDsTH/olxSJKiPlV4Byhp+KJxcko/HAoDNK2lyARLkbYTu4nTtzir9kasxPViBCVdUgaflOX5nAw0YbyF7NnuYrAzF780bWqbElArROn44vA6H3DogxkbL9Jy7o9yY73clOrKxc68PTzzf9XDyh8+w7ggI3BtgnaL3UzsWrzEXYhwjPY4dVAZ+LuVOn9hMOowaXyc0mtvlpOEcoDsG1kscNGohhSAo2Lz4TMTBOwSxSN9/V60Q3Z+gKQ==; 5:qKNnOuYP47fyKQ1lePy0ZlaJAECQClCkqXY3yu2QHYoX+3FV4ryZSKwd0UFv2HZEj6+8O4ha3+lvu57CkFefWs6R/9/QsupVamXXOlXr9Lw1wULX904XDZuyW28kB5vdhrIba509Bt/lzRJAnKofom6apVTp2QPVwfz7xN1AdUo=; 7:8obGt2q6QtKeLwzcGvjvAZGllry7TRdmY+ysupjYYRg4mWfwgI/pxi7Nv15QrXFwnDOUo5hd+RDjCIlKf15UiAXl3Pv4Wf47AyDHcuPiehHJPAmKiUVBMDFpVFlEhCCyyvVyuj9MI9Q86yBBAiK2FRG1tUxqm696gLpWGuS7VAapN/w/Eoz0EqHlDdpvHwO4wtUb+EtsxU1bRXVijmAmbRT2QAGWi3BEYSBN3v20inArtoXMd9pmlP56ePs5qvWu x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: f8aaece9-fdbf-4db7-1a94-08d62ef9ec0d x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1561; x-ms-traffictypediagnostic: YTOPR0101MB1561: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231355)(944501410)(52105095)(149066)(150057)(6041310)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051); SRVR:YTOPR0101MB1561; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1561; x-forefront-prvs: 08213D42D3 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(376002)(39850400004)(136003)(346002)(189003)(199004)(5660300001)(478600001)(81156014)(81166006)(8936002)(786003)(316002)(14454004)(6246003)(2501003)(5250100002)(8676002)(305945005)(74316002)(25786009)(2900100001)(14444005)(256004)(55016002)(6436002)(53936002)(105586002)(9686003)(106356001)(229853002)(6506007)(33656002)(74482002)(71190400001)(53546011)(71200400001)(110136005)(7696005)(99286004)(86362001)(186003)(102836004)(2906002)(446003)(476003)(11346002)(76176011)(68736007)(97736004)(486006)(46003); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1561; H:YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: TtUG1LlqU7m2btpcpGsPCZl2N4xyz+yrRauGXP1PkMN+Qc5FS3GDkDCR/V4Aa962DYYrIfA2cBvkv28Lc/4v1S24DxNSwteptaiYZ3PkxoAd0wZ9nbJjiep5MCT3ky4S0pfdjAxbcvwPyFvttRqiUfg2eznijHpA3VyLtGU5uSjKect+DisnIjPGYVZOYXywTlFlfg6pyPvzKZnAN5/CaXmDqxVjS48EtxvGyKxrNQAWKzHLmsYZXli+w1Pvoq17c3KoYo0CDuaT6rc+mOMpUZMknC55RzJBiT/cCDuiQREOMHS97n7BHBQOV/ImlI8x8IItoVX9z9d8wTo5uUT4GsVyha+4mgUT2mwtQtxy2fE= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: f8aaece9-fdbf-4db7-1a94-08d62ef9ec0d X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2018 21:47:06.0679 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1561 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 21:47:08 -0000 Felix Winterhalter wrote: On 10/4/18 5:21 PM, Rick Macklem wrote: [stuff snipped] >>> I am now trying to mount this directory as root first without having to >>> deal with user keytabs or tickets. >>> >>> This works fine with -sec=3Dsys and nfsv4.1 and nfsv3 and -sec=3Dkrb5p. >>> This does not however work with nfsv4 and krb5p or any other krb5 flavo= r. >> Sorry, I'm not sure what you are saying here. Is it >> 1 - no version of NFS works for krb5p or >> 2 - NFSv4.1 works for krb5p, but NFSv4.0 does not or >> 3 - only nfsv3 works for krb5p [snipped lots of text] > >#3 is indeed what was happening. I could mount with krb5p for nfsv3 >(which I was not aware was even doable) however nfsv4 would stubbornly >refuse to do any mounting. Yes, RPCSEC_GSS was done by Sun for NFSv3 and it was a good fit, since NFSv= 3 does not have any server state to maintain. As such, all RPCs are atomic op= erations done by users (which for Kerberized mounts must have a TGT in a credential = cache). NFSv4 wasn't really a good fit for the model, because the NFSv4 server main= tains lock state (NFSv4 Opens are a form of lock used by Windows at file open tim= e). There are "state maintenance" operations that must be done by the user doin= g the mount (usually root), where they typically don't have a TGT in a creden= tial cache. --> The ugly solution for this is typically a host-based client credential = in a keytab on the client. (Usually a principal like "root/client-host.domain@REA= LM" or "host/client-host.domain@REALM" or "nfs/client-host.domain@REALM" in the default keytab on the client.) >I have now after a lot of try and error figured out what I need to do in >order to make it work. > >To start with I have kerberos credentials with both host/ and nfs/ on >both client and server. Mounting nfsv4 shares with krb5p from a linux >server has also worked in this context. Yes, I'm assuming that satisfied the host-based client credential as I desc= ribed above. >I leave you to judge whether what I found out is intended behaviour or >if something weird is going on. Yes, sounds like intended behaviour, since the client must have a Kerberos credential to use for the "state maintenance" operations that are not done = on behalf of a user. >My exports file originally looked something like this: > >/nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=3Droot >-sec=3Dkrb5p clients > >V4: /nfsTests -sec=3Dkrb5p clients > >Which allowed me to do nfsv3 krb5p mounts but not nfsv4 krb5p mounts. > >Changing the exports file to this: > >/nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=3Droot >-sec=3Dkrb5p clients > >V4: /nfsTests -sec=3Dkrb5p,krb5i clients This suggests that there is a bug in the client, where it uses krb5i instea= d of krb5p at some point in the mounting process. (I have also seen cases where the cl= ient erroneously falls back on using sys at some point in the mounting process.) (You did mention before you were using the Linux client. If you are using a= FreeBSD client, I would be interested in looking at this.) >Allows nfsv4 krb5p mounts to work for some reason I do not understand. >Not setting the -sec option on the V4 line apparently defaults to >-sec=3Dsys and doesn't allow any krb5 mounts. I'm not sure that this is a >good default as I wasn't even aware that the -sec option needed to be >set on this line. In FreeBSD, defaults are meant to maintain backwards compatibility. This me= ans that AUTH_SYS should work by default. Also, AUTH_SYS is what 99.9999% of FreeBSD NFS mounts still use, from what I've seen.) >I've got packet traces of the nfsv3 krb5 and krb5i mounts and I'll make >traces of the two nfsv4 mount attempts and send them to you if you're >interested. I'm still not sure what exactly is happening here. The successful one for NFSv4 might be interesting. If you look at it in wireshark, I suspect you'd find somewhere during the mount that it did RPCs which were not krb5p and that would show why the addition of krb5i made it work. I did suggest you start with -sec=3Dsys:krb5:krb5i:krb5p and, once that wor= ks, remove the security flavours one at a time until the mount doesn't work. (Then you capture packets for the minimal case that does work and look at what security flavours the client is using for all RPCs done during the mo= unt.) You now know why almost no one uses Kerberized NFSv4 mounts. Unfortunately, the NFSv4 working group has never gotten around to a better solution. Discussion of a host based encryption technique using something like SSL has happened, but no one has gone beyond that. rick From owner-freebsd-fs@freebsd.org Wed Oct 10 22:38:20 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5245410BEC94 for ; Wed, 10 Oct 2018 22:38:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E1F9E7504B for ; Wed, 10 Oct 2018 22:38:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A326F10BEC93; Wed, 10 Oct 2018 22:38:19 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91B0810BEC92 for ; Wed, 10 Oct 2018 22:38:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3323575049 for ; Wed, 10 Oct 2018 22:38:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 77EAF24D45 for ; Wed, 10 Oct 2018 22:38:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9AMcIYT012190 for ; Wed, 10 Oct 2018 22:38:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9AMcIoL012189 for fs@FreeBSD.org; Wed, 10 Oct 2018 22:38:18 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 208130] smbfs is slow because it (apparently) doesn't do any caching/buffering Date: Wed, 10 Oct 2018 22:38:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: noah.bergbauer@tum.de 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 22:38:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208130 --- Comment #5 from noah.bergbauer@tum.de --- (In reply to Conrad Meyer from comment #4) If you're talking about sysutils/fusefs-smbnetfs, it maxes out around 8 MB/= s. But I wonder: Why is FreeBSD smbfs capped at about 60 MB/s while Linux cifs (inside bhyve on the same machine!) easily saturates the Gigabit link (120 MB/s)? From a quick peek at the code the maximum read size seems to be 60KB which my measurements somewhat confirm. Synchronously transferring 60KB buf= fers at 60MB/s indicates a round trip time of exactly 1ms - in reality the RTT is 0.35 ms though. Perhaps it takes one time slice for the reply to be process= ed (kern.hz=3D1000)? It's just a bit surprising that remotely mounting a filesystem (or even jus= t a block device) from one freebsd server to another is this hard. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 04:25:08 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1550910CDADC for ; Thu, 11 Oct 2018 04:25:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A9140839C7 for ; Thu, 11 Oct 2018 04:25:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6C34B10CDADB; Thu, 11 Oct 2018 04:25:07 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B13710CDADA for ; Thu, 11 Oct 2018 04:25:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDB14839B9 for ; Thu, 11 Oct 2018 04:25:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3746027DE8 for ; Thu, 11 Oct 2018 04:25:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9B4P68i004977 for ; Thu, 11 Oct 2018 04:25:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9B4P60t004976 for fs@FreeBSD.org; Thu, 11 Oct 2018 04:25:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 228750] panic on zfs mirror removal Date: Thu, 11 Oct 2018 04:25:04 +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.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: allanjude@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 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 04:25:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 Allan Jude changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |allanjude@FreeBSD.org --- Comment #5 from Allan Jude --- (In reply to Roger Hammerstein from comment #4) That panic is different, and may warrant its own PR. See also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 04:25:02 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 606B110CDAD6 for ; Thu, 11 Oct 2018 04:25:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 00ADC839AA for ; Thu, 11 Oct 2018 04:25:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B7E5310CDAD5; Thu, 11 Oct 2018 04:25:01 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A698810CDAD4 for ; Thu, 11 Oct 2018 04:25:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49A60839A6 for ; Thu, 11 Oct 2018 04:25:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A4E3C27DDF for ; Thu, 11 Oct 2018 04:25:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9B4P0XA004789 for ; Thu, 11 Oct 2018 04:25:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9B4P0t3004787 for fs@FreeBSD.org; Thu, 11 Oct 2018 04:25:00 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 229007] [zfs] kernel crashes on remove disk Date: Thu, 11 Oct 2018 04:25:00 +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 Some People X-Bugzilla-Who: allanjude@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 04:25:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 --- Comment #6 from Allan Jude --- Possibly related to two different crashes discussed in: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 09:08:12 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 777E710B22CA for ; Thu, 11 Oct 2018 09:08:11 +0000 (UTC) (envelope-from peter@ifm.liu.se) Received: from mailout.ifm.liu.se (mailout.ifm.liu.se [130.236.160.13]) by mx1.freebsd.org (Postfix) with ESMTP id 802668EA43 for ; Thu, 11 Oct 2018 09:08:10 +0000 (UTC) (envelope-from peter@ifm.liu.se) Received: from dhcp-16-246.it.liu.se (propen.it.liu.se [130.236.16.246]) (authenticated bits=0) by mail.ifm.liu.se (8.15.2/8.14.4) with ESMTPSA id w9B8aX78001241 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Oct 2018 10:36:33 +0200 (CEST) From: Peter Eriksson Message-Id: <33A0F0BC-4AD8-4DE3-B484-42B7FB208B6A@ifm.liu.se> Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: NFSv4 Kerberos mount from Linux Date: Thu, 11 Oct 2018 10:36:27 +0200 In-Reply-To: Cc: "freebsd-fs@freebsd.org" To: Rick Macklem , Felix Winterhalter References: <30f6446c-6fed-4b1e-9cae-9c417974ec46@audiofair.de> X-Mailer: Apple Mail (2.3445.100.39) X-IFMLiUSE-MailScanner-Information: Please contact postmaster@ifm.liu.se more information X-IFMLiUSE-MailScanner-ID: w9B8aX78001241 X-IFMLiUSE-MailScanner: Found to be clean X-IFMLiUSE-MailScanner-From: peter@ifm.liu.se X-Spam-Status: No Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 09:08:12 -0000 Just a few comments (random brain-dump) in case someone else is having = problems with NFS & Kerberos.=20 We=E2=80=99ve been using NFSv4 with Kerberos from Linux clients here for = many years (with Solaris-based NFS servers and MIT Kerberos) and lately = using FreeBSD as the NFS server OS (in an Microsoft AD Kerberos = environment).=20 There are a few differences in behaviour (from a Solaris perspective), = mainly regarding the =E2=80=9Cpseudo=E2=80=9D NFSv4 filesystem but not = something that can=E2=80=99t be handled. In the process of moving to = FreeBSD based servers I=E2=80=99ve also been testing lots of different = clients in order to make sure everything works as expected. Here are = some notes: General stuff: 1. Have a _kerberos.my.zone.com DNS TXT record containing the Kerberos = realm (nice to have) 2. Have a _nfsv4domain.my.zone.com DNS = TXT record containing the NFSv4 =E2=80=9Cdomain=E2=80=9D (not all = clients use it, but it=E2=80=99s nice to have) * FreeBSD server (with ZFS filesystems), things below /export is = NFS-shared as (for example) server:/staff/user1 1. /etc/exports (we _only_ allow sec=3Dkrb for home = directories): V4: /export -sec=3Dkrb5:krb5i:krb5p Or (on a server also serving some (read-only) sec=3Dsys filesystems = below /exports) V4: /export -sec=3Dkrb5:krb5i:krb5p:sys 2. /etc/zfs/exports (generated from =E2=80=9Cset sharenfs=3Dxxx=E2=80=9D = on the ZFS filesystems) Home-server: /export/staff -sec=3Dkrb5:krb5i:krb5p=20= /export/staff/user1 -sec=3Dkrb5:krb5i:krb5p=20 /export/staff/user2 -sec=3Dkrb5:krb5i:krb5p=20 /export/students -sec=3Dkrb5:krb5i:krb5p=20 /export/students/user3 -sec=3Dkrb5:krb5i:krb5p=20 Software-server: /export/db/icons -sec=3Dsys -ro=20 /export/old/ifm/solaris-x86 -sec=3Dkrb5:krb5i:krb5p:sys -ro=20= /export/old/ifm/windows-86 -sec=3Dkrb5:krb5i:krb5p:sys -ro=20 /export/software -sec=3Dkrb5:krb5i:krb5p -ro=20 3. Make sure you have host/FQDN@REALM and nfs/FQDN@REALM Kerberos = principals in /etc/krb5.keytab and that FQDN is listed in /etc/hosts = like: 1.2.3.4 foo.bar.com foo 4. rc.conf (we have a lot of users in our AD so we have to use a large = number for usermax, replace =E2=80=9Cliu.se =E2=80=9D = with your NFSv4 =E2=80=9Cdomain=E2=80=9D for nfsuserd_flags) gssd_enable=3D"YES" nfs_server_enable=3D"YES" nfsv4_server_enable=3D"YES" nfscbd_enable=3D"YES" mountd_enable=3D"YES" nfsuserd_enable=3D"YES" nfsuserd_flags=3D"-manage-gids -domain liu.se -usertimeout 10 -usermax = 100000 16" 5. Make sure you use NTPD so the clock is correct.=20 * All clients (Solaris 10, OmniOS, MacOS 10.12-10.14, FreeBSD 11.0-11.2, = CentOS 7, Debian 9, Ubuntu 17-18 tested): 1. Make sure FQDN is in /etc/hosts 2. Make sure you use NTPD so the clock is correct. 3. Have a =E2=80=9Chost/FQDN@REALM=E2=80=9D Kerberos host principal in = /etc/krb5.keytab (nfs or root is not needed for NFS-mounting to work) 4. We use a fairly default /etc/krb5.conf, sort of like: > [libdefaults] > default_realm =3D REALM > dns_lookup_realm =3D true >=20 > ticket_lifetime =3D 24h > renew_lifetime =3D 7d > forwardable =3D true >=20 > default_ccache_name =3D KEYRING:persistent:%{uid} KEYRING probably only works on Linux and there are some problems with = KEYRING in Debian & Ubuntu since not everything in it supports it due to = them using Heimdal instead of MIT (like for smbclient) but it mostly = works. Works fine in CentOS 7 though - in general CentOS 7 feels more = =E2=80=9Centerprise=E2=80=9D-ready than Debian & Ubuntu. The old classic = FILE-ccaches should work fine though. For mounting we use the automounter and a "executable map=E2=80=9D (perl = script) that looks up records in DNS (Hesiod-style) since the built-in = Hesiod support in most automounters is a bit.. lacking. Works quite = well. You can find the scripts we use here: http://www.grebo.net/~peter/nfs = (The dns-update scripts use data from an SQL database so probably = isn=E2=80=99t directly usable to anybody else. We use the same SQL = database to populate a locally developed BerkeleyDB-based NSS-database = on each FreeBSD server in order to speed things up since AD/LDAP-looks = with ~90k users and silly amounts of AD groups takes forever, even with = cacheing). Some Linux-specific stuff:=20 Packages needed: CentOS: - nfs-utils - libnfsidmap - nfs4-acl-tools - autofs Debian: - keyutils - nfs-kernel-server # rpc.idmapd needs this due to a bug in Debian Ubuntu: - keyutils Other nice-to have packages: - hesiod - autofs-hesiod Some settings to check for: /etc/default/nfs-common: NEED_IDMAPD=3Dyes NEED_GSSD=3Dyes /etc/idmapd.conf (replace =E2=80=9Cliu.se =E2=80=9D = with your NFSv4 =E2=80=9Cdomain=E2=80=9D): Domain=3Dliu.se /etc/request-key.d/id_resolver.conf (should be there already if using = a modern Linux and you=E2=80=99ve added the packages above): create id_resolver * * /usr/sbin/nfsidmap %k %d MacOS: Basically require the latest - 10.14 (Mojave) - for things to work = smoothly. In theory 10.12 & 10.13 should work but there is some bug in = them that causes the OS to panic when you try to use NFS & Kerberos. = 10.11 and earlier doesn=E2=80=99t support good enough encryption for = us=E2=80=A6 But with 10.14 you just need to get a Kerberos ticket and = then you can mount things just fine. /etc/nfs.conf should contain (replace =E2=80=9Cliu.se = =E2=80=9D with your NFSv4 =E2=80=9Cdomain=E2=80=9D): nfs.client.default_nfs4domain=3Dliu.se (There are a lot of problems you can run into with Microsofts AD = implementation of Kerberos too that we=E2=80=99ve had to be fighting = with, but that=E2=80=99s a whole other topic) - Peter > On 10 Oct 2018, at 23:47, Rick Macklem wrote: >=20 > Felix Winterhalter wrote: > On 10/4/18 5:21 PM, Rick Macklem wrote: > [stuff snipped] >>>> I am now trying to mount this directory as root first without = having to >>>> deal with user keytabs or tickets. >>>>=20 >>>> This works fine with -sec=3Dsys and nfsv4.1 and nfsv3 and = -sec=3Dkrb5p. >>>> This does not however work with nfsv4 and krb5p or any other krb5 = flavor. >>> Sorry, I'm not sure what you are saying here. Is it >>> 1 - no version of NFS works for krb5p or >>> 2 - NFSv4.1 works for krb5p, but NFSv4.0 does not or >>> 3 - only nfsv3 works for krb5p > [snipped lots of text] >>=20 >> #3 is indeed what was happening. I could mount with krb5p for nfsv3 >> (which I was not aware was even doable) however nfsv4 would = stubbornly >> refuse to do any mounting. > Yes, RPCSEC_GSS was done by Sun for NFSv3 and it was a good fit, since = NFSv3 > does not have any server state to maintain. As such, all RPCs are = atomic operations > done by users (which for Kerberized mounts must have a TGT in a = credential cache). >=20 > NFSv4 wasn't really a good fit for the model, because the NFSv4 server = maintains > lock state (NFSv4 Opens are a form of lock used by Windows at file = open time). > There are "state maintenance" operations that must be done by the user = doing > the mount (usually root), where they typically don't have a TGT in a = credential > cache. > --> The ugly solution for this is typically a host-based client = credential in a keytab > on the client. (Usually a principal like = "root/client-host.domain@REALM" or > "host/client-host.domain@REALM" or "nfs/client-host.domain@REALM" > in the default keytab on the client.) >=20 >> I have now after a lot of try and error figured out what I need to do = in >> order to make it work. >>=20 >> To start with I have kerberos credentials with both host/ and nfs/ on >> both client and server. Mounting nfsv4 shares with krb5p from a linux >> server has also worked in this context. > Yes, I'm assuming that satisfied the host-based client credential as I = described > above. >=20 >> I leave you to judge whether what I found out is intended behaviour = or >> if something weird is going on. > Yes, sounds like intended behaviour, since the client must have a = Kerberos > credential to use for the "state maintenance" operations that are not = done on > behalf of a user. >=20 >> My exports file originally looked something like this: >>=20 >> /nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=3Droot >> -sec=3Dkrb5p clients >>=20 >> V4: /nfsTests -sec=3Dkrb5p clients >>=20 >> Which allowed me to do nfsv3 krb5p mounts but not nfsv4 krb5p mounts. >>=20 >> Changing the exports file to this: >>=20 >> /nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=3Droot >> -sec=3Dkrb5p clients >>=20 >> V4: /nfsTests -sec=3Dkrb5p,krb5i clients > This suggests that there is a bug in the client, where it uses krb5i = instead of krb5p > at some point in the mounting process. (I have also seen cases where = the client > erroneously falls back on using sys at some point in the mounting = process.) > (You did mention before you were using the Linux client. If you are = using a FreeBSD > client, I would be interested in looking at this.) >=20 >> Allows nfsv4 krb5p mounts to work for some reason I do not = understand. >> Not setting the -sec option on the V4 line apparently defaults to >> -sec=3Dsys and doesn't allow any krb5 mounts. I'm not sure that this = is a >> good default as I wasn't even aware that the -sec option needed to be >> set on this line. > In FreeBSD, defaults are meant to maintain backwards compatibility. = This means that > AUTH_SYS should work by default. Also, AUTH_SYS is what 99.9999% of = FreeBSD > NFS mounts still use, from what I've seen.) >=20 >> I've got packet traces of the nfsv3 krb5 and krb5i mounts and I'll = make >> traces of the two nfsv4 mount attempts and send them to you if you're >> interested. I'm still not sure what exactly is happening here. > The successful one for NFSv4 might be interesting. If you look at it = in > wireshark, I suspect you'd find somewhere during the mount that it > did RPCs which were not krb5p and that would show why the addition > of krb5i made it work. >=20 > I did suggest you start with -sec=3Dsys:krb5:krb5i:krb5p and, once = that works, > remove the security flavours one at a time until the mount doesn't = work. > (Then you capture packets for the minimal case that does work and look = at > what security flavours the client is using for all RPCs done during = the mount.) >=20 > You now know why almost no one uses Kerberized NFSv4 mounts. > Unfortunately, the NFSv4 working group has never gotten around to > a better solution. Discussion of a host based encryption technique = using > something like SSL has happened, but no one has gone beyond that. >=20 > rick > _______________________________________________ > 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 Thu Oct 11 10:46:17 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5966F10B60D9 for ; Thu, 11 Oct 2018 10:46:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E5DD292E58 for ; Thu, 11 Oct 2018 10:46:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id ABB1C10B60D8; Thu, 11 Oct 2018 10:46:16 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A7A710B60D7 for ; Thu, 11 Oct 2018 10:46:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B3DF92E57 for ; Thu, 11 Oct 2018 10:46:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5D7BB3359 for ; Thu, 11 Oct 2018 10:46:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BAkFvw015135 for ; Thu, 11 Oct 2018 10:46:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BAkFVW015134 for fs@FreeBSD.org; Thu, 11 Oct 2018 10:46:15 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 229007] [zfs] kernel crashes on remove disk Date: Thu, 11 Oct 2018 10:46: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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: serzh@expir.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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 10:46:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 --- Comment #7 from Sergei Masharov --- (In reply to Allan Jude from comment #6) I think they are related. In my case I also see "indirect" devices in probl= em pools. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 11:52:05 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E88510B7D50 for ; Thu, 11 Oct 2018 11:52:05 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from mail.inparadise.se (h-112-105.A444.priv.bahnhof.se [158.174.112.105]) (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 E033394EB4 for ; Thu, 11 Oct 2018 11:52:04 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id A50884619C; Thu, 11 Oct 2018 13:51:54 +0200 (CEST) Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id iNKXjL-xlkVU; Thu, 11 Oct 2018 13:51:52 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id B374F4619D; Thu, 11 Oct 2018 13:51:52 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.inparadise.se B374F4619D X-Virus-Scanned: amavisd-new at inparadise.se Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ka07Al5HmzKL; Thu, 11 Oct 2018 13:51:52 +0200 (CEST) Received: from its-5cg60227mj.its.uu.se (its-5cg60227mj.its.uu.se [130.238.131.18]) by mail.inparadise.se (Postfix) with ESMTPSA id 633464619C; Thu, 11 Oct 2018 13:51:52 +0200 (CEST) Message-ID: <054a82958e9c1bed12c3a159d69db36b4cfcb5ec.camel@inparadise.se> Subject: Re: NFSv4 Kerberos mount from Linux From: Karli =?ISO-8859-1?Q?Sj=F6berg?= Reply-To: karli@inparadise.se To: Peter Eriksson , Rick Macklem , Felix Winterhalter Cc: "freebsd-fs@freebsd.org" Date: Thu, 11 Oct 2018 13:49:59 +0200 In-Reply-To: <33A0F0BC-4AD8-4DE3-B484-42B7FB208B6A@ifm.liu.se> References: <30f6446c-6fed-4b1e-9cae-9c417974ec46@audiofair.de> <33A0F0BC-4AD8-4DE3-B484-42B7FB208B6A@ifm.liu.se> Organization: InParadise Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-6HWtWOXsHgjO/mRWq1SE" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 11:52:05 -0000 --=-6HWtWOXsHgjO/mRWq1SE Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2018-10-11 at 10:36 +0200, Peter Eriksson wrote: > Just a few comments (random brain-dump) in case someone else is > having problems with NFS & Kerberos.=20 "Just a few comments", hot dog, that was a great write-up! It would be great, I think, to have this on the FreeBSD wiki or in the Handbook even, because I agree not many people use Kerberized NFS since it=C2=B4s such a hassle and not that much info about it. /K >=20 >=20 > We=E2=80=99ve been using NFSv4 with Kerberos from Linux clients here for = many > years (with Solaris-based NFS servers and MIT Kerberos) and lately > using FreeBSD as the NFS server OS (in an Microsoft AD Kerberos > environment).=20 >=20 > There are a few differences in behaviour (from a Solaris > perspective), mainly regarding the =E2=80=9Cpseudo=E2=80=9D NFSv4 filesys= tem but not > something that can=E2=80=99t be handled. In the process of moving to Free= BSD > based servers I=E2=80=99ve also been testing lots of different clients in > order to make sure everything works as expected. Here are some notes: >=20 > General stuff: >=20 > 1. Have a _kerberos.my.zone.com DNS TXT record containing the > Kerberos realm (nice to have) > 2. Have a _nfsv4domain.my.zone.com > DNS TXT record containing the NFSv4 =E2=80=9Cdomain=E2=80=9D (not all cli= ents use it, > but it=E2=80=99s nice to have) >=20 >=20 > * FreeBSD server (with ZFS filesystems), things below /export is NFS- > shared as (for example) server:/staff/user1 >=20 > 1. /etc/exports (we _only_ allow sec=3Dkrb for home > directories): > V4: /export -sec=3Dkrb5:krb5i:krb5p >=20 > Or (on a server also serving some (read-only) sec=3Dsys filesystems > below /exports) > V4: /export -sec=3Dkrb5:krb5i:krb5p:sys >=20 >=20 > 2. /etc/zfs/exports (generated from =E2=80=9Cset sharenfs=3Dxxx=E2=80=9D = on the ZFS > filesystems) > Home-server: > /export/staff -sec=3Dkrb5:krb5i:krb5p=20 > /export/staff/user1 -sec=3Dkrb5:krb5i:krb5p=20 > /export/staff/user2 -sec=3Dkrb5:krb5i:krb5p=20 > /export/students -sec=3Dkrb5:krb5i:krb5p=20 > /export/students/user3 -sec=3Dkrb5:krb5i:krb5p=20 >=20 > Software-server: > /export/db/icons -sec=3Dsys -ro=20 > /export/old/ifm/solaris-x86 -sec=3Dkrb5:krb5i:krb5p:sys -ro=20 > /export/old/ifm/windows-86 -sec=3Dkrb5:krb5i:krb5p:sys -ro=20 > /export/software -sec=3Dkrb5:krb5i:krb5p -ro=20 >=20 >=20 > 3. Make sure you have host/FQDN@REALM and nfs/FQDN@REALM Kerberos > principals in /etc/krb5.keytab and that FQDN is listed in /etc/hosts > like: >=20 > 1.2.3.4 foo.bar.com foo >=20 > 4. rc.conf (we have a lot of users in our AD so we have to use a > large number for usermax, replace =E2=80=9Cliu.se =E2=80= =9D with your > NFSv4 =E2=80=9Cdomain=E2=80=9D for nfsuserd_flags) >=20 > gssd_enable=3D"YES" > nfs_server_enable=3D"YES" > nfsv4_server_enable=3D"YES" > nfscbd_enable=3D"YES" > mountd_enable=3D"YES" > nfsuserd_enable=3D"YES" > nfsuserd_flags=3D"-manage-gids -domain liu.se -usertimeout 10 -usermax > 100000 16" >=20 > 5. Make sure you use NTPD so the clock is correct.=20 >=20 >=20 > * All clients (Solaris 10, OmniOS, MacOS 10.12-10.14, FreeBSD 11.0- > 11.2, CentOS 7, Debian 9, Ubuntu 17-18 tested): >=20 > 1. Make sure FQDN is in /etc/hosts >=20 > 2. Make sure you use NTPD so the clock is correct. >=20 > 3. Have a =E2=80=9Chost/FQDN@REALM=E2=80=9D Kerberos host principal in > /etc/krb5.keytab (nfs or root is not needed for NFS-mounting to work) >=20 > 4. We use a fairly default /etc/krb5.conf, sort of like: >=20 > > [libdefaults] > > default_realm =3D REALM > > dns_lookup_realm =3D true > >=20 > > ticket_lifetime =3D 24h > > renew_lifetime =3D 7d > > forwardable =3D true > >=20 > > default_ccache_name =3D KEYRING:persistent:%{uid} >=20 > KEYRING probably only works on Linux and there are some problems with > KEYRING in Debian & Ubuntu since not everything in it supports it due > to them using Heimdal instead of MIT (like for smbclient) but it > mostly works. Works fine in CentOS 7 though - in general CentOS 7 > feels more =E2=80=9Centerprise=E2=80=9D-ready than Debian & Ubuntu. The o= ld classic > FILE-ccaches should work fine though. >=20 > For mounting we use the automounter and a "executable map=E2=80=9D (perl > script) that looks up records in DNS (Hesiod-style) since the built- > in Hesiod support in most automounters is a bit.. lacking. Works > quite well. You can find the scripts we use here: >=20 > http://www.grebo.net/~peter/nfs < > http://www.grebo.net/~peter/nfs> >=20 > (The dns-update scripts use data from an SQL database so probably > isn=E2=80=99t directly usable to anybody else. We use the same SQL databa= se > to populate a locally developed BerkeleyDB-based NSS-database on each > FreeBSD server in order to speed things up since AD/LDAP-looks with > ~90k users and silly amounts of AD groups takes forever, even with > cacheing). >=20 > Some Linux-specific stuff:=20 >=20 > Packages needed: >=20 > CentOS: > - nfs-utils > - libnfsidmap > - nfs4-acl-tools > - autofs >=20 > Debian: > - keyutils > - nfs-kernel-server # rpc.idmapd needs this due to a bug in Debian >=20 > Ubuntu: > - keyutils >=20 > Other nice-to have packages: > - hesiod > - autofs-hesiod >=20 > Some settings to check for: >=20 > /etc/default/nfs-common: > NEED_IDMAPD=3Dyes > NEED_GSSD=3Dyes >=20 > /etc/idmapd.conf (replace =E2=80=9Cliu.se =E2=80=9D wit= h your NFSv4 > =E2=80=9Cdomain=E2=80=9D): > Domain=3Dliu.se >=20 > /etc/request-key.d/id_resolver.conf (should be there already if > using a modern Linux and you=E2=80=99ve added the packages above): > create id_resolver * * /usr/sbin/nfsidmap %k > %d >=20 >=20 > MacOS: >=20 > Basically require the latest - 10.14 (Mojave) - for things to work > smoothly. In theory 10.12 & 10.13 should work but there is some bug > in them that causes the OS to panic when you try to use NFS & > Kerberos. 10.11 and earlier doesn=E2=80=99t support good enough encryptio= n > for us=E2=80=A6 But with 10.14 you just need to get a Kerberos ticket an= d > then you can mount things just fine. >=20 > /etc/nfs.conf should contain (replace =E2=80=9Cliu.se =E2= =80=9D with > your NFSv4 =E2=80=9Cdomain=E2=80=9D): > nfs.client.default_nfs4domain=3Dliu.se >=20 >=20 >=20 > (There are a lot of problems you can run into with Microsofts AD > implementation of Kerberos too that we=E2=80=99ve had to be fighting with= , > but that=E2=80=99s a whole other topic) >=20 > - Peter >=20 >=20 > > On 10 Oct 2018, at 23:47, Rick Macklem > > wrote: > >=20 > > Felix Winterhalter wrote: > > On 10/4/18 5:21 PM, Rick Macklem wrote: > > [stuff snipped] > > > > > I am now trying to mount this directory as root first without > > > > > having to > > > > > deal with user keytabs or tickets. > > > > >=20 > > > > > This works fine with -sec=3Dsys and nfsv4.1 and nfsv3 and > > > > > -sec=3Dkrb5p. > > > > > This does not however work with nfsv4 and krb5p or any other > > > > > krb5 flavor. > > > >=20 > > > > Sorry, I'm not sure what you are saying here. Is it > > > > 1 - no version of NFS works for krb5p or > > > > 2 - NFSv4.1 works for krb5p, but NFSv4.0 does not or > > > > 3 - only nfsv3 works for krb5p > >=20 > > [snipped lots of text] > > >=20 > > > #3 is indeed what was happening. I could mount with krb5p for > > > nfsv3 > > > (which I was not aware was even doable) however nfsv4 would > > > stubbornly > > > refuse to do any mounting. > >=20 > > Yes, RPCSEC_GSS was done by Sun for NFSv3 and it was a good fit, > > since NFSv3 > > does not have any server state to maintain. As such, all RPCs are > > atomic operations > > done by users (which for Kerberized mounts must have a TGT in a > > credential cache). > >=20 > > NFSv4 wasn't really a good fit for the model, because the NFSv4 > > server maintains > > lock state (NFSv4 Opens are a form of lock used by Windows at file > > open time). > > There are "state maintenance" operations that must be done by the > > user doing > > the mount (usually root), where they typically don't have a TGT in > > a credential > > cache. > > --> The ugly solution for this is typically a host-based client > > credential in a keytab > > on the client. (Usually a principal like " > > root/client-host.domain@REALM" or > > "host/client-host.domain@REALM" or " > > nfs/client-host.domain@REALM" > > in the default keytab on the client.) > >=20 > > > I have now after a lot of try and error figured out what I need > > > to do in > > > order to make it work. > > >=20 > > > To start with I have kerberos credentials with both host/ and > > > nfs/ on > > > both client and server. Mounting nfsv4 shares with krb5p from a > > > linux > > > server has also worked in this context. > >=20 > > Yes, I'm assuming that satisfied the host-based client credential > > as I described > > above. > >=20 > > > I leave you to judge whether what I found out is intended > > > behaviour or > > > if something weird is going on. > >=20 > > Yes, sounds like intended behaviour, since the client must have a > > Kerberos > > credential to use for the "state maintenance" operations that are > > not done on > > behalf of a user. > >=20 > > > My exports file originally looked something like this: > > >=20 > > > /nfsTests/ /nfsTests/testexport /nfsTests/otherexport > > > -maproot=3Droot > > > -sec=3Dkrb5p clients > > >=20 > > > V4: /nfsTests -sec=3Dkrb5p clients > > >=20 > > > Which allowed me to do nfsv3 krb5p mounts but not nfsv4 krb5p > > > mounts. > > >=20 > > > Changing the exports file to this: > > >=20 > > > /nfsTests/ /nfsTests/testexport /nfsTests/otherexport > > > -maproot=3Droot > > > -sec=3Dkrb5p clients > > >=20 > > > V4: /nfsTests -sec=3Dkrb5p,krb5i clients > >=20 > > This suggests that there is a bug in the client, where it uses > > krb5i instead of krb5p > > at some point in the mounting process. (I have also seen cases > > where the client > > erroneously falls back on using sys at some point in the mounting > > process.) > > (You did mention before you were using the Linux client. If you are > > using a FreeBSD > > client, I would be interested in looking at this.) > >=20 > > > Allows nfsv4 krb5p mounts to work for some reason I do not > > > understand. > > > Not setting the -sec option on the V4 line apparently defaults to > > > -sec=3Dsys and doesn't allow any krb5 mounts. I'm not sure that > > > this is a > > > good default as I wasn't even aware that the -sec option needed > > > to be > > > set on this line. > >=20 > > In FreeBSD, defaults are meant to maintain backwards compatibility. > > This means that > > AUTH_SYS should work by default. Also, AUTH_SYS is what 99.9999% of > > FreeBSD > > NFS mounts still use, from what I've seen.) > >=20 > > > I've got packet traces of the nfsv3 krb5 and krb5i mounts and > > > I'll make > > > traces of the two nfsv4 mount attempts and send them to you if > > > you're > > > interested. I'm still not sure what exactly is happening here. > >=20 > > The successful one for NFSv4 might be interesting. If you look at > > it in > > wireshark, I suspect you'd find somewhere during the mount that it > > did RPCs which were not krb5p and that would show why the addition > > of krb5i made it work. > >=20 > > I did suggest you start with -sec=3Dsys:krb5:krb5i:krb5p and, once > > that works, > > remove the security flavours one at a time until the mount doesn't > > work. > > (Then you capture packets for the minimal case that does work and > > look at > > what security flavours the client is using for all RPCs done during > > the mount.) > >=20 > > You now know why almost no one uses Kerberized NFSv4 mounts. > > Unfortunately, the NFSv4 working group has never gotten around to > > a better solution. Discussion of a host based encryption technique > > using > > something like SSL has happened, but no one has gone beyond that. > >=20 > > rick > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-fs < > > https://lists.freebsd.org/mailman/listinfo/freebsd-fs> > > To unsubscribe, send any mail to " > > freebsd-fs-unsubscribe@freebsd.org > freebsd-fs-unsubscribe@freebsd.org>" >=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" --=-6HWtWOXsHgjO/mRWq1SE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEw0f5gWr+/IyirHlmGmjXrg3Zy5EFAlu/OOcACgkQGmjXrg3Z y5FJYAf+JNciD69KSLg0WtgA4ZRxLw2VHiA27e4ROK/5SFdi3kyIZPYpze2KQC+V fOHjwJv6cakRUFr3m5uJoNOwEmoXfr0RWRhoSC4b/3k+SmCLEaeLXz1o0GA2IU2q gF+L74i09sY3nZYZh4BX17gTRCxmpF/Mo3mx1uOiM7teiZBSQ6zXT6zGXK04xgA1 tn9Utk+XDjt7ILTpgX7mAPwepywVb0h7j+8xXfzAupKJpi/Q8fQU0BUoKlrZhg6h UVkFqKl5uQtLMyBqwn1tm2uALj8T3h4H9um1L02xr3kTeJkbpbNZpFt2aQ7mX21F SbrMImalBRg9C6C8J2kGNsk9EW18yA== =HKAY -----END PGP SIGNATURE----- --=-6HWtWOXsHgjO/mRWq1SE-- From owner-freebsd-fs@freebsd.org Thu Oct 11 14:02:26 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75D2210BBD50 for ; Thu, 11 Oct 2018 14:02:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1176571765 for ; Thu, 11 Oct 2018 14:02:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C98DD10BBD4F; Thu, 11 Oct 2018 14:02:25 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B840210BBD4E for ; Thu, 11 Oct 2018 14:02:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A24F7175D for ; Thu, 11 Oct 2018 14:02:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A6A1D538D for ; Thu, 11 Oct 2018 14:02:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BE2OhG060916 for ; Thu, 11 Oct 2018 14:02:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BE2OA1060915 for fs@FreeBSD.org; Thu, 11 Oct 2018 14:02: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 227784] zfs: Fatal trap 9: general protection fault while in kernel mode on shutdown Date: Thu, 11 Oct 2018 14:02: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: CURRENT X-Bugzilla-Keywords: panic, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wulf@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 14:02:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227784 --- Comment #14 from Vladimir Kondratyev --- (In reply to Mark Johnston from comment #12) 12.0-ALPHA9 r339280 still panics. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 14:03:11 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 59ACC10BBD7B for ; Thu, 11 Oct 2018 14:03:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EBD0F71907 for ; Thu, 11 Oct 2018 14:03:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AFAC510BBD7A; Thu, 11 Oct 2018 14:03:10 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E4DD10BBD79 for ; Thu, 11 Oct 2018 14:03:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B519718FE for ; Thu, 11 Oct 2018 14:03:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 9892A5399 for ; Thu, 11 Oct 2018 14:03:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BE39iu062039 for ; Thu, 11 Oct 2018 14:03:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BE39U0062038 for fs@FreeBSD.org; Thu, 11 Oct 2018 14:03:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229007] [zfs] kernel crashes on remove disk Date: Thu, 11 Oct 2018 14:03:09 +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 Some People X-Bugzilla-Who: allanjude@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 14:03:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 --- Comment #8 from Allan Jude --- (In reply to Sergei Masharov from comment #7) An indirect vdev is what you get once a remove has progressed. Do you have a stack trace or crash dump from that point in the process? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 15:58:31 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3358410BF081 for ; Thu, 11 Oct 2018 15:58:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C24D376511 for ; Thu, 11 Oct 2018 15:58:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 852D010BF080; Thu, 11 Oct 2018 15:58:30 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61F4310BF07F for ; Thu, 11 Oct 2018 15:58:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F291F7650B for ; Thu, 11 Oct 2018 15:58:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2BF266318 for ; Thu, 11 Oct 2018 15:58:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BFwTlh097286 for ; Thu, 11 Oct 2018 15:58:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BFwTYi097285 for fs@FreeBSD.org; Thu, 11 Oct 2018 15:58:29 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 229007] [zfs] kernel crashes on remove disk Date: Thu, 11 Oct 2018 15:58:28 +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 Some People X-Bugzilla-Who: gldisater@gmail.com 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 15:58:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 --- Comment #9 from Jeremy Faulkner --- tar zcvf core-dump-zfs-devrem.tar.gz /boot/kernel /usr/lib/debug/boot/kernel /var/crash/*.0 https://drive.google.com/open?id=3D1SUTm-hBgIhkkTmYNridU9zZqVMSIlA3T root@devremoval:~ # uname -a FreeBSD devremoval 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338859 GENERIC amd64 I haven't updated this bhyve vm recently but it's been unable to boot if th= ree of it's drives are enabled. panic: solaris assert: zio->io_type =3D=3D ZIO_TYPE_WRITE (0x3 =3D=3D 0x2),= file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_indirect.c, li= ne: 1267 cpuid =3D 1 time =3D 1539270204 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe004d167= 7e0 vpanic() at vpanic+0x1a3/frame 0xfffffe004d167840 panic() at panic+0x43/frame 0xfffffe004d1678a0 assfail3() at assfail3+0x2c/frame 0xfffffe004d1678c0 vdev_indirect_io_start() at vdev_indirect_io_start+0xae/frame 0xfffffe004d167900 zio_vdev_io_start() at zio_vdev_io_start+0x4b5/frame 0xfffffe004d167960 zio_execute() at zio_execute+0x18c/frame 0xfffffe004d1679b0 zio_nowait() at zio_nowait+0xc4/frame 0xfffffe004d1679e0 vdev_mirror_io_start() at vdev_mirror_io_start+0x42a/frame 0xfffffe004d167a= 70 zio_vdev_io_start() at zio_vdev_io_start+0x1fe/frame 0xfffffe004d167ad0 zio_execute() at zio_execute+0x18c/frame 0xfffffe004d167b20 taskqueue_run_locked() at taskqueue_run_locked+0x10c/frame 0xfffffe004d167b= 80 taskqueue_thread_loop() at taskqueue_thread_loop+0x88/frame 0xfffffe004d167= bb0 fork_exit() at fork_exit+0x84/frame 0xfffffe004d167bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe004d167bf0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- KDB: enter: panic [ thread pid 0 tid 100510 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 16:17:53 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A47E910BFC80 for ; Thu, 11 Oct 2018 16:17:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3E9747714C for ; Thu, 11 Oct 2018 16:17:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 016FC10BFC7F; Thu, 11 Oct 2018 16:17:53 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E38E010BFC7D for ; Thu, 11 Oct 2018 16:17:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 817CB77147 for ; Thu, 11 Oct 2018 16:17:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D445965F8 for ; Thu, 11 Oct 2018 16:17:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BGHp4M064763 for ; Thu, 11 Oct 2018 16:17:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BGHphN064762 for fs@FreeBSD.org; Thu, 11 Oct 2018 16:17:51 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 229614] ZFS lockup in zil_commit_impl Date: Thu, 11 Oct 2018 16:17: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: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: olgeni@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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 16:17:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 --- Comment #25 from Jimmy Olgeni --- (In reply to commit-hook from comment #23) > MFC after: 2 months Is this safe? I keep having issues on most of my 11.2 boxes :| Should I patch the kernel manually in the meantime? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 19:30:12 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC07910C5266 for ; Thu, 11 Oct 2018 19:30:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 597237E61F for ; Thu, 11 Oct 2018 19:30:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1B22010C5265; Thu, 11 Oct 2018 19:30:12 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09C3B10C5264 for ; Thu, 11 Oct 2018 19:30:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F4A27E61A for ; Thu, 11 Oct 2018 19:30:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CC979102B1 for ; Thu, 11 Oct 2018 19:30:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BJUA6d007857 for ; Thu, 11 Oct 2018 19:30:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BJUA2J007856 for fs@FreeBSD.org; Thu, 11 Oct 2018 19:30:10 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 229614] ZFS lockup in zil_commit_impl Date: Thu, 11 Oct 2018 19:30:10 +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.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: andreas.sommer87@googlemail.com 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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 19:30:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229614 --- Comment #26 from Andreas Sommer --- I recommend everyone having the described problem and similar `procstat -kk` stacktrace to patch their kernel manually for now. For our development CI h= ost, I did just that (built and replaced kernel only) and it works stably for so= me days now *without* the `kern.maxvnodes=3DHIGHNUMBER` workaround. The same a= pplies to my reproduction setup (see GitHub link, posted above) =E2=80=93 previous= ly it took a few seconds to reproduce the issue, and after replacing the kernel, no more problems. However, if you have 24/7 services that need to keep running, probably use = the workaround for now and wait for a dot release which will then anyhow requir= e a reboot. 2 months actually sounds long enough to give the safety of many people tryi= ng and confirming the change. It will also immediately make it from head to stable/12 according to https://www.freebsd.org/releases/12.0R/schedule.html= , so I'm happy. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 21:08:14 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1180C10C7F30 for ; Thu, 11 Oct 2018 21:08:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9C1E08254A for ; Thu, 11 Oct 2018 21:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5CD2D10C7F2F; Thu, 11 Oct 2018 21:08:13 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B61210C7F2E for ; Thu, 11 Oct 2018 21:08:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E187D82541 for ; Thu, 11 Oct 2018 21:08:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 33445110C0 for ; Thu, 11 Oct 2018 21:08:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BL8CfQ067105 for ; Thu, 11 Oct 2018 21:08:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BL8CX2067097 for fs@FreeBSD.org; Thu, 11 Oct 2018 21:08: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 228750] panic on zfs mirror removal Date: Thu, 11 Oct 2018 21:08: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: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to bug_status 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 21:08:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 Alexander Motin changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fs@FreeBSD.org |mav@FreeBSD.org Status|New |In Progress CC| |mav@FreeBSD.org --- Comment #6 from Alexander Motin --- I think those crashes are caused by lach of TRIM support in device removal code. This patch fixes alike crashes for me: https://reviews.freebsd.org/D17523 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 11 21:11:54 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A190810C81B4 for ; Thu, 11 Oct 2018 21:11:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3FD6B82888 for ; Thu, 11 Oct 2018 21:11:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 03A3510C81B3; Thu, 11 Oct 2018 21:11:54 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E65D110C81B2 for ; Thu, 11 Oct 2018 21:11:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8921782883 for ; Thu, 11 Oct 2018 21:11:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E69491120B for ; Thu, 11 Oct 2018 21:11:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9BLBq6C093290 for ; Thu, 11 Oct 2018 21:11:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9BLBqBu093282 for fs@FreeBSD.org; Thu, 11 Oct 2018 21:11:52 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 229007] [zfs] kernel crashes on remove disk Date: Thu, 11 Oct 2018 21:11:52 +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 Some People X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 21:11:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007 Alexander Motin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress Assignee|fs@FreeBSD.org |mav@FreeBSD.org --- Comment #10 from Alexander Motin --- At least some those crashes (zio->io_type =3D=3D ZIO_TYPE_WRITE (0x3 =3D=3D= 0x2)) are caused by lack of TRIM support in device removal code. This patch fixes al= ike crashes for me: https://reviews.freebsd.org/D17523 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 12 00:37:58 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3900C10CD16E for ; Fri, 12 Oct 2018 00:37:58 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670052.outbound.protection.outlook.com [40.107.67.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA9628A2CA for ; Fri, 12 Oct 2018 00:37:57 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM (52.132.44.160) by YTOPR0101MB1497.CANPRD01.PROD.OUTLOOK.COM (52.132.48.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.25; Fri, 12 Oct 2018 00:37:56 +0000 Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::65af:417a:161f:f4eb]) by YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::65af:417a:161f:f4eb%3]) with mapi id 15.20.1228.020; Fri, 12 Oct 2018 00:37:56 +0000 From: Rick Macklem To: Peter Eriksson , Felix Winterhalter CC: "freebsd-fs@freebsd.org" Subject: Re: NFSv4 Kerberos mount from Linux Thread-Topic: NFSv4 Kerberos mount from Linux Thread-Index: AQHUW9DS+OLl3kMYEUaTZ7pIOOpJR6UPKibngAl2Y4CAAGctboAAu6iAgAEEoaU= Date: Fri, 12 Oct 2018 00:37:55 +0000 Message-ID: References: <30f6446c-6fed-4b1e-9cae-9c417974ec46@audiofair.de> , <33A0F0BC-4AD8-4DE3-B484-42B7FB208B6A@ifm.liu.se> In-Reply-To: <33A0F0BC-4AD8-4DE3-B484-42B7FB208B6A@ifm.liu.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1497; 6:JfN/EjNqgWTcBMpPwS0G/VCF+KDXD2306Lxh0SZYZ4LhKtBsgrBeKuacIOPOUsB+fbcgfpp5TFW2clkYLdIVBgoiwars6ELxLKdH2VpieR8UMcN4YUlNk41kgnQ1Iw5B5i/cwG0Ahn9Sqdglb5UqsEcj4DXrq1rbv95IRIRV5T1ugvqpOnPJfSrl/kWLiFqkuot8lMD8BhYKVx1t5Tp2MR33YbwQ0gv7ZKPDXrZPhkujS/6LIZFMR9TAVFRIh1ThsAscM4hNqq641XFDVp91nUmPE7OcxKF1T4BHhkLyyx02vtDlxJK0VFbQN5gmbQ8cR8tmMjXhGyk4f3H98vKaRdmZT0RgTOmp6KjygWQK9T2z+vMiEHkSj+TEcAToMIuNpm43qwgy1vR8T6oSmeBVkuMyy18AcDKFBsq1xXcJppaiBXCq5SGq95xW4qRf6TZBN+4pC/A+8WyuOigIkGeq7w==; 5:qwYNFj0fUuSWv1BtRkY2mkQqyyiazQ+riiw1Da8Yt2SCxIst1sbYJhdvc8wCA8cPvHbh3Gy41TanJBRxL8fZM/t6oXPQ51nTJ3+hKzsMLkzhKGIPkESsGEvPc8rpmja68QJDa5vW9wn0ONTCykmV/gWbZroWRCUHTiz9G9njx/8=; 7:Wxg8ckPu9TOuH9FkBKUju7mu1lQAlvwfIDvF1QxKqLPzWNmmUmnAUKgIvVjTkDFPjq1+TST+I5kcsm6h2cxNHru5WId7XgeswTRFobGvHnb/JCJhk15juioYi2FMUQF8dGevPgZzOyZMWXqLtdXriDVf4heE4onq05a6tupw6rOHTx4eprTwXz/3dkV0oz0JHSkJ5TdtpCD3YR2/tRC6cT2O3yaD1jLJH14bvEu8nBx7uElvgImn0bltkBXzPaOl x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 438287dc-9696-4aec-4dc2-08d62fdaf3db x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1497; x-ms-traffictypediagnostic: YTOPR0101MB1497: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(788757137089)(12572780692934)(269456686620040)(192374486261705)(75325880899374)(18154293887054); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231355)(944501410)(4982022)(52105095)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051); SRVR:YTOPR0101MB1497; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1497; x-forefront-prvs: 0823A5777B x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(39860400002)(346002)(136003)(366004)(51444003)(189003)(199004)(486006)(99286004)(106356001)(105586002)(46003)(11346002)(446003)(256004)(476003)(71200400001)(305945005)(71190400001)(81156014)(8676002)(81166006)(14444005)(102836004)(8936002)(33656002)(74482002)(76176011)(7696005)(186003)(110136005)(9686003)(53936002)(53546011)(55016002)(6306002)(6506007)(6436002)(2900100001)(93886005)(229853002)(74316002)(5660300001)(6246003)(97736004)(5250100002)(68736007)(14454004)(4744004)(966005)(45080400002)(25786009)(786003)(2906002)(316002)(478600001)(86362001)(4326008); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1497; H:YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: Iy+Y+NaaCePCeiQVglD5CN+6OTqejORVXD3m9xFCUtvBMjAY94Qtaq1yXDZVy5ne/VXjyw2/S5CdrDOhlyruC39zReUwf42VHBGqsiPkZA3w0oW7KEat7Bb43/JvQd7qlrJO/NH2rHl5X6/IU+XtjjYBpOKVGm9/aYPrwZgZQAmRvLhqs8mgLmFrBkX4AshG1dmW44dVtnsg5MQ/51ZBmquE2qDf03p1G7eCTtvohWrLHMR+WGRaU6e2jrkCiIBYLBT7LiMgyu3qidH4v/ihXgVMq1K6OLdI+i7PZRhrgO65qSZx/hJ9Btdlko8OCGvI5no0sSiZDlzkKfaB8lSGl5affkGqw0SjRIkJaQbIl0U= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 438287dc-9696-4aec-4dc2-08d62fdaf3db X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2018 00:37:55.8954 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1497 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 00:37:58 -0000 From: Peter Eriksson wrote: >Just a few comments (random brain-dump) in case someone else is having pro= blems >with NFS & Kerberos. > > >We=92ve been using NFSv4 with Kerberos from Linux clients here for many ye= ars (with >Solaris-based NFS servers and MIT Kerberos) and lately using Fre= eBSD as the NFS >server OS (in an Microsoft AD Kerberos environment). I agree with the other post that this is a very useful document and it woul= d be nice to keep it somewhere where it is easier to find than in the mailing li= st archive. I don't know where that could be, so hopefully someone else in FreeBSD-land can suggest a good place? The one area you don't discuss (and maybe isn't really a problem?) is what ticket encryption type(s) you use. Kerberized NFS still uses DES (someday this may change, but I think that re= quires implementation of RPCSEC_GSS V3), so it needs an 8byte session key. (I have never seen a documented way to convert a session key of greater tha= n 8bytes into an 8byte session key for RPCSEC_GSS to use. As such, I have no= idea what happens if you choose a ticket encryption type that results in a grea= ter than 8byte key.) Here's a couple of minor comments: [lots of good stuff snipped] >4. rc.conf (we have a lot of users in our AD so we have to use a large num= ber for >usermax, replace =93liu.se=94 with your NFSv4 =93do= main=94 for >nfsuserd_flags) > >gssd_enable=3D"YES" >nfs_server_enable=3D"YES" >nfsv4_server_enable=3D"YES" >nfscbd_enable=3D"YES" Since the nfscbd is only used by the client (and only when delegations or p= NFS is enabled in the server), I believe this is harmless, but unnecessary for th= e server. >mountd_enable=3D"YES" >nfsuserd_enable=3D"YES" >nfsuserd_flags=3D"-manage-gids -domain liu.se -usertimeout = 10 -usermax 100000 16" > Btw, if you have many clients doing NFSv4.0 mounts, tuning of your DRC is a= dvised. (The defaults are for extremely small NFS servers.) NFSv4.1 mounts don't us= e the DRC, so if that is what your clients are doing, this isn't necessary. It's a little off topic, but for NFSv4.0 (and/or NFSv3) mounts and a reason= able sized NFS server, reasonable settings in /etc/sysctl.conf might be: vfs.nfsd.tcpcachetimeo=3D600 vfs.nfsd.tcphighwater=3D100000 vfs.nfsd.v4statelimit=3D10000000 vfs.nfsd.clienthashsize=3D10000 vfs.nfsd.statehashsize=3D10000 - If most/all of your mounts are NFSv4.1, then instead of the above, you mi= ght want: vfs.nfsd.sessionhashsize=3D10000 >5. Make sure you use NTPD so the clock is correct. > > >* All clients (Solaris 10, OmniOS, MacOS 10.12-10.14, FreeBSD 11.0-11.2, C= entOS 7, >Debian 9, Ubuntu 17-18 tested): > >1. Make sure FQDN is in /etc/hosts > >2. Make sure you use NTPD so the clock is correct. > >3. Have a =93host/FQDN@REALM=94 Kerberos host principal in /etc/krb5.keyta= b (nfs or >root is not needed for NFS-mounting to work) I'm guessing that you use the "gssname=3Dhost" mount option for your FreeBS= D clients? (The name after "gssname=3D" is whatever name you have before "/FQDN@REALM" for this principal name.) This is what I referred to as the host-based initiator credential. Thanks for posting this, rick 4. We use a fairly default /etc/krb5.conf, sort of like: [libdefaults] default_realm =3D REALM dns_lookup_realm =3D true ticket_lifetime =3D 24h renew_lifetime =3D 7d forwardable =3D true default_ccache_name =3D KEYRING:persistent:%{uid} KEYRING probably only works on Linux and there are some problems with KEYRI= NG in Debian & Ubuntu since not everything in it supports it due to them us= ing Heimdal instead of MIT (like for smbclient) but it mostly works. Works = fine in CentOS 7 though - in general CentOS 7 feels more =93enterprise=94-r= eady than Debian & Ubuntu. The old classic FILE-ccaches should work fine th= ough. For mounting we use the automounter and a "executable map=94 (perl script) = that looks up records in DNS (Hesiod-style) since the built-in Hesiod suppo= rt in most automounters is a bit.. lacking. Works quite well. You can find = the scripts we use here: http://www.grebo.net/~peter/nfs (The dns-update scripts use data from an SQL database so probably isn=92t d= irectly usable to anybody else. We use the same SQL database to populate a = locally developed BerkeleyDB-based NSS-database on each FreeBSD server in o= rder to speed things up since AD/LDAP-looks with ~90k users and silly amoun= ts of AD groups takes forever, even with cacheing). Some Linux-specific stuff: Packages needed: CentOS: - nfs-utils - libnfsidmap - nfs4-acl-tools - autofs Debian: - keyutils - nfs-kernel-server # rpc.idmapd needs this due to a bug in Debian Ubuntu: - keyutils Other nice-to have packages: - hesiod - autofs-hesiod Some settings to check for: /etc/default/nfs-common: NEED_IDMAPD=3Dyes NEED_GSSD=3Dyes /etc/idmapd.conf (replace =93liu.se=94 with your NFSv4 =93= domain=94): Domain=3Dliu.se /etc/request-key.d/id_resolver.conf (should be there already if using a m= odern Linux and you=92ve added the packages above): create id_resolver * * /usr/sbin/nfsidmap %k %d MacOS: Basically require the latest - 10.14 (Mojave) - for things to work smoothly= . In theory 10.12 & 10.13 should work but there is some bug in them that ca= uses the OS to panic when you try to use NFS & Kerberos. 10.11 and earlier = doesn=92t support good enough encryption for us=85 But with 10.14 you just= need to get a Kerberos ticket and then you can mount things just fine. /etc/nfs.conf should contain (replace =93liu.se=94 with your= NFSv4 =93domain=94): nfs.client.default_nfs4domain=3Dliu.se (There are a lot of problems you can run into with Microsofts AD implementa= tion of Kerberos too that we=92ve had to be fighting with, but that=92s a w= hole other topic) - Peter On 10 Oct 2018, at 23:47, Rick Macklem > wrote: Felix Winterhalter wrote: On 10/4/18 5:21 PM, Rick Macklem wrote: [stuff snipped] I am now trying to mount this directory as root first without having to deal with user keytabs or tickets. This works fine with -sec=3Dsys and nfsv4.1 and nfsv3 and -sec=3Dkrb5p. This does not however work with nfsv4 and krb5p or any other krb5 flavor. Sorry, I'm not sure what you are saying here. Is it 1 - no version of NFS works for krb5p or 2 - NFSv4.1 works for krb5p, but NFSv4.0 does not or 3 - only nfsv3 works for krb5p [snipped lots of text] #3 is indeed what was happening. I could mount with krb5p for nfsv3 (which I was not aware was even doable) however nfsv4 would stubbornly refuse to do any mounting. Yes, RPCSEC_GSS was done by Sun for NFSv3 and it was a good fit, since NFSv= 3 does not have any server state to maintain. As such, all RPCs are atomic op= erations done by users (which for Kerberized mounts must have a TGT in a credential = cache). NFSv4 wasn't really a good fit for the model, because the NFSv4 server main= tains lock state (NFSv4 Opens are a form of lock used by Windows at file open tim= e). There are "state maintenance" operations that must be done by the user doin= g the mount (usually root), where they typically don't have a TGT in a creden= tial cache. --> The ugly solution for this is typically a host-based client credential = in a keytab on the client. (Usually a principal like "root/client-host.domain@REAL= M" or "host/client-host.domain@REALM" or "nfs/client-host.domain@REALM" in the default keytab on the client.) I have now after a lot of try and error figured out what I need to do in order to make it work. To start with I have kerberos credentials with both host/ and nfs/ on both client and server. Mounting nfsv4 shares with krb5p from a linux server has also worked in this context. Yes, I'm assuming that satisfied the host-based client credential as I desc= ribed above. I leave you to judge whether what I found out is intended behaviour or if something weird is going on. Yes, sounds like intended behaviour, since the client must have a Kerberos credential to use for the "state maintenance" operations that are not done = on behalf of a user. My exports file originally looked something like this: /nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=3Droot -sec=3Dkrb5p clients V4: /nfsTests -sec=3Dkrb5p clients Which allowed me to do nfsv3 krb5p mounts but not nfsv4 krb5p mounts. Changing the exports file to this: /nfsTests/ /nfsTests/testexport /nfsTests/otherexport -maproot=3Droot -sec=3Dkrb5p clients V4: /nfsTests -sec=3Dkrb5p,krb5i clients This suggests that there is a bug in the client, where it uses krb5i instea= d of krb5p at some point in the mounting process. (I have also seen cases where the cl= ient erroneously falls back on using sys at some point in the mounting process.) (You did mention before you were using the Linux client. If you are using a= FreeBSD client, I would be interested in looking at this.) Allows nfsv4 krb5p mounts to work for some reason I do not understand. Not setting the -sec option on the V4 line apparently defaults to -sec=3Dsys and doesn't allow any krb5 mounts. I'm not sure that this is a good default as I wasn't even aware that the -sec option needed to be set on this line. In FreeBSD, defaults are meant to maintain backwards compatibility. This me= ans that AUTH_SYS should work by default. Also, AUTH_SYS is what 99.9999% of FreeBSD NFS mounts still use, from what I've seen.) I've got packet traces of the nfsv3 krb5 and krb5i mounts and I'll make traces of the two nfsv4 mount attempts and send them to you if you're interested. I'm still not sure what exactly is happening here. The successful one for NFSv4 might be interesting. If you look at it in wireshark, I suspect you'd find somewhere during the mount that it did RPCs which were not krb5p and that would show why the addition of krb5i made it work. I did suggest you start with -sec=3Dsys:krb5:krb5i:krb5p and, once that wor= ks, remove the security flavours one at a time until the mount doesn't work. (Then you capture packets for the minimal case that does work and look at what security flavours the client is using for all RPCs done during the mou= nt.) You now know why almost no one uses Kerberized NFSv4 mounts. Unfortunately, the NFSv4 working group has never gotten around to a better solution. Discussion of a host based encryption technique using something like SSL has happened, but no one has gone beyond that. rick _______________________________________________ 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 Fri Oct 12 01:29:50 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32D9A10CE2E8 for ; Fri, 12 Oct 2018 01:29:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C300F8BC51 for ; Fri, 12 Oct 2018 01:29:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 875E710CE2E7; Fri, 12 Oct 2018 01:29:49 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75D8210CE2E6 for ; Fri, 12 Oct 2018 01:29:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1799A8BC50 for ; Fri, 12 Oct 2018 01:29:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5CB54134C4 for ; Fri, 12 Oct 2018 01:29:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9C1TmV9049682 for ; Fri, 12 Oct 2018 01:29:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9C1TmEv049681 for fs@FreeBSD.org; Fri, 12 Oct 2018 01:29: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 228750] panic on zfs mirror removal Date: Fri, 12 Oct 2018 01:29:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 01:29:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 Rodney W. Grimes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fs@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 12 03:32:06 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6F0510D0C36 for ; Fri, 12 Oct 2018 03:32:06 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 4A48C8F377 for ; Fri, 12 Oct 2018 03:32:06 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-cf9ff70000003ddd-99-5bc015adebfd Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 06.8E.15837.EA510CB5; Thu, 11 Oct 2018 23:31:58 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id w9C3Vq4i019074; Thu, 11 Oct 2018 23:31:54 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w9C3Vkgk022179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Oct 2018 23:31:48 -0400 Date: Thu, 11 Oct 2018 22:31:46 -0500 From: Benjamin Kaduk To: Rick Macklem Cc: Peter Eriksson , Felix Winterhalter , "freebsd-fs@freebsd.org" Subject: Re: NFSv4 Kerberos mount from Linux Message-ID: <20181012033145.GC3293@kduck.kaduk.org> References: <30f6446c-6fed-4b1e-9cae-9c417974ec46@audiofair.de> <33A0F0BC-4AD8-4DE3-B484-42B7FB208B6A@ifm.liu.se> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMKsWRmVeSWpSXmKPExsUixG6nortO9EC0QesvI4s/b16xWBx7/JPN Yubcn6wWD5ddY3Jg8Zj+2dRjxqf5LB4brl9j9Pi9eS9TAEsUl01Kak5mWWqRvl0CV8aZI/tY C+YrVHxf1s3WwDhVqouRk0NCwETi2NIrLCC2kMBiJolbWzS6GLmA7I2MEp+OP2OBcK4ySZze coMJpIpFQFVi76Q5YDabgIpEQ/dlZhBbREBdYvPqfmaQBmaBLkaJCU2zwMYKC+gANbewgti8 AsYSi+fdhpq6jlli0e7FLBAJQYmTM5+A2cxAk/7MuwQ0iQPIlpZY/o8DIiwv0bx1NtgyToFE iRNvG8GOEBVQltjbd4h9AqPgLCSTZiGZNAth0iwkkxYwsqxilE3JrdLNTczMKU5N1i1OTszL Sy3SNdPLzSzRS00p3cQIDn8X5R2ML/u8DzEKcDAq8fD+mLg/Wog1say4MvcQoyQHk5Ior+0n oBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR3r6fQDnelMTKqtSifJiUNAeLkjjvxJbF0UIC6Ykl qdmpqQWpRTBZGQ4OJQneVyIHooUEi1LTUyvSMnNKENJMHJwgw3mAhmcJA9XwFhck5hZnpkPk TzHqcrQ9vT6DWYglLz8vVUocYpAASFFGaR7cHFDaksjeX/OKURzoLWHeAyBVPMCUBzfpFdAS JqAlp0L2gCwpSURISTUwuj53tKyZ6mDft+yi0N5nj3QEmsKfR83YVXFC/zjPXcHkOZd9Qr/K fC+ZU89w5+UEFhUlLluvIym9P15efLC+cJKOJ9uaNxmrL3Xc2nwgZZVD0P/duRqnt/1KYl7m MOvXqZ+rLn0R3+7WK9Fne1P0yLIIlei6s8dyp0oq5q//e/7cY46X/cqru5VYijMSDbWYi4oT AXOQoL82AwAA X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 03:32:07 -0000 On Fri, Oct 12, 2018 at 12:37:55AM +0000, Rick Macklem wrote: > From: Peter Eriksson wrote: > >Just a few comments (random brain-dump) in case someone else is having problems >with NFS & Kerberos. > > > > > >We’ve been using NFSv4 with Kerberos from Linux clients here for many years (with >Solaris-based NFS servers and MIT Kerberos) and lately using FreeBSD as the NFS >server OS (in an Microsoft AD Kerberos environment). > I agree with the other post that this is a very useful document and it would be > nice to keep it somewhere where it is easier to find than in the mailing list > archive. > I don't know where that could be, so hopefully someone else in FreeBSD-land > can suggest a good place? > > The one area you don't discuss (and maybe isn't really a problem?) is what > ticket encryption type(s) you use. > Kerberized NFS still uses DES (someday this may change, but I think that requires > implementation of RPCSEC_GSS V3), so it needs an 8byte session key. This isn't true anymore; you can use stronger session keys just fine. (See also RFC 6649 -- don't use single-DES!) > (I have never seen a documented way to convert a session key of greater than > 8bytes into an 8byte session key for RPCSEC_GSS to use. As such, I have no idea > what happens if you choose a ticket encryption type that results in a greater > than 8byte key.) We did have this problem in the AFS world, and are currently using this hack: https://tools.ietf.org/html/draft-kaduk-afs3-rxkad-k5-kdf-00 > Here's a couple of minor comments: > [lots of good stuff snipped] > >4. rc.conf (we have a lot of users in our AD so we have to use a large number for >usermax, replace “liu.se” with your NFSv4 “domain” for >nfsuserd_flags) > > > >gssd_enable="YES" > >nfs_server_enable="YES" > >nfsv4_server_enable="YES" > >nfscbd_enable="YES" > Since the nfscbd is only used by the client (and only when delegations or pNFS is > enabled in the server), I believe this is harmless, but unnecessary for the server. > >mountd_enable="YES" > >nfsuserd_enable="YES" > >nfsuserd_flags="-manage-gids -domain liu.se -usertimeout 10 -usermax 100000 16" > > > Btw, if you have many clients doing NFSv4.0 mounts, tuning of your DRC is advised. > (The defaults are for extremely small NFS servers.) NFSv4.1 mounts don't use the > DRC, so if that is what your clients are doing, this isn't necessary. > It's a little off topic, but for NFSv4.0 (and/or NFSv3) mounts and a reasonable > sized NFS server, reasonable settings in /etc/sysctl.conf might be: > vfs.nfsd.tcpcachetimeo=600 > vfs.nfsd.tcphighwater=100000 > vfs.nfsd.v4statelimit=10000000 > vfs.nfsd.clienthashsize=10000 > vfs.nfsd.statehashsize=10000 > - If most/all of your mounts are NFSv4.1, then instead of the above, you might want: > vfs.nfsd.sessionhashsize=10000 > > >5. Make sure you use NTPD so the clock is correct. > > > > > >* All clients (Solaris 10, OmniOS, MacOS 10.12-10.14, FreeBSD 11.0-11.2, CentOS 7, >Debian 9, Ubuntu 17-18 tested): > > > >1. Make sure FQDN is in /etc/hosts > > > >2. Make sure you use NTPD so the clock is correct. > > > >3. Have a “host/FQDN@REALM” Kerberos host principal in /etc/krb5.keytab (nfs or >root is not needed for NFS-mounting to work) > I'm guessing that you use the "gssname=host" mount option for your FreeBSD > clients? (The name after "gssname=" is whatever name you have before > "/FQDN@REALM" for this principal name.) > This is what I referred to as the host-based initiator credential. I'm told that the Linux client will automatically attempt to use any of root/, host/, or nfs/ credentials as an NFS client. This is incredibly frustrating to me (not least because of the amount of confusion it perpetuates about how NFS with Kerberos is hard!), and is decidedly not Kerberos best practices. I would probably have specified a new host-based service name, like nfscl/, though I guess there is some argument that root/ is reasonable. > Thanks for posting this, rick And thank you for the extra tips! -Ben From owner-freebsd-fs@freebsd.org Fri Oct 12 15:14:32 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3E7210C11EC for ; Fri, 12 Oct 2018 15:14:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3FEC986F8B for ; Fri, 12 Oct 2018 15:14:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 058DF10C11EB; Fri, 12 Oct 2018 15:14:32 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E884210C11EA for ; Fri, 12 Oct 2018 15:14:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45B3486F59 for ; Fri, 12 Oct 2018 15:14:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 4EC8B1A7A0 for ; Fri, 12 Oct 2018 15:14:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9CFESFb020470 for ; Fri, 12 Oct 2018 15:14:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9CFESqM020462 for fs@FreeBSD.org; Fri, 12 Oct 2018 15:14:28 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 228750] panic on zfs mirror removal Date: Fri, 12 Oct 2018 15:14:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 15:14:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 --- Comment #8 from commit-hook@freebsd.org --- A commit references this bug: Author: mav Date: Fri Oct 12 15:14:22 UTC 2018 New revision: 339329 URL: https://svnweb.freebsd.org/changeset/base/339329 Log: Add ZIO_TYPE_FREE support for indirect vdevs. Upstream code expects only ZIO_TYPE_READ and some ZIO_TYPE_WRITE requests to removed (indirect) vdevs, while on FreeBSD there is also ZIO_TYPE_FREE (TRIM). ZIO_TYPE_FREE requests do not have the data buffers, so don't need the pointer adjustment. PR: 228750, 229007 Reviewed by: allanjude, sef Approved by: re (kib) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D17523 Changes: head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_indirect.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 12 18:39:20 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 375A010C683D for ; Fri, 12 Oct 2018 18:39:20 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8947E8FE90 for ; Fri, 12 Oct 2018 18:39:19 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([5.144.193.244]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MfVYB-1g0nig3xlb-00P3He for ; Fri, 12 Oct 2018 20:39:10 +0200 Received: from moby.local ([5.144.193.244]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MfVYB-1g0nig3xlb-00P3He for ; Fri, 12 Oct 2018 20:39:10 +0200 To: FreeBSD Filesystems From: Nikos Vassiliadis Subject: zfs allow reports empty username Message-ID: Date: Fri, 12 Oct 2018 21:39:01 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:8K9m5Ngjxnzq49AEAGewUayRPw04vo86k15YBerGS5VAlrEbb6S DVy7IC+eMdne0Gq7pWCTebBor0cn1EhQ4xn4gMzGF5667WeOCLfAtzczUqFeanoW0NLYsIg PaqjSAeFOSqmBeGfV06jKZyu9UVssUbOeRXUOrFuzwahr7AKeWomVaYlCAIMvAVkRaZf1VZ ZTVNhwRpulMQ8JR4Nvl7w== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V01:K0:BU3AxGaJvcc=:kASCIEZEN0c5K1CQJLd+Bo IX9zujl1Iaok9+x6fLVMnm5eczZIJ7aHRPIEEE0aVW9Bs/Qxg2LDDM6AMSnpNtG2Yc0NgjffC ePDBMsg78SwmyVMU7Z0zslG/hnBo6e8p44MALJPAiTE8KTwXFAcN34/TbBmx074mxTuOP5wEv yMc/ScXYRUCSCvGubX1G3kM1lAeTdQ1qJivOZ4ePYML8pOnYRQE5UJc3i2QyEg9IgwgerTxuM kR9AKVwLROuTfO09e0D2d0+AJ00tCQLOz6Re+XHpcwGa9gPqktb00VEKrV5PSGN5j3KKM/aCZ A/AfrweOoNL/jzZMyCVX+VgERj19ChGUF2WCgvLrHTFBa6Y3QQkX3VYIBVwCUdzh1IL2OhTev AgcjD87chVyZk6tp6STyu+6PThhjIl68feh75fs3PUMJnHucmQyGHVEK5GAqvKqWTC1Dt8ccr 4jZQqrt0kG/z+LOIINHiqNggIUz/45RD2UBYw7EQ2R0IvRUjjM3A5GVPEJPiFkhFGvNnaCsXj kxa9qzCwo2TEN7yTAqpyyCK7DZwFbjTKNNViNNO6JJx0yQvZUacqOqOzyUGks3GzVCnPMTO40 m8uqP36dk0RtNxsfNqjPpUYoGh3ptm49BIkDYYNh7eq4j+2BZud0kuqddMgZlKUnw/zNdTcBq YmcwM3O7pDQ7R4SrEuM/W/dlXf7H7l/P//ptxcxOmXk0xmZsZv2ke7BAwr8XFC7Yg1kTb1jO7 eFqJosM/u363LYfhMZkT8kdIxdgntmP65xkFGYY4zJsTORnD54Iy8eYb+HlCS91BDzktXj+gS nHF8HTGnxLvACB1CTQvdc6tkJW0axwSgQnwJBdGse2ht+oX670= X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 18:39:20 -0000 Hi, On a backup server that runs FBSD-11.2-RELEASE I noticed that 'zfs allow' reports an empty username:> root@hermes:~ # zfs allow storage > ---- Permissions on storage ------------------------------------------ > Local+Descendent permissions: > user backup compression,create,destroy,groupquota,groupused,mount,mountpoint,receive,snapdir,sync,userprop,userquota,userused > user compression,create,destroy,groupquota,groupused,mount,mountpoint,receive,sync,userprop,userquota,userused I don't recall adding a username and later removing it. Any ideas how to remove this? Thanks in advance! Nikos From owner-freebsd-fs@freebsd.org Fri Oct 12 19:47:56 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCC1C10C8932 for ; Fri, 12 Oct 2018 19:47:55 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 5975A72DB6 for ; Fri, 12 Oct 2018 19:47:55 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id AF42421AC2; Fri, 12 Oct 2018 15:47:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 12 Oct 2018 15:47:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=bhQpWro7fM76HbUomsX558RbYWB rcAwVLYxGwEk9mhk=; b=TvWI+Z+8TozWZTyczPF7uL3xOyzNVq0FnWjpMU+dOcQ p7J34JeltijJQ7QWuOmPGj2gPaxodPi/6I/keT8llit1nGoxS0ViQj+JUY68R+pn fR8lq4E8sS3jkVN2NyAH69Ob3sN9asMIbdoEi/mzvQJcl6X23UEjWAFeKvpmlOxM D4Sq3aEAnP0FHk39abtqH1auXE5vwnFdrs9coS2FbQebs4Kb/Tm7iO8EI7UCz1U2 8c4UgnEOH/nKPce8V0rCQAznQebm5vd6XYipt48mv3HZpvkYWtFC6fbTPtwrkz8i iHSgjl2/UoklpnPIL9LPex4L+3Ft8zm76J820nOfgzw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=bhQpWr o7fM76HbUomsX558RbYWBrcAwVLYxGwEk9mhk=; b=UlVs7T9VO3PCaOIeya1y28 NT3Fq7qej8mr+8GUjCOcWyPrVpGuJec1UtbdP9CIffmPoC1SMnBFi2pc+6CIWkDY +F9vcVrOob2Beh2ktZrTN93BPpeopmHTYBSKSwueStNXIdYdtk2rf3klrScYC/0A nyMh7Cn+xdm93b/d2Kj454zlaxWMY0kySgESTRJzF6lKiTiIPEm3/mk1BeZrvlZN fRlf2jKtw7wTgtGX6Se9Ml4ty//cfi+wbpRZYBQxChnl0jORk/h0JkNGekqbybvr 9iJH+TaRrH3+jG/qHmHINyfcUDOnPeJdgZREVl2TyY2eBeDYEukTuEvSuJwuC9ig == X-ME-Sender: X-ME-Proxy: Received: from [192.168.1.2] (unknown [94.233.225.150]) by mail.messagingengine.com (Postfix) with ESMTPA id E78DC102D7; Fri, 12 Oct 2018 15:47:46 -0400 (EDT) Subject: Re: zfs allow reports empty username To: Nikos Vassiliadis , FreeBSD Filesystems References: From: Yuri Pankov Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= xsBNBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAHNH1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD7CwJcEEwEIAEECGwMFCQWjmoAF CwkIBwMFFQoJCAsFFgMCAQACHgECF4AWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW708wAIZ AQAKCRCTi+B/sSrhbPxBB/961alcU091O+yKT5/oReHVc/PX0Tz4sW3V44AcgLfYlrZavCro EFz90qmCrl0xqEwuAKcC4bjmL8SjPWAhSN6IH9nxdw+HeZnAPiHm/q679Bu47+nHBl3qD/9p +t1PkKeKZfaWToFMt1nq06ytSu6VLMCwLdlDNe6DReX0ex/afEqKsuaIZSKL4UYjRwklp8PU Uf98QkrfapyHB67hQMzfI4tPeJaYyv0cTgfq3kUWJx1V6Xi0b6Zxj4ZrB2TXvaMO5g7yhU9E E3WWAvoe4FgB3a7dHe8atnHhq5+Cuvm6+LD4Jh7jvMAE5UMN+xxQpnGpNghHjaCy4vXrLRBZ nhRYzsBNBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFSc XACDsdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIol Dahy2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CA NN8F1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC 0sE2Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4z ABEBAAHCwHwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAK CRCTi+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuU D3kh2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy +jsnTfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6 Kv+VRu54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2v ZHBB6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: Date: Fri, 12 Oct 2018 22:47:22 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="360vkasmzsfoesYauVjyqFsQ7anUJMpTI" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 19:47:56 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --360vkasmzsfoesYauVjyqFsQ7anUJMpTI Content-Type: multipart/mixed; boundary="RrytlFWDD7ALlvz5n2Cu5rEazXY7soWBA"; protected-headers="v1" From: Yuri Pankov To: Nikos Vassiliadis , FreeBSD Filesystems Message-ID: Subject: Re: zfs allow reports empty username References: In-Reply-To: --RrytlFWDD7ALlvz5n2Cu5rEazXY7soWBA Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Nikos Vassiliadis wrote: > Hi, >=20 > On a backup server that runs FBSD-11.2-RELEASE I noticed that > 'zfs allow' reports an empty username:> root@hermes:~ # zfs allow stora= ge >> ---- Permissions on storage ------------------------------------------= >> Local+Descendent permissions: >> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 user backup >> compression,create,destroy,groupquota,groupused,mount,mountpoint,recei= ve,snapdir,sync,userprop,userquota,userused >> >> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 user=C2=A0 >> compression,create,destroy,groupquota,groupused,mount,mountpoint,recei= ve,sync,userprop,userquota,userused >> >=20 > I don't recall adding a username and later removing it. Any ideas how t= o > remove this? You *could* try temporarily applying the patch from https://github.com/openzfs/openzfs/pull/690 (you'll need to fix the paths, of course) and check if it would turn out to be a username you deleted after all :-) --RrytlFWDD7ALlvz5n2Cu5rEazXY7soWBA-- --360vkasmzsfoesYauVjyqFsQ7anUJMpTI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlvA+ksACgkQk4vgf7Eq 4Wxp0wgAnjBtmbsfoPZldCS52lCyuZCTyOwFzZkYE573jTN0/mAGwHd1CzQFhMPE FUijexgPdFS6yS41+Ho8zPTMitLilPi9Iq6vtxB4dzxdK93pas3W2ZgI1jCuswiC PCaReAGUQBVuucmgbNwXf5DeGPB1NG+mjGznHe6TC1yfqHauziMk4hC1+lDzOoiB w3mviWFR46Uwt8GacGj3w54iboDLAGqAM2oUjZmBkWvLpVJvB0NQTXCVAIeqr5LF UQeZsfmu3zwzr/Mw8piAj0RbfYttlLKOG6/cuQmvnR+R2Gz+73qBXjLjbAtKxGlN o+D2CECxe3zt4bBs4B6wefCC2+rgwg== =Hh/f -----END PGP SIGNATURE----- --360vkasmzsfoesYauVjyqFsQ7anUJMpTI-- From owner-freebsd-fs@freebsd.org Fri Oct 12 22:36:45 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8F2010CD2C1 for ; Fri, 12 Oct 2018 22:36:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 77AEF7950A for ; Fri, 12 Oct 2018 22:36:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3C5E710CD2BC; Fri, 12 Oct 2018 22:36:45 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B37A10CD2BB for ; Fri, 12 Oct 2018 22:36:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C2AEF794FE for ; Fri, 12 Oct 2018 22:36:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 043B41E4FB for ; Fri, 12 Oct 2018 22:36:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9CMah8u049670 for ; Fri, 12 Oct 2018 22:36:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9CMahA9049669 for fs@FreeBSD.org; Fri, 12 Oct 2018 22:36:43 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 232175] [panic][zfs] solaris assert: HDR_EMPTY(hdr), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c, line: 6213 Date: Fri, 12 Oct 2018 22:36: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: 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: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 22:36:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232175 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 Fri Oct 12 22:37:12 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CB3A10CD323 for ; Fri, 12 Oct 2018 22:37:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CA4907959A for ; Fri, 12 Oct 2018 22:37:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8EFA810CD320; Fri, 12 Oct 2018 22:37:11 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DCBB10CD31F for ; Fri, 12 Oct 2018 22:37:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 203AB79597 for ; Fri, 12 Oct 2018 22:37:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6E2701E4FD for ; Fri, 12 Oct 2018 22:37:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9CMbAtJ050091 for ; Fri, 12 Oct 2018 22:37:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9CMbAkA050089 for fs@FreeBSD.org; Fri, 12 Oct 2018 22:37:10 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 232152] unrecoverable state after zroot is filled with data to 100%, can't boot, can't import Date: Fri, 12 Oct 2018 22:37:10 +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.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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 22:37:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232152 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 Sat Oct 13 00:44:37 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90C8210D0C3A for ; Sat, 13 Oct 2018 00:44:37 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670087.outbound.protection.outlook.com [40.107.67.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8323E7E13F for ; Sat, 13 Oct 2018 00:44:34 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM (52.132.44.160) by YTOPR0101MB1513.CANPRD01.PROD.OUTLOOK.COM (52.132.48.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1185.25; Sat, 13 Oct 2018 00:44:32 +0000 Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::65af:417a:161f:f4eb]) by YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::65af:417a:161f:f4eb%3]) with mapi id 15.20.1228.020; Sat, 13 Oct 2018 00:44:32 +0000 From: Rick Macklem To: Benjamin Kaduk CC: Peter Eriksson , Felix Winterhalter , "freebsd-fs@freebsd.org" Subject: Re: NFSv4 Kerberos mount from Linux Thread-Topic: NFSv4 Kerberos mount from Linux Thread-Index: AQHUW9DS+OLl3kMYEUaTZ7pIOOpJR6UPKibngAl2Y4CAAGctboAAu6iAgAEEoaWAADiTAIABYEo1 Date: Sat, 13 Oct 2018 00:44:32 +0000 Message-ID: References: <30f6446c-6fed-4b1e-9cae-9c417974ec46@audiofair.de> <33A0F0BC-4AD8-4DE3-B484-42B7FB208B6A@ifm.liu.se> , <20181012033145.GC3293@kduck.kaduk.org> In-Reply-To: <20181012033145.GC3293@kduck.kaduk.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1513; 6:lK8JXoYKqHPhP0tZy2kqozkDUvJ8yEYlw9FhFlVQCp5duv8IypQyTKKuW3P/NEDR7dqxf6nf61C5AJ3vGRBX3k4srg56boLTuHNJLJx8t1aKlNL1hxH8jWqIBpnHqHDznlY9uQYlLVj9Nz++3SXRuZKEb9wX7f/iPOTIGMS9J9d2rbD6C0oA/WFWF6v7zm8SHnWtUny/iQIZKYHYi/vanE/l6SMya4hhXgUzURn/fVMID7MIyDdTmr/2zLSFH8vdnERMY9DtbdBbsR4Mb0Uh4LehdVdbQnT+TMJbo4P4yrPA8mPfS507AJ0j5lVD415qcfF/hqrw05GAMRiyu3V1AN8l/sr2b7R1+PWS++3ewe3ZDRXUsJwSXrMfmCgcdGU6iaJ+nqVZvPbSTyFHJ4OL3T7+bxM6Gax9irl1S1m9LuZ5pzAOar7a0AVXMQUo7mEm5XmaNJwy3ZV6nqmGOL/0jQ==; 5:RRYyVPVB9RaqKGDWdxCWyNkaPQDIdnPuneFKvF3S/Io5toAt0z9QS8FuB6arF4QLlxbrI9rq71vmKfg/oNZXDA7lBWjI8FO89dNv9bciV04NvwPOBX3qwQ5UxCBxZKC1AnOgxjpHqVsKSu72un/e3O3SToXgD9hJU3Yy5jeCOo0=; 7:OX42tDSCNBXnLdKyrBxSs7+PswoY1uNnI+aifpGkejDDIZpG4vZg/66vtv4dhfMH7Ox08cd9PN8HGg8Vtl21DD5tgKrOzhtS26SdeyxqjsCzwGbrlrbpNUm16CROgt8QA24gqQ6/E26r2uIGyhb5AzIYkfSS6mBIvUXs3svHDR0IcIvp54WA3gCPkn/j4WAk5ie9QG7monwlEuJWyBiDhVM/bimY/ZPsn7vIRMqDWYLPmSQQHk0nwN/lFlbw5Y+6 x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 43826ce1-7129-4de9-6376-08d630a50aac x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1513; x-ms-traffictypediagnostic: YTOPR0101MB1513: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231355)(944501410)(52105095)(3002001)(149066)(150057)(6041310)(201703131423095)(201703031522075)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(201708071742011)(7699051)(76991067); SRVR:YTOPR0101MB1513; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1513; x-forefront-prvs: 082465FB26 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(376002)(346002)(39860400002)(136003)(199004)(189003)(51444003)(74316002)(786003)(446003)(71190400001)(71200400001)(68736007)(6246003)(93886005)(86362001)(33656002)(186003)(97736004)(46003)(486006)(81166006)(99286004)(102836004)(4326008)(316002)(8676002)(2900100001)(81156014)(296002)(54906003)(229853002)(25786009)(14454004)(74482002)(6436002)(305945005)(6506007)(105586002)(106356001)(11346002)(5250100002)(6916009)(2906002)(2171002)(53936002)(9686003)(8936002)(5660300001)(7696005)(76176011)(14444005)(55016002)(256004)(476003)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1513; H:YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: ajH0qcTCMUU0Y+EbidEvjhPX0RK2g04BP0O31ezOrzawCTrhhPdIuRhinuXdBUII7EyFdrCE626yYMN3xI+bBp8X0fXzPB8u2WHMh7O7sqNYIIrig1VjiKXROYqdaVUDGeuiFGeZ+xgsPczm8nVhSpDLbyzoApA/2MfKg/uhm2uapfH/kQdJ4OpgX6Kgx9558fTY9fXdd3gfR4si7TisPggBP2eVR82WjnTMMUughRdQVHZ/4hua1cO3KVZXuoYNHelMTHeToyBOUZCHEzf1Q7LORRGr+Vyp40zjyV+U8mvfrSh4V+gF/PZ4pOJmpV8GMzqNOBSAALazLrVZMuLI5zFGXI965FGxXDoCm3ZRXt0= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 43826ce1-7129-4de9-6376-08d630a50aac X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Oct 2018 00:44:32.4779 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1513 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 00:44:37 -0000 Benjamin Kaduk wrote: >I wrote: >> >> The one area you don't discuss (and maybe isn't really a problem?) is wh= at >> ticket encryption type(s) you use. >> Kerberized NFS still uses DES (someday this may change, but I think that= requires >> implementation of RPCSEC_GSS V3), so it needs an 8byte session key. > >This isn't true anymore; you can use stronger session keys just fine. >(See also RFC 6649 -- don't use single-DES!) I haven't read RFC6649, but from looking at the kgssapi code in FreeBSD's head/current, it appears that newer encryption types are used for wrap/unwr= ap (krb5p). >From what I can see, the following appear to be supported: DES, DES3, AES128, AES256, Arcfour, Arcfour_56 (I'll have to look at RFC6649 someday, because I've never seen an RFC speci= fying anything but DES for RPCSEC_GSS.) I won't even try to guess whether all of the above work for all implementat= ions, but it appears that it uses whatever the session key is (krb5_key_state?). Peter, do you happen to know what encryption type(s) you have been using? >> (I have never seen a documented way to convert a session key of greater = than >> 8bytes into an 8byte session key for RPCSEC_GSS to use. As such, I have= no idea >> what happens if you choose a ticket encryption type that results in a g= reater >> than 8byte key.) Ignore this. I just wasn't correct. rick [good stuff snipped] From owner-freebsd-fs@freebsd.org Sat Oct 13 01:33:33 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E936E10D315A for ; Sat, 13 Oct 2018 01:33:32 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A91180B4B for ; Sat, 13 Oct 2018 01:33:32 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([5.144.193.244]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MF4iR-1gQrG20cJ9-00GEHq; Sat, 13 Oct 2018 03:20:29 +0200 Received: from moby.local ([5.144.193.244]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MF4iR-1gQrG20cJ9-00GEHq; Sat, 13 Oct 2018 03:20:29 +0200 Subject: Re: zfs allow reports empty username To: Yuri Pankov , FreeBSD Filesystems References: From: Nikos Vassiliadis Message-ID: <90dcc7f1-69fe-ea2c-5c50-e3025572492a@gmx.com> Date: Sat, 13 Oct 2018 04:20:16 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:YlYywVMx3HYZlkMwuJCKbyxQuVadOV3TymazZCrD9ZhJXNQeDM9 erRx9ob+HONn0Hv3hjyUoU2VJo5i8s2wwhZofGnc6gSY6kPAsN6odMtd0Afmm52Rg+BwyXZ yfXxZtXCAuTGQbKtT1Uq77ZOmTqRwnpLa2vV8DZGupaMt344qIdJMIVwaYvfywLR/Cf/Fh+ FF5Zkl4/bSwDuZIsuTGAQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V01:K0:bhePlx2/R4k=:3bQ6eVSFQncE8RXVoxNj6+ MyxDkrNKiGq9ilMlM4B9eamy01j3UmpAb9xXR50oUjjkG/YcDS5lqg1LV1+IEjja0CG6Tc7LN dLdfjEFsEeBiDAPueOrGzjU3JKfHss9QFlg3giYelf/UN4A+thU6uZWjqHcofnSoxfupLhHOY w782ryT7ehnHTzb4Vy8jsbmV19CXl7SAVxYCl6ILgjhVcxmnMNBcHFdQV+fp+CANXoXgd0fSv AdiUbjvv9z7v6ohdNadNFWRWflyd1RUfmQfMUCg5QgSFlX84VPV5qjPUnwArW83H2rJpL+pFG OZFBuDxD3Uh8e3EtGWUbpFhlRPcVRdKRk9QObHpmj+EAGw06rbm9JyOshAckfixhQ64IGeAI1 4tL45dLrMuxRI09tkGH9mlQ3IUc61/gpbnB0RJwnxmQWbS4j6gvmmPY8tRPvR1Odef86qxHPo Y2gWSDfGpYWUKuROJxsKKyfRiWyTLIzRljXJ6TPGr98w+Sxet454V+8OlCjx4IGVFNNG37WBB V1Wa2Wvrp64R8uqX/rbTYgyPcZT4r9J7aehFwMOdRWs2i44hRXQ01Qpaxsxdrd9kptCwoRq0d 8r10t+UHjq1Lj1jXxbzJsEFa+Gh9QmOu7ZXe0urUK9zDUYQv60p6SylZPXRKXqafq/OnpXAgA G1yxeHJWUWiCEForBzF7o/3tM60/atObbEz5GoTmudLVBFPQrnYo0poVCuRCy2RjRj4ONzfL5 yKNlcBVMVOhYZXm8jAxjyhh8BJp4f4/sCZFmkrP78hmAko2AsbU8Pc5ZYvljl3iSGRV5gUh0E voOI31QORx8QRs1VezPmZy/hwv5xXAy79Mf7DWK/a1J3qgEUnQ= X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 01:33:33 -0000 On 10/12/18 10:47 PM, Yuri Pankov wrote: > You *could* try temporarily applying the patch from > https://github.com/openzfs/openzfs/pull/690 (you'll need to fix the > paths, of course) and check if it would turn out to be a username you > deleted after all :-) > Oh I see... Thanks for the pointer. Unfortunately I cannot try your patch because the system has no source and I'd like to keep this way, that is updating via the "freebsd-update" route. Knowing that there is this bug though, helped a lot because I fixed it using the quick solution of adding users until a username appeared. It was just UID 1004 so I didn't have to search a lot... Thanks a lot! Nikos From owner-freebsd-fs@freebsd.org Sat Oct 13 12:43:06 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A53EE10C9371 for ; Sat, 13 Oct 2018 12:43:06 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 30A38797D3 for ; Sat, 13 Oct 2018 12:43:06 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id E7CA221B6B; Sat, 13 Oct 2018 08:43:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 13 Oct 2018 08:43:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm3; bh=fd7mcyZzp8gBtaXkwHkPPoFZH2p b/bD2CdDnZp0dzB4=; b=w0JpjuYz6oNEzuVSIv7i9R3Wwv3QzSpCc/4OsIa0eWF D6osC4QeV2RkibRcISOg6YPOz2wxc+mNqwELWNjKAqfhlXSO6BU43E2IiuMsuuLv TBqARb2ck+99i0KwFxaljgIjrkke6EfZJ4IA1lx+94A2Mw9R+MNfUAv92S3cg1a2 qysDgGEHJ6t6Od4Ms/tahpm4v+6LJT/4m6umqc7I0SJa9z+T2sawVAKrvVkr2sm5 iQcvPf9dnyWbLVRAZ1CM04RcBYkZMgE9A/ehe/qypG+2WqEjHhNEDjefdVocun/y zTdHCgEcddNOBGJD88mYE9bqQ0v26POcZSZwP6SpV5A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=fd7mcy Zzp8gBtaXkwHkPPoFZH2pb/bD2CdDnZp0dzB4=; b=ugGtKEINpS1cKeT1VjmtqQ 8D5kBO/jmqlkHjXD8vGgbWF7p6w1/ahmT9VJkYr1Q9EjqoYoSz3onJUh2+xvei0J IilWwPeO9GKihKJnpvQPHG4jg0OaWR3Q3ogGfxczoMHEUIshAq/SLSddk/X2xq4k 91MtmDJy+k1N09YZJ9R6EibgqP9+nx+jPToOVp4QuRRhp/h+0V9dVC5et3lSa+90 UcNh8BrcZcFVG1MT/iPUkegz3fwEsRvgRTaYNTqQFIUvhTS2vnbTvf0lGrUQWyXt Iq3Ts94UZYB8OoN6h/01hifsJKaYEgU9GqBFWBXqQ1xOpqIzWtvil+i4Ysld1l5Q == X-ME-Sender: X-ME-Proxy: Received: from [192.168.1.2] (unknown [94.233.225.150]) by mail.messagingengine.com (Postfix) with ESMTPA id 06EBD102A0; Sat, 13 Oct 2018 08:43:03 -0400 (EDT) Subject: Re: zfs allow reports empty username To: Nikos Vassiliadis , FreeBSD Filesystems References: <90dcc7f1-69fe-ea2c-5c50-e3025572492a@gmx.com> From: Yuri Pankov Openpgp: preference=signencrypt Autocrypt: addr=yuripv@yuripv.net; keydata= xsBNBFu8u6IBCADB11gP0QwnorrHjqAtKLHKHNHskhy0s7jqJKfx0YqXgVBKGLJ9/mjLAz0F CBNvemHSDDTs0mEZ9cBKKi6cmsav6+UQgr//yai6hvXLBJqKchSFO4MhmdvBtsGFq1yKz5Zi uhjmimKyIpgBgvMdbgGbGq6cnSB2uEPmZuJr419SVRODOkXukU+F5WHgaHzDdHAIu1asCt2B +6msxqIqlFWcXyZyTGicTGGvC/PFIsVRUtD1dIJANTC876g7DTb7LZXWiWwJpSJ4GKMXMHVX Ct9BoQ4i3nhKbOxb6Io1wsy+NFyWsTJ9KYrxKKPJP3oG8BWb/cqlFqnE4eNSsiq2q7krABEB AAHNH1l1cmkgUGFua292IDx5dXJpcHZAeXVyaXB2Lm5ldD7CwJcEEwEIAEECGwMFCQWjmoAF CwkIBwMFFQoJCAsFFgMCAQACHgECF4AWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW708wAIZ AQAKCRCTi+B/sSrhbPxBB/961alcU091O+yKT5/oReHVc/PX0Tz4sW3V44AcgLfYlrZavCro EFz90qmCrl0xqEwuAKcC4bjmL8SjPWAhSN6IH9nxdw+HeZnAPiHm/q679Bu47+nHBl3qD/9p +t1PkKeKZfaWToFMt1nq06ytSu6VLMCwLdlDNe6DReX0ex/afEqKsuaIZSKL4UYjRwklp8PU Uf98QkrfapyHB67hQMzfI4tPeJaYyv0cTgfq3kUWJx1V6Xi0b6Zxj4ZrB2TXvaMO5g7yhU9E E3WWAvoe4FgB3a7dHe8atnHhq5+Cuvm6+LD4Jh7jvMAE5UMN+xxQpnGpNghHjaCy4vXrLRBZ nhRYzsBNBFu8u6IBCADKih3Q933rDNj4ZA8FhBQ2RlmBgvwOLcDPIL3h0V7h38y3+HisgFSc XACDsdrTlYZ1bRXkD9FHENynBcv0l/3uGJDk8jaGIDE0TP8OQBRp+IaU9/BHnAqrKxTJGIol Dahy2m+yx2yhdc6B4ujWMDqCF1rWOD+ymOWw+VLllOkrHcZa5PJtX9UOGbApZl8ZTM8El4CA NN8F1bg9MWzUi+8LYoGWGc+BwsFS1OUB1c4SPgMu5fD4Wfsr9yRl06fdpEA2YT7B/j5/5RSC 0sE2Zs/tmJ/JRflHJ12ycj59ma2xQMfEJF40hZDpMFQmZvbVqgEg3ocQcltjbxlIKZ/mjC4z ABEBAAHCwHwEGAEKACYWIQT4arc+w94tPi0v/3CTi+B/sSrhbAUCW7y7ogIbDAUJBaOagAAK CRCTi+B/sSrhbIDcCACqAZMcoxUBLZa40a5b24j5i1jplvCYYb3h+Q5lt5+BFJ87kCb4dJuU D3kh2i29BrxWQWa9WNue9ozxeYkbkfXubQYXexVolRsnh64OdGsE8KvorBFBB3zdK/GRt2Jy +jsnTfUWuQllbzMP0MfhCDMk1Mo8WvDH2/cOEP/yLKf20a+cd6nLs7bidjmGXo9pyuBKAtV6 Kv+VRu54AL+A/UBYu/eB3Dtvzcnut+1Zq6KaP++kUwPwINLIk04OBDwN0zRNTiqMAFYYyz2v ZHBB6E1th/l//ZC5b9Dk0ZpFI1bYdL9ymnrZe1MqbGPnDCToQxu00T/pZCm6Z92YrZQYuNwl Message-ID: Date: Sat, 13 Oct 2018 15:42:36 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <90dcc7f1-69fe-ea2c-5c50-e3025572492a@gmx.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ijkjoXjp6EJdyBwS6xnQq7Joca57RTCSG" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 12:43:06 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ijkjoXjp6EJdyBwS6xnQq7Joca57RTCSG Content-Type: multipart/mixed; boundary="wH5QTna0P5cX2lDFOLQIOVhiJVnJds7Ms"; protected-headers="v1" From: Yuri Pankov To: Nikos Vassiliadis , FreeBSD Filesystems Message-ID: Subject: Re: zfs allow reports empty username References: <90dcc7f1-69fe-ea2c-5c50-e3025572492a@gmx.com> In-Reply-To: <90dcc7f1-69fe-ea2c-5c50-e3025572492a@gmx.com> --wH5QTna0P5cX2lDFOLQIOVhiJVnJds7Ms Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Nikos Vassiliadis wrote: > On 10/12/18 10:47 PM, Yuri Pankov wrote: >> You *could* try temporarily applying the patch from >> https://github.com/openzfs/openzfs/pull/690 (you'll need to fix the >> paths, of course) and check if it would turn out to be a username you >> deleted after all :-) >> >=20 > Oh I see... Thanks for the pointer. Unfortunately I cannot try your > patch because the system has no source and I'd like to keep this way, > that is updating via the "freebsd-update" route. >=20 > Knowing that there is this bug though, helped a lot because I fixed it > using the quick solution of adding users until a username appeared. It > was just UID 1004 so I didn't have to search a lot... Good to know. BTW, it's tracked as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200663 in our bugzill= a. --wH5QTna0P5cX2lDFOLQIOVhiJVnJds7Ms-- --ijkjoXjp6EJdyBwS6xnQq7Joca57RTCSG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlvB6DwACgkQk4vgf7Eq 4WyStAgAsM+ez7Dt0j+mYKrmWkBlv9ngypCDmBF6gchPSScGcUk53FPEGH1pdSbU 2++4ZEFKZdF1COSkqLxIFAphkwqhhVx+z3aF6Z1tkX+WGt0p2xk/vtFlUG2NgGt7 /y7WH69RWb4oRETbC9qIY25oMTtKoL6M3BFTMh4zPJxwvIZznrlL+K+C41Qp67z2 f9oPWj5+m/74EZ0PJ87yn4hwdUVSXCFZdAXAxypB+sok7gEEhh4Ajx2ICmPbN0od BEEeH6K2h0KNEi3QV3TcTH5YrgmiK4lhXP6ATzafaeBQnI6PetOpmsPkaBEPEqcx gsniKowB+JLJpaiQRZYaGVJEPaWVYQ== =WQsC -----END PGP SIGNATURE----- --ijkjoXjp6EJdyBwS6xnQq7Joca57RTCSG-- From owner-freebsd-fs@freebsd.org Sat Oct 13 16:55:44 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92E0A10CFE13 for ; Sat, 13 Oct 2018 16:55:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2EB7C821DD for ; Sat, 13 Oct 2018 16:55:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E4EBD10CFE12; Sat, 13 Oct 2018 16:55:43 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3AE910CFE11 for ; Sat, 13 Oct 2018 16:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A7FB821D8 for ; Sat, 13 Oct 2018 16:55:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id AFA4A27E24 for ; Sat, 13 Oct 2018 16:55:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9DGtgSN061146 for ; Sat, 13 Oct 2018 16:55:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9DGtgNs061145 for fs@FreeBSD.org; Sat, 13 Oct 2018 16:55: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 228750] panic on zfs mirror removal Date: Sat, 13 Oct 2018 16:55:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cheeky.m@live.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 16:55:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 --- Comment #9 from Roger Hammerstein --- I moved the 11.2 test machine to 12, but I can make a new 11.2 test later. The panic in Comment 4 is still occurring in the latest 12 at r339345. Can you take a look at that ?=20 FreeBSD 12.0-ALPHA9 (GENERIC) #3 r339345M --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Sat Oct 13 17:19:16 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 003E510D049D for ; Sat, 13 Oct 2018 17:19:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8E6FA82BD8 for ; Sat, 13 Oct 2018 17:19:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4DFCE10D049C; Sat, 13 Oct 2018 17:19:15 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C43F10D049B for ; Sat, 13 Oct 2018 17:19:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3FD882BC4 for ; Sat, 13 Oct 2018 17:19:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1D52D121 for ; Sat, 13 Oct 2018 17:19:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9DHJDX2030503 for ; Sat, 13 Oct 2018 17:19:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9DHJDCd030502 for fs@FreeBSD.org; Sat, 13 Oct 2018 17:19: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 228750] panic on zfs mirror removal Date: Sat, 13 Oct 2018 17:19:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: allanjude@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 17:19:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 --- Comment #10 from Allan Jude --- (In reply to Roger Hammerstein from comment #9) There is a 2nd patch you'll need as well. See here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229007#c12 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Sat Oct 13 18:09:20 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CEEE10D179C for ; Sat, 13 Oct 2018 18:09:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4EB6B847EC for ; Sat, 13 Oct 2018 18:09:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 11F3C10D1797; Sat, 13 Oct 2018 18:09:19 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E391D10D1796 for ; Sat, 13 Oct 2018 18:09:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 809E2847D5 for ; Sat, 13 Oct 2018 18:09:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C3AF5836 for ; Sat, 13 Oct 2018 18:09:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9DI9Hr5016104 for ; Sat, 13 Oct 2018 18:09:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9DI9HaA016099 for fs@FreeBSD.org; Sat, 13 Oct 2018 18:09: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 228750] panic on zfs mirror removal Date: Sat, 13 Oct 2018 18:09:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cheeky.m@live.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2018 18:09:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 --- Comment #11 from Roger Hammerstein --- (In reply to Allan Jude from comment #10) yes, that patch works.=20=20 root@freebsd12:~ # zpool remove test mirror-1 root@freebsd12:~ # root@freebsd12:~ # zpool status pool: test state: ONLINE scan: none requested remove: Evacuation of mirror-1 in progress since Sat Oct 13 10:03:42 2018 5.81M copied out of 5.81M at 850K/s, 100.00% done, 0h0m to go config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da9 ONLINE 0 0 0 da8 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 da7 ONLINE 0 0 0 da6 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 da5 ONLINE 0 0 0 da4 ONLINE 0 0 0 errors: No known data errors root@freebsd12:~ # root@freebsd12:~ # zpool status pool: test state: ONLINE scan: none requested remove: Removal of vdev 1 copied 5.81M in 0h0m, completed on Sat Oct 13 10:03:51 2018 384 memory used for removed device mappings config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da9 ONLINE 0 0 0 da8 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 da5 ONLINE 0 0 0 da4 ONLINE 0 0 0 errors: No known data errors root@freebsd12:~ # and for extra: root@freebsd12:~ # zpool remove test mirror-2 root@freebsd12:~ # zpool status pool: test state: ONLINE scan: none requested remove: Evacuation of mirror-2 in progress since Sat Oct 13 10:05:49 2018 7.15M copied out of 7.15M at 1.79M/s, 100.00% done, 0h0m to go 384 memory used for removed device mappings config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da9 ONLINE 0 0 0 da8 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 da5 ONLINE 0 0 0 da4 ONLINE 0 0 0 errors: No known data errors root@freebsd12:~ # root@freebsd12:~ # zpool status pool: test state: ONLINE scan: none requested remove: Removal of vdev 2 copied 7.15M in 0h0m, completed on Sat Oct 13 10:05:54 2018 912 memory used for removed device mappings config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da9 ONLINE 0 0 0 da8 ONLINE 0 0 0 errors: No known data errors root@freebsd12:~ # root@freebsd12:~ # zpool clear test root@freebsd12:~ # zpool status test pool: test state: ONLINE scan: none requested remove: Removal of vdev 2 copied 7.15M in 0h0m, completed on Sat Oct 13 10:05:54 2018 912 memory used for removed device mappings config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da9 ONLINE 0 0 0 da8 ONLINE 0 0 0 errors: No known data errors root@freebsd12:~ # root@freebsd12:~ # zpool export test root@freebsd12:~ # zpool import test zpool status test root@freebsd12:~ # zpool status test pool: test state: ONLINE scan: none requested remove: Removal of vdev 2 copied 7.15M in 0h0m, completed on Sat Oct 13 10:05:54 2018 912 memory used for removed device mappings config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da9 ONLINE 0 0 0 da8 ONLINE 0 0 0 errors: No known data errors root@freebsd12:~ # FreeBSD freebsd12 12.0-ALPHA9 FreeBSD 12.0-ALPHA9 #3 r339345M --=20 You are receiving this mail because: You are on the CC list for the bug.=