Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Mar 2017 12:06:14 +0000
From:      Pete French <petefrench@ingresso.co.uk>
To:        avg@FreeBSD.org, 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:  <E1coUAY-0000ou-8i@dilbert.ingresso.co.uk>
In-Reply-To: <6b397d83-e802-78ca-e24e-6d0713f07212@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> I don't like the delay and retry approach at all.

Its not ideal, but it is what we do for UFS after 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?

I'm not talking about an infinite loop here, just making it honour
the 'vfs.mountroot.timeout' setting like it does ofr UFS. So it
should wait for the timeout I have set and then proceed as it would if
there had been no timeout. Default behaviout is for it to behave as it
does now, its onyl when you need the retry that you enable it.

Right now this works for UFS, but not for ZFS, which is an inconsistency
that I dont like, and also means I am being forced down a UFS root
path if I require this.

> Microsoft provides support for FreeBSD Hyper-V drivers.
> Please try to discuss this problem on virtualization@ or with sephe@ directly.

OK, will do, thanks...

-pete.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1coUAY-0000ou-8i>