From owner-freebsd-fs@freebsd.org Sun Apr 3 19:23:29 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9372CB01B98 for ; Sun, 3 Apr 2016 19:23: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 mx1.freebsd.org (Postfix) with ESMTPS id 848C1182F for ; Sun, 3 Apr 2016 19:23:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u33JNTbX073183 for ; Sun, 3 Apr 2016 19:23:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 205154] newfs_msdos issue Date: Sun, 03 Apr 2016 19:23:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Documentation X-Bugzilla-Component: Documentation X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bcr@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2016 19:23:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205154 Benedict Reuschling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bcr@FreeBSD.org Assignee|freebsd-doc@FreeBSD.org |freebsd-fs@FreeBSD.org --- Comment #1 from Benedict Reuschling --- Over to filesystem folks, maybe you can help with this. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 3 20:18:20 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6541BB01CD4 for ; Sun, 3 Apr 2016 20:18: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 mx1.freebsd.org (Postfix) with ESMTPS id 5678611E1 for ; Sun, 3 Apr 2016 20:18:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u33KIJC1012507 for ; Sun, 3 Apr 2016 20:18:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 205154] newfs_msdos issue Date: Sun, 03 Apr 2016 20:18:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Documentation X-Bugzilla-Component: Documentation X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: Ultima1252@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2016 20:18:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205154 Ultima changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Ultima1252@gmail.com --- Comment #2 from Ultima --- (In reply to RueiChang from comment #0) Can you explain a bit more in depth what "damaged storage" is please? Is it not mountable? data corrupted? Details will help greatly. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 3 21:00:52 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4434BB00B97 for ; Sun, 3 Apr 2016 21:00: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 mx1.freebsd.org (Postfix) with ESMTPS id 234421701 for ; Sun, 3 Apr 2016 21:00:52 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u33L01wP097496 for ; Sun, 3 Apr 2016 21:00:52 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201604032100.u33L01wP097496@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 03 Apr 2016 21:00:52 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2016 21:00:52 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f 4 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Apr 4 07:55:07 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB67BB01731 for ; Mon, 4 Apr 2016 07:55:07 +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 mx1.freebsd.org (Postfix) with ESMTPS id BC6FD15E0 for ; Mon, 4 Apr 2016 07:55:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u347t7bS039420 for ; Mon, 4 Apr 2016 07:55:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207533] LOR in UFS on FreeBSD 10.3-BETA3 @ sys_openat Date: Mon, 04 Apr 2016 07:55: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: 10.3-BETA2 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: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 07:55:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207533 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 07:55:40 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0C03B0185E for ; Mon, 4 Apr 2016 07: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 mx1.freebsd.org (Postfix) with ESMTPS id E1A9716C2 for ; Mon, 4 Apr 2016 07:55:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u347teN0040146 for ; Mon, 4 Apr 2016 07:55:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207534] LOR in UFS on FreeBSD 10.3-BETA3 @ sys_rmdir Date: Mon, 04 Apr 2016 07: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: 10.3-BETA2 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: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 07:55:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207534 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 07:55:54 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0D2AB018F3 for ; Mon, 4 Apr 2016 07:55: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 mx1.freebsd.org (Postfix) with ESMTPS id B1C1317C0 for ; Mon, 4 Apr 2016 07:55:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u347tslZ040591 for ; Mon, 4 Apr 2016 07:55:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207535] LOR in UFS on FreeBSD 10.3-BETA3 @ sys_fsync Date: Mon, 04 Apr 2016 07:55: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: 10.3-BETA2 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: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 07:55:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207535 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 07:58:40 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77D41B01B61 for ; Mon, 4 Apr 2016 07:58: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 mx1.freebsd.org (Postfix) with ESMTPS id 68C4F1A4B for ; Mon, 4 Apr 2016 07:58:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u347wdT2044637 for ; Mon, 4 Apr 2016 07:58:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207619] ZFS range_tree_remove() assert causes kernel panic Date: Mon, 04 Apr 2016 07:58: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: 10.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: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 07:58:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207619 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 08:00:59 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1B4CB01F98 for ; Mon, 4 Apr 2016 08:00: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 mx1.freebsd.org (Postfix) with ESMTPS id 92AF81C63 for ; Mon, 4 Apr 2016 08:00:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3480w1S062511 for ; Mon, 4 Apr 2016 08:00:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Mon, 04 Apr 2016 08:00:59 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 08:00:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 08:05:13 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24A88B02485 for ; Mon, 4 Apr 2016 08:05:13 +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 mx1.freebsd.org (Postfix) with ESMTPS id 15537146A for ; Mon, 4 Apr 2016 08:05:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3485CVP094722 for ; Mon, 4 Apr 2016 08:05:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207838] [zfs] getcwd fails with permission denied under load Date: Mon, 04 Apr 2016 08:05:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 08:05:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207838 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 08:07:02 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF478B02687 for ; Mon, 4 Apr 2016 08:07:02 +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 mx1.freebsd.org (Postfix) with ESMTPS id AFA5017C6 for ; Mon, 4 Apr 2016 08:07:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u34872HJ097074 for ; Mon, 4 Apr 2016 08:07:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207902] zfs boot into Safe Mode & Single User leads to auto mount failure. Date: Mon, 04 Apr 2016 08:07:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 08:07:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207902 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 11:41:45 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8652BB0387A for ; Mon, 4 Apr 2016 11:41:45 +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 mx1.freebsd.org (Postfix) with ESMTPS id 774CD186D for ; Mon, 4 Apr 2016 11:41:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u34Bfi8v095987 for ; Mon, 4 Apr 2016 11:41:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Mon, 04 Apr 2016 11:41:45 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 11:41:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #1 from Andriy Gapon --- If you are not able to get a crash dump, then, at least, please get a screenshot of the panic screen. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 4 11:45:08 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05AAFB0394B for ; Mon, 4 Apr 2016 11:45: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 mx1.freebsd.org (Postfix) with ESMTPS id E5DD11ADA for ; Mon, 4 Apr 2016 11:45:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u34Bj7Mr004058 for ; Mon, 4 Apr 2016 11:45:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207902] zfs boot into Safe Mode & Single User leads to auto mount failure. Date: Mon, 04 Apr 2016 11:45:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 11:45:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207902 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Not A Bug --- Comment #1 from Andriy Gapon --- In the single user mode only the root filesystem is mounted read-only _by design_. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Apr 5 00:44:24 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE4E6B01897 for ; Tue, 5 Apr 2016 00:44:24 +0000 (UTC) (envelope-from wiml@omnigroup.com) Received: from omnigroup.com (omnigroup.com [198.151.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "omnigroup.com", Issuer "The Omni Group CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CD50C115B for ; Tue, 5 Apr 2016 00:44:24 +0000 (UTC) (envelope-from wiml@omnigroup.com) Received: from machamp.omnigroup.com (machamp.omnigroup.com [198.151.161.135]) by omnigroup.com (Postfix) with ESMTP id A186F316BA0F for ; Mon, 4 Apr 2016 17:38:30 -0700 (PDT) Received: from [10.4.3.73] (pfsense.omnigroup.com [198.151.161.131]) by machamp.omnigroup.com (Postfix) with ESMTPSA id 0A3A41B8ED44 for ; Mon, 4 Apr 2016 17:38:27 -0700 (PDT) From: Wim Lewis Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: ZFS pool with a large number of filesystems Message-Id: <34DB45E8-7E1F-4D7C-96FF-E0A403EE8000@omnigroup.com> Date: Mon, 4 Apr 2016 17:38:30 -0700 To: "freebsd-fs@FreeBSD.org" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 00:44:25 -0000 I'm curious how many ZFS filesystems are reasonable to have on a single = machine (in a single zpool). We're contemplating a design in which we'd = have tens of thousands, perhaps a couple hundred thousand, filesystems = mounted out of the same pool. Before we go too far into investigating = this idea: Does anyone have real-world experience doing something like = that? Is it a situation that ZFS-on-FreeBSD is engineered to handle with = good performance? Is there a rough estimate of the resources consumed = per additional filesystem (in terms of kernel VM and disk space)? Thanks for any insight or advice (even, or especially, if the answer is = "that's crazy, don't do that" :) ) Wim Lewis / wiml@omnigroup.com From owner-freebsd-fs@freebsd.org Tue Apr 5 01:15:53 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27B79B023D7 for ; Tue, 5 Apr 2016 01:15:53 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 E24CC11FF for ; Tue, 5 Apr 2016 01:15:52 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 055562845A; Tue, 5 Apr 2016 03:15:51 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 21B6628417; Tue, 5 Apr 2016 03:15:50 +0200 (CEST) Message-ID: <570311C5.4010702@quip.cz> Date: Tue, 05 Apr 2016 03:15:49 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Wim Lewis , "freebsd-fs@FreeBSD.org" Subject: Re: ZFS pool with a large number of filesystems References: <34DB45E8-7E1F-4D7C-96FF-E0A403EE8000@omnigroup.com> In-Reply-To: <34DB45E8-7E1F-4D7C-96FF-E0A403EE8000@omnigroup.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 01:15:53 -0000 Wim Lewis wrote on 04/05/2016 02:38: > I'm curious how many ZFS filesystems are reasonable to have on a single machine (in a single zpool). We're contemplating a design in which we'd have tens of thousands, perhaps a couple hundred thousand, filesystems mounted out of the same pool. Before we go too far into investigating this idea: Does anyone have real-world experience doing something like that? Is it a situation that ZFS-on-FreeBSD is engineered to handle with good performance? Is there a rough estimate of the resources consumed per additional filesystem (in terms of kernel VM and disk space)? > > Thanks for any insight or advice (even, or especially, if the answer is "that's crazy, don't do that" :) ) I donn't know about how many filesystems but I know that few hundereds of snapshots can make a noticeable slowdown for some zfs operations. I think that basic "zfs list" will be painfully slow with tens of thousands of filesystems. Miroslav Lachman From owner-freebsd-fs@freebsd.org Tue Apr 5 01:38:20 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 366DDB02B93 for ; Tue, 5 Apr 2016 01:38:20 +0000 (UTC) (envelope-from tenzin.lhakhang@gmail.com) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E52CF1E49 for ; Tue, 5 Apr 2016 01:38:19 +0000 (UTC) (envelope-from tenzin.lhakhang@gmail.com) Received: by mail-qg0-x235.google.com with SMTP id f52so71672974qga.3 for ; Mon, 04 Apr 2016 18:38:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hgqViGXIi3okeFOFOLbpQvklDvMbplzPGz2iMlefKNY=; b=Bk15eukcdCn1xt/PJKhBbcTgtVD1MuzIvcymAWvzoEJe/Blom657ZAPevgOh+06ghQ icu9LXjLpGqkOukMbdIf+ngVZUU7fUDu1iVpJnMklDMA6h1kQ1HBvN6R5dK+Nult1c6c aKCVl4H60KfID7TZQLjMtG1Fvz3wZejBuZbzL4RW6HhHJZsCdGGpX9eMMQ1IL1ccqKkL KjY7f4VjyPZWFmdjI/40parzQo47UIzlV9w/DZyFvs06+2PeqG7R1IC8TxZluIX+HK3V lgQta/N6S2t6F0S/scNdnyE+y9Bcu/yQWpNo2VqPHm6qQkRiYFU+y4U/hVha5foPX8V2 3JLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hgqViGXIi3okeFOFOLbpQvklDvMbplzPGz2iMlefKNY=; b=mZgAz6DDJ0Gq31aBS+vYG5/xWVzsRo/m99YSjn57pqTIiX8wcBOL3PufkglCTK9zPb qaBNChyw1+avI5O327IxUIj4HuzP+3Cp2yTaVi+D8ul7IgfCypuVGf5KJoWoIfXp/2xe dRkssgPLVr3XYXfijZQ3vWSDOQz91G14Z+DtGnpGCrFLtQaBF6/QkzrA94wEBieK1376 2hFl0XVDadopp6DnVCLhuFGP818gv9ITPPL0sgzLxzZ9GTuPlR3fNIlRrsXS144Ci78Q xxcXrOgcx3R1Kava6nnt/0j3K4Edn3KTxlAVsM+ZGTfQeDEFGGFuE2DdQEoCX8FjBd/+ VnIg== X-Gm-Message-State: AD7BkJJK8Nf3LCfP/Uah7rmccpKEPlevwSSg7+PoCOHKNnVupFEqbxeETyZFz2en7ORyCA== X-Received: by 10.140.228.68 with SMTP id y65mr27114129qhb.78.1459820299092; Mon, 04 Apr 2016 18:38:19 -0700 (PDT) Received: from [192.168.100.34] (c-73-167-145-126.hsd1.ma.comcast.net. [73.167.145.126]) by smtp.gmail.com with ESMTPSA id y89sm8451651qgd.5.2016.04.04.18.38.17 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2016 18:38:18 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: ZFS pool with a large number of filesystems From: "Tenzin W. Lhakhang" X-Mailer: iPhone Mail (13E238) In-Reply-To: <570311C5.4010702@quip.cz> Date: Mon, 4 Apr 2016 21:38:16 -0400 Cc: Wim Lewis , "freebsd-fs@FreeBSD.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <34DB45E8-7E1F-4D7C-96FF-E0A403EE8000@omnigroup.com> <570311C5.4010702@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 01:38:20 -0000 The most I have seen is approximately 10,000. The performance isn't too bad at that scale. The clone fs metadata becomes a= bit costly. I seen pretty deep nesting into the zfs dataset chains on cert= ain server types; dataset clone snap clone snap chains going about 30 levels= . Note: we are running zfs on illumos (Smartos) General system specs are: e5-26[89]0v2,256gb ram, 1-2 ZIL and ssd or spinni= ng with 4-6 ssd cache drives. Tenzin Sent from my iPhone > On Apr 4, 2016, at 9:15 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >=20 > Wim Lewis wrote on 04/05/2016 02:38: >> I'm curious how many ZFS filesystems are reasonable to have on a single m= achine (in a single zpool). We're contemplating a design in which we'd have t= ens of thousands, perhaps a couple hundred thousand, filesystems mounted out= of the same pool. Before we go too far into investigating this idea: Does a= nyone have real-world experience doing something like that? Is it a situatio= n that ZFS-on-FreeBSD is engineered to handle with good performance? Is ther= e a rough estimate of the resources consumed per additional filesystem (in t= erms of kernel VM and disk space)? >>=20 >> Thanks for any insight or advice (even, or especially, if the answer is "= that's crazy, don't do that" :) ) >=20 > I donn't know about how many filesystems but I know that few hundereds of s= napshots can make a noticeable slowdown for some zfs operations. > I think that basic "zfs list" will be painfully slow with tens of thousand= s of filesystems. >=20 > Miroslav Lachman > _______________________________________________ > 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 Tue Apr 5 02:26:23 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CAF3B03B81 for ; Tue, 5 Apr 2016 02:26:23 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA9A511D6 for ; Tue, 5 Apr 2016 02:26:22 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-io0-x236.google.com with SMTP id q128so3157788iof.3 for ; Mon, 04 Apr 2016 19:26:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=r2x2hE9odDMdTwGT/LxUxBVNKYeHEZZ5vw3q8i+sFf8=; b=veh6v2kU51XD+IXqOJ8Akn/gm/Lv99wmPCecfVM/OVcgZcOcsL+6nsczvzrTzqdzgt ahhtNrFzJP1V78quVHiCAnI6y+qIMq2ip+rTUrPVNO46GehqIFz49dnpoDE86hb2Y2nX xacvf4Vk4k+7wUcQh/2GugdeSdwU8rAee5Dpek3vWVVOINuGs5WN6SBd9aM326TlZs3P SI2gpJ795fra2/fgBU7CfAx7ag/EAS0w78D/wYgmjM9WWPghJ1BRFL5GH6Ymo9Kg74Qp VB3THnNxTsGZxn+QpF9ANzE90AelREP/9iaeLEMDU4pP0Jv9/FiEb3/D2e+xHEk7rhQH hp8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=r2x2hE9odDMdTwGT/LxUxBVNKYeHEZZ5vw3q8i+sFf8=; b=iJUSn4nWKjKcB+g/xIFpvetcBM/KgFEAz9uO5cAPkj0XSrXLcIn6689WL3/wNIi1AE 6QN8CLN9fA6dU/YOyHjRRxYbZiaLaaM9D5rnHUQPaKcjwNwu483lRdoodRnSA0ZbC6NL k3DxPC0RjcC4oEVXymYRGDfdbC3jNFBLK6wdpFRNGcukscR6QkCq+teVc52YrFzU1Ant Shy2HWS+H9pVmPxZqoR5CfNOAHq7gNxf8TJjdA7EH62XG3w5wVe90i84ARm0wJ+DxmJi Tsv1mxugYT/nfY74QMLkiuOtdUfBnGP0BuE3DWbG1d9WSutbOiC/7ShsRy7nelZbK9ik 2qkQ== X-Gm-Message-State: AD7BkJJoc4V6vrskoctYUbAOjM8blghY9mD9gfd3669Ya9z3S6xZVQqB1Tj78ChvxF3VwcLD+LvX11vWijFEmQ== MIME-Version: 1.0 X-Received: by 10.107.133.233 with SMTP id p102mr18977517ioi.1.1459823182345; Mon, 04 Apr 2016 19:26:22 -0700 (PDT) Received: by 10.107.161.6 with HTTP; Mon, 4 Apr 2016 19:26:22 -0700 (PDT) Received: by 10.107.161.6 with HTTP; Mon, 4 Apr 2016 19:26:22 -0700 (PDT) In-Reply-To: References: <34DB45E8-7E1F-4D7C-96FF-E0A403EE8000@omnigroup.com> <570311C5.4010702@quip.cz> Date: Mon, 4 Apr 2016 19:26:22 -0700 Message-ID: Subject: Re: ZFS pool with a large number of filesystems From: Freddie Cash To: Miroslav Lachman <000.fbsd@quip.cz> Cc: FreeBSD Filesystems , Wim Lewis Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 02:26:23 -0000 On Apr 4, 2016 6:16 PM, "Miroslav Lachman" <000.fbsd@quip.cz> wrote: > > Wim Lewis wrote on 04/05/2016 02:38: >> >> I'm curious how many ZFS filesystems are reasonable to have on a single machine (in a single zpool). We're contemplating a design in which we'd have tens of thousands, perhaps a couple hundred thousand, filesystems mounted out of the same pool. Before we go too far into investigating this idea: Does anyone have real-world experience doing something like that? Is it a situation that ZFS-on-FreeBSD is engineered to handle with good performance? Is there a rough estimate of the resources consumed per additional filesystem (in terms of kernel VM and disk space)? >> >> Thanks for any insight or advice (even, or especially, if the answer is "that's crazy, don't do that" :) ) > > > I donn't know about how many filesystems but I know that few hundereds of snapshots can make a noticeable slowdown for some zfs operations. > I think that basic "zfs list" will be painfully slow with tens of thousands of filesystems. > > Miroslav Lachman Adding "-o ,,etc" to limit what you query via "zfs list" really makes a difference. Especially on FreeBSD. PHK did a lot of work optimising that a release or two ago. "zfs list -o name -r -t all pool/fs" is many many many times faster than "zfs list -r -t all pool/fs" Cheers, Freddie Typos courtesy of my phone. From owner-freebsd-fs@freebsd.org Tue Apr 5 21:00:53 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8FD6B04533 for ; Tue, 5 Apr 2016 21:00: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 mx1.freebsd.org (Postfix) with ESMTPS id B0C3B1D16 for ; Tue, 5 Apr 2016 21:00:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u35L0rbp049630 for ; Tue, 5 Apr 2016 21:00:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Tue, 05 Apr 2016 21:00:53 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: michelle@sorbs.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 21:00:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #2 from Michelle Sullivan --- I hate to be beligerent, but exactly how would one do that... take a phone = into the DC and take a photo of the console? What would be nice would be to know how to get it to dump core... I see no reason why it shouldn't...=20=20 in /etc/rc.conf: # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev=3D"AUTO" Then in /etc/rc.conf.local: dumpdev=3D"AUTO" dumpdir=3D"/var/crash" crashinfo_enable=3D"YES" And just to make sure... # ls -l /var/crash/ total 4 -rw-r--r-- 1 root wheel 5 Sep 27 2013 minfree [root@colossus ~]# more /var/crash/minfree=20 2048 [root@colossus ~]# df -h Filesystem Size Used Avail Capacity Mounted on /dev/mirror/roots1a 107G 50G 48G 51% / devfs 1.0k 1.0k 0B 100% /dev VirtualDisks 69G 31k 69G 0% /VirtualDisks sorbs 33T 29T 3.8T 89% /sorbs [root@colossus ~]# more /etc/fstab=20 # Device Mountpoint FStype Options Dump Pas= s# /dev/mirror/roots1a / ufs rw 1 1 /dev/da0s1 none swap sw 1 0 Even did this: [root@colossus ~]# dumpon -v /dev/da0s1=20 kernel dumps on /dev/da0s1=20 (da0s1 =3D 28G(ish) USB drive - 16G RAM in the machine) ... Oh well photograph the console seems to be the answer ... if it helps: http://flashback.sorbs.net/packages/zpool-scrub-panic-console.jpg --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue Apr 5 21:43:18 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B954B0434E for ; Tue, 5 Apr 2016 21:43: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 mx1.freebsd.org (Postfix) with ESMTPS id 0C5C6138D for ; Tue, 5 Apr 2016 21:43:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u35LhHEf003353 for ; Tue, 5 Apr 2016 21:43:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Tue, 05 Apr 2016 21:43:18 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: girgen@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 21:43:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 Palle Girgensohn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |girgen@FreeBSD.org --- Comment #3 from Palle Girgensohn --- You need enough swap to fit the kernel's core dump, or it will be lost at reboot and never be moved to /var/crash by dumpon (this happens after reboo= t) Palle --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue Apr 5 22:08:22 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E6A5B04CF6 for ; Tue, 5 Apr 2016 22:08:22 +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 mx1.freebsd.org (Postfix) with ESMTPS id 164B314D2 for ; Tue, 5 Apr 2016 22:08:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u35M8Li2088181 for ; Tue, 5 Apr 2016 22:08:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Tue, 05 Apr 2016 22:08:22 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: michelle@sorbs.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 22:08:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #4 from Michelle Sullivan --- Understood... >From 'top': Mem: 91M Active, 233M Inact, 2060M Wired, 281M Buf, 13G Free ARC: 1536M Total, 307M MFU, 1209M MRU, 10M Anon, 5994K Header, 4495K Other Swap: 29G Total, 29G Free or if you prefer from dmesg: real memory =3D 17188257792 (16392 MB) avail memory =3D 16491753472 (15727 MB) da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 da0: Removable Direct Access SCSI-6 device= =20 da0: Serial Number 60A44C3FACC9FE118997019C da0: 40.000MB/s transfers da0: 29510MB (60437492 512 byte sectors: 255H 63S/T 3762C) da0: quirks=3D0x2 And just for completeness... [root@colossus ~]# fdisk /dev/da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=3D3762 heads=3D255 sectors/track=3D63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3D3762 heads=3D255 sectors/track=3D63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 60436467 (29509 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 689/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: [root@colossus ~]# bsdlabel /dev/da0s1=20 # /dev/da0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 60436451 16 swap=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20 c: 60436467 0 unused 0 0 # "raw" part, don't edit I'd suggest there is enough space... yet it doesn't produce dumps - infact = when it panics it shows the uptime then locks solid (won't respond to the 3 fing= er salute) ... reset button or power button for +3 seconds is the only way to = get a response... --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue Apr 5 22:21:22 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F150AB03268 for ; Tue, 5 Apr 2016 22:21:22 +0000 (UTC) (envelope-from nishida@asusa.net) Received: from asusam.asj-hosting.net (asusa.asj-hosting.net [219.118.222.245]) (using TLSv1.2 with cipher CAMELLIA256-SHA (256/256 bits)) (Client CN "*.asj-hosting.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DF4C1F2E for ; Tue, 5 Apr 2016 22:21:21 +0000 (UTC) (envelope-from nishida@asusa.net) Received: (qmail 50017 invoked by uid 89); 6 Apr 2016 07:21:13 +0900 X-ASJ-Track-ID: <20160405222113.50017.qmail@asusam.asj-hosting.net> X-Spam-Checker-Version: ASJ KMsrv Spam Check Process Internal X-Spam-Status: No, hits=0.0 X-Spam-Flag: No X-Virus-Scanned: ASJ KMsrv Virus Check Process 08041001 X-ASJ-SMTP-Authentication: nishida@asusa.net X-ASJ-Arrival-IP: 50.207.112.201 X-ASJ-SPF-Info: auth X-ASJ-Scan-ID: <1459894873.234244.50010@asusam.asj-hosting.net> X-ASJ-Received-SPF: pass (send with smtp authentication by nishida@asusa.net@50.207.112.201) Received: from gw.asusa.net (HELO rd03.asusa-internal.net) (nishida@asusa.net@50.207.112.201) by asusams.asj-hosting.net with ESMTPS (AES128-SHA encrypted); 6 Apr 2016 07:21:13 +0900 Subject: Re: Problem with FUSE + fts To: freebsd-fs@freebsd.org References: <56F42EF4.5000505@asusa.net> <1294209833.31699182.1458950014610.JavaMail.zimbra@uoguelph.ca> <56F6148D.2030706@asusa.net> <56FAD050.2080707@asusa.net> <765991039.37160180.1459291777879.JavaMail.zimbra@uoguelph.ca> <56FB07DC.4000504@asusa.net> <2009006928.37186618.1459292816761.JavaMail.zimbra@uoguelph.ca> <56FB0DD0.4000806@asusa.net> <294037501.39717127.1459381643954.JavaMail.zimbra@uoguelph.ca> <56FD4788.5030808@asusa.net> From: Hiroshi Nishida Message-ID: <57043A57.7030705@asusa.net> Date: Tue, 5 Apr 2016 15:21:11 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <56FD4788.5030808@asusa.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 22:21:23 -0000 Since there is no response even at fuse-devel ML, I would like to write down a solution here. * Symptom When using a command that calls fts_read() like "find" or "rm -r" for a FUSE based filesystem, it outputs "No such file or directory" for some files/directories that exist. * Solution In /usr/ports/sysutils/fusefs-libs/work/libfuse-fuse_X_X_X/lib/fuse.c, the following struct is declared: static struct fuse_lowlevel_ops fuse_path_ops = { .init = fuse_lib_init, .destroy = fuse_lib_destroy, .lookup = fuse_lib_lookup, .forget = fuse_lib_forget, .forget_multi = fuse_lib_forget_multi, .getattr = fuse_lib_getattr, Here, comment out .forget and .forget_multi lines like: static struct fuse_lowlevel_ops fuse_path_ops = { .init = fuse_lib_init, .destroy = fuse_lib_destroy, .lookup = fuse_lib_lookup, //.forget = fuse_lib_forget, //.forget_multi = fuse_lib_forget_multi, .getattr = fuse_lib_getattr, Alternatively, you can use "noforget" mount option, though I'm not sure if it can be used for high level APIs like fuse_main(). -- Hiroshi Nishida nishida@asusa.net From owner-freebsd-fs@freebsd.org Tue Apr 5 23:09:34 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7233B0412A for ; Tue, 5 Apr 2016 23:09:34 +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 mx1.freebsd.org (Postfix) with ESMTPS id B832B1242 for ; Tue, 5 Apr 2016 23:09:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u35N9Ytu051040 for ; Tue, 5 Apr 2016 23:09:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Tue, 05 Apr 2016 23:09:34 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: girgen@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 23:09:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #5 from Palle Girgensohn --- That sucks, then maybe you're out of luck getting a core dump. :-( --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 6 03:08:26 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB00DB0362D for ; Wed, 6 Apr 2016 03:08:26 +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 mx1.freebsd.org (Postfix) with ESMTPS id DBC5F1CBA for ; Wed, 6 Apr 2016 03:08:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3638Qes041560 for ; Wed, 6 Apr 2016 03:08:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Wed, 06 Apr 2016 03:08:26 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bjk@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 03:08:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 Benjamin Kaduk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjk@FreeBSD.org --- Comment #6 from Benjamin Kaduk --- I don't think coredump to swap-on-USB is expected to work. I am not famil= iar with the details, but am given to understand that the architecture of the U= SB support makes it basically not work in panic context. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 6 05:21:15 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F03C9B05841 for ; Wed, 6 Apr 2016 05:21:15 +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 mx1.freebsd.org (Postfix) with ESMTPS id E0E5F1DD8 for ; Wed, 6 Apr 2016 05:21:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u365LFHF077245 for ; Wed, 6 Apr 2016 05:21:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Wed, 06 Apr 2016 05:21:15 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: michelle@sorbs.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 05:21:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #7 from Michelle Sullivan --- That would make sense, but can't swap to zfs either (options there are file= - which won't work (documented) or zvol which is not documented but trying it just gave an inappropriate ioctl when trying to add the dump dev) possibly = the other thing I could do it take the hotspare device out of the pool and turn= it into a sump dev... but really trying not to screw with the existing config.= ... Did you take a look at the photo of the console? Does it seem interesting?= It is 100% reproducable and the panic is instant. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 6 12:43:25 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5ACEB03D6C for ; Wed, 6 Apr 2016 12:43: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 mx1.freebsd.org (Postfix) with ESMTPS id C8DAB1055 for ; Wed, 6 Apr 2016 12:43:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u36ChPlK021721 for ; Wed, 6 Apr 2016 12:43:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Wed, 06 Apr 2016 12:43:26 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bjk@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 12:43:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #8 from Benjamin Kaduk --- (In reply to Michelle Sullivan from comment #7) > That would make sense, but can't swap to zfs either (options there are fi= le - which won't work (documented) or zvol which is not documented but tryi= ng it just gave an inappropriate ioctl when trying to add the dump dev) pos= sibly the other thing I could do it take the hotspare device out of the poo= l and turn it into a sump dev... but really trying not to screw with the ex= isting config.... Of those, I would only expect taking the hotspare out of the pool and using= the raw device for swap to provide a usable crash dump, but am not at the point= of recommending that you do so. > Did you take a look at the photo of the console? Does it seem interestin= g? It is 100% reproducable and the panic is instant. I did look at it, and it seems interesting, but unfortunately outside my ar= ea of expertise. Hopefully Andriy will take a look. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 6 17:10:11 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B5BFB06A0F for ; Wed, 6 Apr 2016 17:10: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 mx1.freebsd.org (Postfix) with ESMTPS id 6C3AC1F44 for ; Wed, 6 Apr 2016 17:10:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u36HAAHg059509 for ; Wed, 6 Apr 2016 17:10:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Wed, 06 Apr 2016 17:10:10 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 17:10:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #9 from Andriy Gapon --- (In reply to Michelle Sullivan) Replying to multiple comments at once. Yes, taking a picture of a monitor is a fine last measure. A serial consol= e, real or emulated via, e.g., IPMI or AMT, is better, of course. The panic looks like a result of a well-known (among developers) and very h= ard to fix problem with interaction between GEOM and ZVOLs that arises from usi= ng ZFS pools on top of ZFS volumes. I can not offer you any fix although I ha= ve got some work-in-progress on this issue. I can suggest a work-around: create a FreeBSD VM using the volumes comprisi= ng the pool as the VM's disks and run the scrub within the VM. Besides zpool scrub commands like zpool reopen, zpool split, zpool online [= -e] can also trigger the same bug for pools on top of ZFS volumes. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 6 17:10:37 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DE3AB06A73 for ; Wed, 6 Apr 2016 17:10:37 +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 mx1.freebsd.org (Postfix) with ESMTPS id 7EE021FDB for ; Wed, 6 Apr 2016 17:10:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u36HAbjs060342 for ; Wed, 6 Apr 2016 17:10:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Wed, 06 Apr 2016 17:10:37 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 17:10:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed Apr 6 20:43:15 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65549B06562 for ; Wed, 6 Apr 2016 20:43:15 +0000 (UTC) (envelope-from leo.prasath@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32404122B for ; Wed, 6 Apr 2016 20:43:15 +0000 (UTC) (envelope-from leo.prasath@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id 2so70793907ioy.1 for ; Wed, 06 Apr 2016 13:43:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=Bkd8PagxCyUYYTVZg0WErnat9bIq09FHLPmZgbZV5cw=; b=gnr6s6kO3ScHcX5lbDZ0gzK5Pwbd4IcVH1Eo6tb0Lik2mBoDfwNJhQVbZu2CC1tyFJ OYW0fpF7vSotFcxyKsT+v8rg+Fd859H2Vc3NJp50akHmd7AYB4g9bfvVv+Ckvbx4HNIW I+/uA2mjuZsjpV77dk4PRDTJowxTddLQsYsBl95H5++ppm4MMJEF1m10UzgH824KFx8L Fvh4sMpxLuVmCjU0fEL26IHWyt3BL9ydzXwxeRJEP4sjyFWYhbIv8G2YP8Zt1knl+jVc 24ThnCCt2qWAH4NmQaCuf56YRcB6ujmShNcFZH4FwyI6wfMfM2jYoVFmXtmL2MV9uoqg UTjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Bkd8PagxCyUYYTVZg0WErnat9bIq09FHLPmZgbZV5cw=; b=ih4fXAPHMMwT/T5s8gssoIiNDxz03m4lENK2aOt4syKPnB998hK5HU67NKs3aSE+4H iHrP+gl8Il22FB8VD8Ax5K1xOXbWTpP8VdAZstX7NhJre1ROeA7DRul67zjb3Y6UbOk6 9mjENez57JEZxCW4fqtxAcqd5pCSIQjgHxyd1mfmccHVhMUdAKcT89TyZnjGweg2RYxQ ftr9VQeCo6AqpUNL1hFpH/rZUHfCcle+XpBQSyfKJ2rRIDCpHmCojjQ+vMKdksW/sy7c VVTdNwoKzDnuQ6qd8Pj4gHUl7QYt91l4l4xbrstwHo63ebCy5jUAnGM5QzBCecHCDPLI fFTQ== X-Gm-Message-State: AD7BkJLrSJ/9VEtTcoyAr7ONjtFOhPfinDfTW86FqEQmO50/zcnKKCcH9EyXeySN3sPa5YAxtICDAAarWDAMVA== X-Received: by 10.107.29.212 with SMTP id d203mr22773155iod.6.1459975394575; Wed, 06 Apr 2016 13:43:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.91.83 with HTTP; Wed, 6 Apr 2016 13:42:55 -0700 (PDT) From: Leo Prasath Arulraj Date: Wed, 6 Apr 2016 15:42:55 -0500 Message-ID: Subject: Does ZFS or UFS classify FS Metatada I/O requests with specific BIO_META like flag? To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 20:43:15 -0000 Linux file systems pass down a metadata flag with block i/o requests so that the device driver below the file system have this information. This flag could be set on those block I/O requests that the file system issues to file system metadata information like FS inodes, journal , block allocation bitmaps etc. on the disk. Examples: 1) Ext3: This thread here : http://lists.linuxfoundation.org/pipermail/containers/2009-April/017126.html says ext3 file system sets this flag on metadata i/o requests so that it is prioritized over data i/o requests in the I/O controller for the disk. 2) Ext4: This thread tells how ext4 tags all journal i/o with the metadata flag : http://www.spinics.net/lists/linux-ext4/msg18213.html 3) XFS: This thread says XFS file system tags metadata I/O requests for better merging: http://oss.sgi.com/pipermail/xfs/2009-November/004631.html I want to know if the FreeBSD filesystem UFS and ZFS set any such flag. >From a skim through the source code, it does not seem so because the bio structure itself does not have any such flag in the first place : http://fxr.watson.org/fxr/source/sys/bio.h?v=FREEBSD10#L143,144 I approciate any help regarding this. Thanks, Leo From owner-freebsd-fs@freebsd.org Wed Apr 6 21:10:32 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69A1EB06CEE for ; Wed, 6 Apr 2016 21:10:32 +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 mx1.freebsd.org (Postfix) with ESMTPS id 5A71D1ED6 for ; Wed, 6 Apr 2016 21:10:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u36LAW27003282 for ; Wed, 6 Apr 2016 21:10:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Wed, 06 Apr 2016 21:10:32 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2016 21:10:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #10 from Andriy Gapon --- Created attachment 169058 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D169058&action= =3Dedit possible patch for stable/9 zfs In fact, this patch might help with the problem at hand (while not solving = the larger problem, but that would be a different story). --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Apr 7 01:47:39 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9885B062A2 for ; Thu, 7 Apr 2016 01:47:39 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from smtp.simplesystems.org (smtp.simplesystems.org [65.66.246.90]) (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 8AFBD1A8A for ; Thu, 7 Apr 2016 01:47:39 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by smtp.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id u371kSk3005242; Wed, 6 Apr 2016 20:46:28 -0500 (CDT) Date: Wed, 6 Apr 2016 20:46:28 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Leo Prasath Arulraj cc: freebsd-fs@freebsd.org Subject: Re: Does ZFS or UFS classify FS Metatada I/O requests with specific BIO_META like flag? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (GSO 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (smtp.simplesystems.org [65.66.246.90]); Wed, 06 Apr 2016 20:46:28 -0500 (CDT) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 01:47:39 -0000 On Wed, 6 Apr 2016, Leo Prasath Arulraj wrote: > > I want to know if the FreeBSD filesystem UFS and ZFS set any such flag. > From a skim through the source code, it does not seem so because the bio > structure itself does not have any such flag in the first place : > http://fxr.watson.org/fxr/source/sys/bio.h?v=FREEBSD10#L143,144 > > I approciate any help regarding this. Zfs would have no use for any such thing since it does everything in terms of transaction groups (delimited by a disk cache sync of data for involved disks, followed by a TXG write, followed by a disk cache sync). Only synchronous writes get any priority, but they are prioritized by writing to a separate synchronous write log (as well as async/sync data targeted for the current transaction group) so that the request is not lost if the transaction group is otherwise lost. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@freebsd.org Fri Apr 8 13:40:50 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DA08B08390 for ; Fri, 8 Apr 2016 13:40:50 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9A2B81DF7 for ; Fri, 8 Apr 2016 13:40:49 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA08305; Fri, 08 Apr 2016 16:40:47 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1aoWeV-000D2p-8p; Fri, 08 Apr 2016 16:40:47 +0300 Subject: Re: Kernel panic zio.c, line: 270 FreeBSD 10.2 (or 10.3) To: DemIS , Steven Hartland , "freebsd-fs@freebsd.org" References: <1061671455578760@web3g.yandex.ru> <56C2655F.9010809@multiplay.co.uk> <1076701455583595@web2g.yandex.ru> <56C2782E.2010404@multiplay.co.uk> <2311371455610101@web11j.yandex.ru> <56C2E7A6.9090004@multiplay.co.uk> <4332271457902960@web8o.yandex.ru> From: Andriy Gapon Message-ID: <5707B4A7.4070203@FreeBSD.org> Date: Fri, 8 Apr 2016 16:39:51 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <4332271457902960@web8o.yandex.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 13:40:50 -0000 On 13/03/2016 23:02, DemIS wrote: > #10 0xffffffff8244ef8b in dbuf_read (db=0xfffff803b1e8de00, zio=0xfffff80071def398, flags=6) > at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c:621 ... > #11 0xffffffff8245a777 in dmu_spill_hold_by_dnode (dn=0xfffff805c8be5000, flags=6, tag=0x0, dbp=0xfffff802f48dfa28) > at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:333 > db = (dmu_buf_impl_t *) 0xfffff803b1e8de00 > err = -512 If you still have this crash dump, then can you please do the following in kgdb? set print pretty fr 11 p/x *dn fr 10 p/x *db I suspect that the following change might be able to prevent future corruption of your files, but it won't help with already corrupted files: https://github.com/openzfs/openzfs/pull/81/commits/ee09d80ceafa7ff7930d1e45dddc21ca3d7a87cb The following completely untested patch might help to avoid panics with the corrupted files, but no promises: diff --git a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c index 4396c01334015..94b353d62e3e6 100644 --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c @@ -329,7 +329,10 @@ dmu_spill_hold_by_dnode rw_exit(&dn->dn_struct_rwlock); ASSERT(db != NULL); - err = dbuf_read(db, NULL, flags); + if (db->db.db_size > 0) + err = dbuf_read(db, NULL, flags); + else + err = ENOENT; if (err == 0) *dbp = &db->db; else -- Andriy Gapon From owner-freebsd-fs@freebsd.org Fri Apr 8 18:05:05 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70BA0B07CE1 for ; Fri, 8 Apr 2016 18:05:05 +0000 (UTC) (envelope-from demis@yandex.ru) Received: from forward11o.cmail.yandex.net (forward11o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::1e1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B3BF1045; Fri, 8 Apr 2016 18:05:04 +0000 (UTC) (envelope-from demis@yandex.ru) Received: from web20o.yandex.ru (web20o.yandex.ru [IPv6:2a02:6b8:0:1a2d::5:120]) by forward11o.cmail.yandex.net (Yandex) with ESMTP id ADB2621691; Fri, 8 Apr 2016 21:05:00 +0300 (MSK) Received: from web20o.yandex.ru (localhost [127.0.0.1]) by web20o.yandex.ru (Yandex) with ESMTP id ECB1FEE0261; Fri, 8 Apr 2016 21:04:59 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1460138700; bh=iO5JLub+/VNob9r72WEtsuFnexj5ro8Ergl27K6c9tA=; h=From:To:In-Reply-To:References:Subject:Date; b=MSNqIpMJ8j1gNWDROHruHIST4cQoZjf94juEdtX07MFLftTE8qX2ZflcuJdnioF1H c62E/gaBe8qcCQwAjbDpu2G7mqxbL/QoldkzwFvoVko35u/MHiqOpaTZGfpZD1A3FV udxdk1VeTlGNPtzjj4qne3vkO755Shf1YhChE1zs= Received: by web20o.yandex.ru with HTTP; Fri, 08 Apr 2016 21:04:59 +0300 From: DemIS To: Andriy Gapon , Steven Hartland , "freebsd-fs@freebsd.org" In-Reply-To: <5707B4A7.4070203@FreeBSD.org> References: <1061671455578760@web3g.yandex.ru> <56C2655F.9010809@multiplay.co.uk> <1076701455583595@web2g.yandex.ru> <56C2782E.2010404@multiplay.co.uk> <2311371455610101@web11j.yandex.ru> <56C2E7A6.9090004@multiplay.co.uk> <4332271457902960@web8o.yandex.ru> <5707B4A7.4070203@FreeBSD.org> Subject: Re: Kernel panic zio.c, line: 270 FreeBSD 10.2 (or 10.3) MIME-Version: 1.0 Message-Id: <4966921460138699@web20o.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 08 Apr 2016 21:04:59 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 18:05:05 -0000 Andriy, The data you requested: (kgdb) bt full ... ... (kgdb) set print pretty (kgdb) fr 11 #11 0xffffffff8245a777 in dmu_spill_hold_by_dnode (dn=0xfffff805c8be5000, flags=6, tag=0x0, dbp=0xfffff802f48dfa28) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:333 333 err = dbuf_read(db, NULL, flags); (kgdb) p/x *dn $1 = { dn_struct_rwlock = { lock_object = { lo_name = 0xffffffff825bd369, lo_flags = 0x2730000, lo_data = 0x0, lo_witness = 0x0 }, sx_lock = 0x11 }, dn_link = { list_next = 0xfffff805c8be0600, list_prev = 0xfffff805c8be4be0 }, dn_objset = 0xfffff80086ebd400, dn_object = 0x798100, dn_dbuf = 0xfffff805b2fdc2a0, dn_handle = 0xfffff805b2feb008, dn_phys = 0xfffffe001589e000, dn_type = 0x14, dn_bonuslen = 0x130, dn_bonustype = 0x2c, dn_nblkptr = 0x1, dn_checksum = 0x0, dn_compress = 0x0, dn_nlevels = 0x1, dn_indblkshift = 0xe, dn_datablkshift = 0x9, dn_moved = 0x0, dn_datablkszsec = 0x1, dn_datablksz = 0x200, dn_maxblkid = 0x0, dn_next_type = {0x0, 0x0, 0x0, 0x0}, dn_next_nblkptr = {0x0, 0x0, 0x0, 0x0}, dn_next_nlevels = {0x0, 0x0, 0x0, 0x0}, dn_next_indblkshift = {0x0, 0x0, 0x0, 0x0}, dn_next_bonustype = {0x0, 0x0, 0x0, 0x0}, dn_rm_spillblk = {0x0, 0x0, 0x0, 0x0}, dn_next_bonuslen = {0x0, 0x0, 0x0, 0x0}, dn_next_blksz = {0x0, 0x0, 0x0, 0x0}, dn_dbufs_count = 0x3, dn_unlisted_l0_blkid = 0xffffffffffffffff, dn_dirty_link = {{ list_next = 0x0, list_prev = 0x0 }, { list_next = 0x0, list_prev = 0x0 }, { list_next = 0xfffff80086ebd6c0, list_prev = 0xfffff80548419c98 }, { list_next = 0x0, list_prev = 0x0 }}, ---Type to continue, or q to quit--- dn_mtx = { lock_object = { lo_name = 0xffffffff825bd37f, lo_flags = 0x2730000, lo_data = 0x0, lo_witness = 0x0 }, sx_lock = 0x1 }, dn_dirty_records = {{ list_size = 0xd8, list_offset = 0x0, list_head = { list_next = 0xfffff805c8be5128, list_prev = 0xfffff805c8be5128 } }, { list_size = 0xd8, list_offset = 0x0, list_head = { list_next = 0xfffff805c8be5148, list_prev = 0xfffff805c8be5148 } }, { list_size = 0xd8, list_offset = 0x0, list_head = { list_next = 0xfffff803c1d2a000, list_prev = 0xfffff803c1d2a000 } }, { list_size = 0xd8, list_offset = 0x0, list_head = { list_next = 0xfffff805c8be5188, list_prev = 0xfffff805c8be5188 } }}, dn_free_ranges = {0x0, 0x0, 0x0, 0x0}, dn_allocated_txg = 0x0, dn_free_txg = 0x0, dn_assigned_txg = 0x123a3ba, dn_notxholds = { cv_description = 0xffffffff825bd39d, cv_waiters = 0x0 }, dn_dirtyctx = 0x1, dn_dirtyctx_firstset = 0xfffff804e0fefcf0, dn_tx_holds = { rc_count = 0x2 }, dn_holds = { rc_count = 0x6 }, dn_dbufs_mtx = { ---Type to continue, or q to quit--- lock_object = { lo_name = 0xffffffff825bd38b, lo_flags = 0x2730000, lo_data = 0x0, lo_witness = 0x0 }, sx_lock = 0x1 }, dn_dbufs = { avl_root = 0xfffff803b7a7a5f0, avl_compar = 0xffffffff8247b100, avl_offset = 0xb0, avl_numnodes = 0x2, avl_size = 0xe0 }, dn_bonus = 0xfffff80052609620, dn_have_spill = 0x1, dn_zio = 0xfffff801db5bcac8, dn_oldused = 0x0, dn_oldflags = 0x0, dn_olduid = 0x271a, dn_oldgid = 0x2711, dn_newuid = 0x271a, dn_newgid = 0x2711, dn_id_flags = 0x5, dn_zfetch = { zf_rwlock = { lock_object = { lo_name = 0xffffffff825c11ef, lo_flags = 0x2730000, lo_data = 0x0, lo_witness = 0x0 }, sx_lock = 0x1 }, zf_stream = { list_size = 0x70, list_offset = 0x58, list_head = { list_next = 0xfffff805c8be52c8, list_prev = 0xfffff805c8be52c8 } }, zf_dnode = 0xfffff805c8be5000, zf_stream_cnt = 0x0, zf_alloc_fail = 0x0 } } (kgdb) fr 10 #10 0xffffffff8244ef8b in dbuf_read (db=0xfffff803b1e8de00, zio=0xfffff80071def398, flags=6) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c:621 621 dbuf_read_impl(db, zio, &flags); (kgdb) p/x *db $2 = { db = { db_object = 0x798100, db_offset = 0x0, db_size = 0x0, db_data = 0x0 }, db_objset = 0xfffff80086ebd400, db_dnode_handle = 0xfffff805b2feb008, db_parent = 0xfffff805b2fdc2a0, db_hash_next = 0x0, db_blkid = 0xfffffffffffffffe, db_blkptr = 0xfffffe001589e180, db_level = 0x0, db_mtx = { lock_object = { lo_name = 0xffffffff825bb470, lo_flags = 0x2730000, lo_data = 0x0, lo_witness = 0x0 }, sx_lock = 0x1 }, db_state = 0x3, db_holds = { rc_count = 0x2 }, db_buf = 0x0, db_changed = { cv_description = 0xffffffff825bb47c, cv_waiters = 0x0 }, db_data_pending = 0x0, db_last_dirty = 0x0, db_link = { avl_child = {0x0, 0x0}, avl_pcb = 0xfffff803b7a7a5f5 }, db_user_ptr = 0x0, db_evict_func = 0x0, db_immediate_evict = 0x0, db_freed_in_flight = 0x0, db_dirtycnt = 0x0 } (kgdb) 08.04.2016, 16:40, "Andriy Gapon" : > On 13/03/2016 23:02, DemIS wrote: >> š#10 0xffffffff8244ef8b in dbuf_read (db=0xfffff803b1e8de00, zio=0xfffff80071def398, flags=6) >> šššššat /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c:621 > > ... >> š#11 0xffffffff8245a777 in dmu_spill_hold_by_dnode (dn=0xfffff805c8be5000, flags=6, tag=0x0, dbp=0xfffff802f48dfa28) >> šššššat /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:333 >> šššššššššdb = (dmu_buf_impl_t *) 0xfffff803b1e8de00 >> šššššššššerr = -512 > > If you still have this crash dump, then can you please do the following in kgdb? > > set print pretty > fr 11 > p/x *dn > fr 10 > p/x *db > > I suspect that the following change might be able to prevent future corruption > of your files, but it won't help with already corrupted files: > https://github.com/openzfs/openzfs/pull/81/commits/ee09d80ceafa7ff7930d1e45dddc21ca3d7a87cb > > The following completely untested patch might help to avoid panics with the > corrupted files, but no promises: > > diff --git a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c > b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c > index 4396c01334015..94b353d62e3e6 100644 > --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c > +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c > @@ -329,7 +329,10 @@ dmu_spill_hold_by_dnode > šššššššššššššššššrw_exit(&dn->dn_struct_rwlock); > > šššššššššASSERT(db != NULL); > - err = dbuf_read(db, NULL, flags); > + if (db->db.db_size > 0) > + err = dbuf_read(db, NULL, flags); > + else > + err = ENOENT; > šššššššššif (err == 0) > ššššššššššššššššš*dbp = &db->db; > šššššššššelse > > -- > Andriy Gapon Demis. From owner-freebsd-fs@freebsd.org Sat Apr 9 13:28:36 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B21D5B09CBC for ; Sat, 9 Apr 2016 13:28:36 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 19A471278; Sat, 9 Apr 2016 13:28:34 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA12677; Sat, 09 Apr 2016 16:28:33 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1aoswD-000FBZ-4r; Sat, 09 Apr 2016 16:28:33 +0300 To: freebsd-fs Cc: Will Andrews , Pawel Jakub Dawidek , Alexander Motin From: Andriy Gapon Subject: zfs: re-use of geom consumer in vdev_geom Message-ID: <57090349.6040206@FreeBSD.org> Date: Sat, 9 Apr 2016 16:27:37 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2016 13:28:36 -0000 Does anyone know why we re-use GEOM consumers in vdev_geom? I mean, it seems that multiple ZFS vdevs could be using the same consumer attached to a particular provider. When is this needed? Couldn't every vdev have its won consumer? Do we have situations where more than vdev would use the same provider in the read-write mode? Or one vdev would want the read-write mode while another would have it in read-only mode? Thank you. -- Andriy Gapon