Date: Thu, 16 Mar 2017 13:31:36 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Pete French <petefrench@ingresso.co.uk>, 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: <6b397d83-e802-78ca-e24e-6d0713f07212@FreeBSD.org> In-Reply-To: <5da1d6d9-27fd-4b53-4d8f-8fe52b5ac846@ingresso.co.uk> References: <E1cnOkS-0000oL-Ia@dilbert.ingresso.co.uk> <20170313190728.GA2967@brick> <ca98a21f-f510-36aa-b8a7-20f4bf4bec59@FreeBSD.org> <5da1d6d9-27fd-4b53-4d8f-8fe52b5ac846@ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16/03/2017 13:18, Pete French wrote: > >> 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. I don't like the delay and retry approach at all. Imagine that you told the kernel that you want to mount your root from a ZFS pool which is on a USB driver which you have already thrown out. Should the kernel just keep waiting for that pool to appear? Microsoft provides support for FreeBSD Hyper-V drivers. Please try to discuss this problem on virtualization@ or with sephe@ directly. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6b397d83-e802-78ca-e24e-6d0713f07212>