From owner-freebsd-fs@freebsd.org  Sun Mar 19 10:22:50 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
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 42E2ED11E90
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 19 Mar 2017 10:22:50 +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 320F9B87
 for <freebsd-fs@FreeBSD.org>; Sun, 19 Mar 2017 10:22:50 +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 v2JAMnDL070753
 for <freebsd-fs@FreeBSD.org>; Sun, 19 Mar 2017 10:22:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 208882] zfs root filesystem mount failure on startup in FreeBSD
 10.3-RELEASE if  USB hdd with zpool is attached to another port
Date: Sun, 19 Mar 2017 10:22:49 +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-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: julian@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: <bug-208882-3630-1uRcg22xkQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208882-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-208882-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Mar 2017 10:22:50 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882

--- Comment #11 from Julian Elischer <julian@FreeBSD.org> ---
to Edward,=20=20
teh problem is that it only knows how to wait for DEVICES,
A filesystem based approach woudl require the filesystem to report back what
devices it would need.. it might bw worth while adding a VFS method for 're=
port
availability" or something but the approach used here works fine and I'm to=
ld
it's fixed in 10-stable anyhow.

--=20
You are receiving this mail because:
You are the assignee for the bug.=