Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

On 8/4/17 7:01 pm, Edward Tomasz Napierała wrote: On 0313T1206, Pete French wrote: I have a number of machines in Azure, all booting from ZFS and, until the weekend, running 10.3 perfectly happily. I started upgrading these to 11. The first went fine, the second would not boot. Looking at the

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

On 0313T1206, Pete French wrote: > I have a number of machines in Azure, all booting from ZFS and, until > the weekend, running 10.3 perfectly happily. > > I started upgrading these to 11. The first went fine, the second would > not boot. Looking at the boot diagnistics it is having problems

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

On 0316T1004, Warner Losh wrote: > [[ stupid mouse ]] > > On Thu, Mar 16, 2017 at 10:01 AM, Warner Losh wrote: > > On Thu, Mar 16, 2017 at 6:06 AM, Pete French > > wrote: > >>> I don't like the delay and retry approach at all. > >> > >> Its not

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

this was a bug in 10.3 that I thought was fixed in 11.. I believe it's fixed in 10-stable. Maybe 11.0 missed it? if you still see this bug look at adding the patch in bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208882 it makes the mountroot code retry, which is all you need.

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

[[ stupid mouse ]] On Thu, Mar 16, 2017 at 10:01 AM, Warner Losh wrote: > On Thu, Mar 16, 2017 at 6:06 AM, Pete French > wrote: >>> I don't like the delay and retry approach at all. >> >> Its not ideal, but it is what we do for UFS after all... >>

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

On Thu, Mar 16, 2017 at 6:06 AM, Pete French wrote: >> 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

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

> 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

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

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? >>

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

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

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

On 13/03/2017 21:07, Edward Tomasz Napierała wrote: > Are you sure the above transcript is right? There are three reasons > I'm asking. First, you'll see the "Root mount waiting" message, > which means the root mount code is, well, waiting for storvsc, exactly > as expected. Second - there is

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

> Are you sure the above transcript is right? There are three reasons > I'm asking. First, you'll see the "Root mount waiting" message, > which means the root mount code is, well, waiting for storvsc, exactly > as expected. Second - there is no "Trying to mount root". But most > of all - for

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

On 0313T1206, Pete French wrote: > I have a number of machines in Azure, all booting from ZFS and, until > the weekend, running 10.3 perfectly happily. > > I started upgrading these to 11. The first went fine, the second would > not boot. Looking at the boot diagnistics it is having problems

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

> The variable still exists but is ignored when using ZFS. > > It's a known issue. You could try this patch: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882#c3 Ah, OK, thanks... > Manually specifying the root pool should workaround the issue. Interesting, I didnt think of trying

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

Pete French wrote: > I have a number of machines in Azure, all booting from ZFS and, until > the weekend, running 10.3 perfectly happily. > > I started upgrading these to 11. The first went fine, the second would > not boot. Looking at the boot diagnistics it is

Re: moutnroot failing on zpools in Azure after upgrade from 10 to 11 due to lack of waiting for da0

One extra datapoint - the machines which do not fail are the small DS1_v2 instances. These seem to boot fine, but if I move to the DS2 size then the problem shows up. -pete. ___ freebsd-stable@freebsd.org mailing list