Date: Mon, 12 Mar 2018 11:37:41 -0600 From: Ian Lepore <ian@freebsd.org> To: Pete French <petefrench@ingresso.co.uk>, freebsd-stable@freebsd.org Subject: Re: zfs problems after rebuilding system [SOLVED] Message-ID: <1520876261.84937.222.camel@freebsd.org> In-Reply-To: <831aa29b-6464-eb6c-e9c9-058963756ec8@ingresso.co.uk> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <CAOtMX2g79aqkinu0meBzhLbui7n9H9yiEwxKm6cxpZSaxbWqbg@mail.gmail.com> <f0e9385c-4d62-a68d-ea93-f013bc456b5d@zyxst.net> <CAOjFWZ4Yq4cnWN_qucbN4W-6qtf4NYNzjNKe4QL17DU-Q=N%2B_g@mail.gmail.com> <CAOjFWZ53WaOtCvRtNpsL1OqgE7rDu8jWNEHRVPZ5Z3Q_n1bnqw@mail.gmail.com> <CAOjFWZ6gF3=N8=v3aXQaiG=pd8kmZ-xpvN2jHYj9%2Bh8fCm=rsw@mail.gmail.com> <CAOjFWZ7nPFdKr_G2qHihXdcHUBed7V0uLLHM9=p1PKzJMZNemw@mail.gmail.com> <CAOjFWZ6J7UV_xXxtASqnonS8qatqaSSEqJUKyi9nw%2Bms%2BUg1QQ@mail.gmail.com> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> <edfb5da8-3fad-168f-4dbc-6da9b0822c76@zyxst.net> <20180303234236.M3811@besplex.bde.org> <9b3cd942-347c-44a2-60d6-0b3c4a45552f@ingresso.co.uk> <1520723109.84937.136.camel@freebsd.org> <84146241-12d3-8333-0687-c2377838f175@ingresso.co.uk> <1520723722.84937.139.camel@freebsd.org> <217437b9-9879-8919-966a-45cf5eb58d33@ingresso.co.uk> <1520725685.84937.144.camel@freebsd.org> <831aa29b-6464-eb6c-e9c9-058963756ec8@ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1520876261.84937.222.camel>