From owner-freebsd-stable@freebsd.org  Thu Mar 16 11:18:15 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 64080D0FB98
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Thu, 16 Mar 2017 11:18:15 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 5059410F1
 for <freebsd-stable@freebsd.org>; Thu, 16 Mar 2017 11:18:15 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 4FAF9D0FB97; Thu, 16 Mar 2017 11:18:15 +0000 (UTC)
Delivered-To: stable@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 4F50FD0FB96
 for <stable@mailman.ysv.freebsd.org>; Thu, 16 Mar 2017 11:18:15 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3])
 (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 1EE5610F0;
 Thu, 16 Mar 2017 11:18:15 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6])
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>)
 id 1coTQ5-0006KP-Qb; Thu, 16 Mar 2017 11:18:13 +0000
Subject: Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11
 due to lack of waiting for da0
To: Andriy Gapon <avg@FreeBSD.org>, stable@FreeBSD.org
References: <E1cnOkS-0000oL-Ia@dilbert.ingresso.co.uk>
 <20170313190728.GA2967@brick>
 <ca98a21f-f510-36aa-b8a7-20f4bf4bec59@FreeBSD.org>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <5da1d6d9-27fd-4b53-4d8f-8fe52b5ac846@ingresso.co.uk>
Date: Thu, 16 Mar 2017 11:18:13 +0000
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <ca98a21f-f510-36aa-b8a7-20f4bf4bec59@FreeBSD.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Mar 2017 11:18:15 -0000


> So, the kernel attempted to mount the root even before vmbus was attached and,
> thus, before storvsc appeared and informed the kernel that it might be holding
> the root.
> How ZFS was supposed to know that vmbus is ever going to appear?
> To me this sounds more like a problem with the Hyper-V drivers.

I am currently running with the patch which waits for a number fo 
seconds and retries the mount, and that appears t fix it. However I dont 
really like rnning a patched OS. How would I set about reporting this to 
Microsoft and getting it fixed, or getting the timeoutpatch commited ? 
Preferably both, as the timeout patch is generally a useful thing to 
have working for ZFS I think.

-pete.