Date: Thu, 16 Mar 2017 11:18:13 +0000 From: Pete French <petefrench@ingresso.co.uk> To: Andriy Gapon <avg@FreeBSD.org>, stable@FreeBSD.org Subject: Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0 Message-ID: <5da1d6d9-27fd-4b53-4d8f-8fe52b5ac846@ingresso.co.uk> In-Reply-To: <ca98a21f-f510-36aa-b8a7-20f4bf4bec59@FreeBSD.org> References: <E1cnOkS-0000oL-Ia@dilbert.ingresso.co.uk> <20170313190728.GA2967@brick> <ca98a21f-f510-36aa-b8a7-20f4bf4bec59@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5da1d6d9-27fd-4b53-4d8f-8fe52b5ac846>