From owner-freebsd-fs@freebsd.org Sat Aug 12 16:32:17 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 CE912DE114A for ; Sat, 12 Aug 2017 16:32:17 +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 9D86D676A6 for ; Sat, 12 Aug 2017 16:32:17 +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 v7CGWHJF073922 for ; Sat, 12 Aug 2017 16:32:17 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: Sat, 12 Aug 2017 16:32:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: seschwar@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: 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: Sat, 12 Aug 2017 16:32:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221075 --- Comment #13 from seschwar@gmail.com --- So I had another go at this... (In reply to Marius Strobl from comment #12) > (is the card reader you mention a USB one?). nope: $ pciconf -lv (...) none2@pci0:11:0:0: class=3D0x0c0010 card=3D0x04a31028 chip=3D0x11f71217 re= v=3D0x05 hdr=3D0x00 vendor =3D 'O2 Micro, Inc.' device =3D 'OZ600 1394a-2000 Controller' class =3D serial bus subclass =3D FireWire none3@pci0:11:0:1: class=3D0x080501 card=3D0x04a31028 chip=3D0x83201217 re= v=3D0x05 hdr=3D0x00 vendor =3D 'O2 Micro, Inc.' device =3D 'OZ600RJ1/OZ900RJ1 SD/MMC Card Reader Controller' class =3D base peripheral subclass =3D SD host controller none4@pci0:11:0:2: class=3D0x018000 card=3D0x04a31028 chip=3D0x83301217 re= v=3D0x05 hdr=3D0x00 vendor =3D 'O2 Micro, Inc.' device =3D 'OZ600 MS/xD Controller' class =3D mass storage > The one thing that comes to my mind is that since r318197, mmcsd(4) depen= ds > on geom_flasmap(4) and that the latter might cause some interaction with = ZFS. > (...) One - not necessarily conclusive - way to > test the theory of interaction between geom_flasmap(4) and ZFS would be t= o use > a kernel built from a configuration with mmcsd(4) removed, so this depend= ency > isn't dragged in. Ok, I've build a 11.1 kernel using the following configuration: $ cat /usr/src/sys/amd64/conf/CUSTOM include GENERIC ident CUSTOM nodevice mmc nodevice mmcsd nodevice sdhci This kernel is indeed capable of mounting the root filesystem on my ZFS poo= l!=20 So your guess that base r318197 is not actually the cause of this, but mere= ly exposes the issue is probably spot on. 12.0-CURRENT not exhibiting the issue raises the question if the underlying problem is fixed there, or just happens to not be triggered. Is there a way for me to provide more information on this? Maybe boot with kern.geom.debugflags set to some appropriate value? --=20 You are receiving this mail because: You are the assignee for the bug.=