Date: Sat, 10 Mar 2018 16:05:09 -0700 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: <1520723109.84937.136.camel@freebsd.org> In-Reply-To: <9b3cd942-347c-44a2-60d6-0b3c4a45552f@ingresso.co.uk> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <CAOtMX2jfmh%2BAMccAMcPSRq-DcQgs6wioqSSUHncEfPruD=w_Ag@mail.gmail.com> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <CAOtMX2gHm_UdYzn5J6Lm76r8KakkYMzEcxddFYLqkmGYwkihuQ@mail.gmail.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2018-03-03 at 16:19 +0000, Pete French wrote: > > > > > That won't work for the boot drive. > > > > When no boot drive is detected early enough, the kernel goes to the > > mountroot prompt. That seems to hold a Giant lock which inhibits > > further progress being made. Sometimes progress can be made by > > trying > > to mount unmountable partitions on other drives, but this usually > > goes > > too fast, especially if the USB drive often times out. > > > We have this problem in Azure with a ZFS root, was fixed by the pacth > in > this bug report, which actually starts off being about USB. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208882 > > You can then set the mountroot timeout as normal and it works. > > I wold really like this patch to be applied, but it seems to have > languished since last summer. We use this as standard on all our > cloud > machines now, and it works very nicely. > > -pete. I've committed a fix to -current (r330745) based on that patch. It would be good if people running -current who've had this problem could give it some testing. I'd like to get it merged back to 11 before the 11.1 release (and back to 10-stable as well). With r330745 in place, the only setting that should be needed if your rootfs is on a device that is slow to arrive is vfs.mountroot.timeout= in loader.conf; the value is the number of seconds to wait before giving up and going to the mountroot prompt. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1520723109.84937.136.camel>