On Mon, 2018-03-12 at 17:21 +0000, Pete French wrote: > > On 10/03/2018 23:48, Ian Lepore wrote: > > > > I based my fix heavily on that patch from the PR, but I rewrote it > > enough that I might've made any number of mistakes, so it needs fresh > > testing. The main change I made was to make it a lot less noisy while > > waiting (it only mentions the wait once, unless bootverbose is set, in > > which case it's once per second). I also removed the logic that > > limited the retries to nfs and zfs, because I think we can remove all > > the old code related to waiting that only worked for ufs and let this > > new retry be the way it waits for all filesystems. But that's a bigger > > change we can do separately; I didn't want to hold up this fix any > > longer. > TThansk for the patch, its is very much appercaited! I applied this > earlier today, and have been continuously rebooting the machine in Azure > ever since (every ten minutes). This has worked flawlessly, so I am very > happy that this fixes the issue for me. I am going to leave it running > though, just to see if anything happens. I havent examined dmesg, but I > thould be able to see the output from the patch there to verify that its > waiting, yes ? > > cheers, > > -pete.
Yes, if the root filesystem isn't available on the first attempt, it should emit a single line saying it will wait for up to N seconds for it to arrive, where N is the vfs.mountroot.timeout value (3 seconds if not set in loader.conf). -- Ian _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
