From owner-freebsd-fs@freebsd.org Sun Aug 13 15:41:42 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 04F52DC5218 for ; Sun, 13 Aug 2017 15:41:42 +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 E65FB734AB for ; Sun, 13 Aug 2017 15:41:41 +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 v7DFffZD003967 for ; Sun, 13 Aug 2017 15:41:41 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: Sun, 13 Aug 2017 15:41:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 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: Sun, 13 Aug 2017 15:41:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221075 --- Comment #14 from Marius Strobl --- Yeah, I've missed that sdhci_pci(4) actually is attaching, probably due to a typo in the search field. Still, the only explanation I have is that the sheer presence of the geom_flasmap(4) class is triggering a GEOM-related ra= ce. Especially, since you apparently didn't have a SD card inserted, so neither mmc(4) nor mmcsd(4) did attach and, consequently, no additional disk(9) was present. I can't find a GEOM-related change not present in stable/11 which looks like it would fix such a race. Thus, I suspect that the particular race in fact = is also present in head, but due to some differences in timing you don't happen to hit it there. Recently it has been mentioned that geom_label(4) is racy, too: https://lists.freebsd.org/pipermail/svn-src-all/2017-August/149683.html The fact that as mentioned in that e-mail, bsdinstall(8) therefore doesn't use labels - but apparently you do in your ZFS setup - might also explain w= hy not more people are hitting the problem you see. So it could be worthwhile = to try whether using ada[0,1]p1 directly for the zpools instead of DISK-p1 labels reliably gets you rid of the problem. Apart from that I don't have an idea how to further debug the actual cause. Part of the problem is that there are several known GEOM-related races, some even documented in the code of geom(4). So changing something or even fixing one race just might alter the timing enough so that the real culprit is hid= den. Another part is that I only know how geom(4) debugging output differs when hitting the race I mentioned earlier, but I don't know how it would differ for the other races, for example the geom_label(4)-related one. --=20 You are receiving this mail because: You are the assignee for the bug.=