From owner-freebsd-fs@freebsd.org Mon Jul 31 21:03:35 2017 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 BA85FDBD9D1 for ; Mon, 31 Jul 2017 21:03:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E65268BCB for ; Mon, 31 Jul 2017 21:03:35 +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 v6VL3ZVP011958 for ; Mon, 31 Jul 2017 21:03:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221075] regression: 11.1 is unable to mount ZFS / on boot Date: Mon, 31 Jul 2017 21:03:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marius@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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jul 2017 21:03:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221075 --- Comment #12 from Marius Strobl --- (In reply to seschwar from comment #10) Unfortunately, I don't see how r318197 could have an impact on ZFS either; that revision only touches bits related to mmc(4), mmcsd(4) and correspondi= ng bridge drivers, but no KPI, no global structure or anything like that. Moreover, according to attachments 184813 and 184814, the drivers in questi= on also don't attach on that machine (is the card reader you mention a USB one= ?). The partial merges only refer to e. g. ARM-specific bridge drivers that sim= ply don't exist in stable/11, so these omissions should impact you even less. The one thing that comes to my mind is that since r318197, mmcsd(4) depends on geom_flasmap(4) and that the latter might cause some interaction with ZF= S. Given that I'm not familiar with how ZFS interfaces with GEOM, I have no id= ea what actually could be going wrong, though. As far as geom_flasmap(4) is concerned, I can't spot an obvious bug in that regard and its code doesn't differ between head and stable/11. One - not necessarily conclusive - way to test the theory of interaction between geom_flasmap(4) and ZFS would be to = use a kernel built from a configuration with mmcsd(4) removed, so this dependen= cy isn't dragged in. In general, I'd suggest to look for unmerged fixes to GEOM and to the parts of ZFS that interface with GEOM. When interfacing mmcsd(4) with geom_flashmap(4), I've had a hard time with races in GEOM; if g_retaste(9) is called (so that an additional provider - now additionally offered by a GEOM class due to a change in configuration - should get picked up) while re-tasting is already in progress, the already ongoing re-tasting won't take note of the new provider and the new re-taste event won't actually result in an additional re-taste cycle being scheduled. If ZFS is suffering from the same or a similar bug, this doesn't necessarily mean that the problem you are hitting is present in stable/11 only; with he= ad you just might be lucky that timing differences resulting from geom_flashma= p(4) also being in the mix don't lead to a race. --=20 You are receiving this mail because: You are the assignee for the bug.=