Date: Wed, 6 Dec 2017 17:38:21 -0700 From: Warner Losh <imp@bsdimp.com> To: lausts@acm.org Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: GPTZFSBOOT in Current r326622 has problems Message-ID: <CANCZdfp22GO%2BzQfJN=KvVpbSy0n_Cek_0rTZp2Og%2Bc-MeSQeNg@mail.gmail.com> In-Reply-To: <20171207001720.GA2058@mail.laus.org> References: <d92d0e84-72c5-e240-a1b5-18cef53dcbff@acm.org> <CANCZdfqHZidf%2BZvf3Pqpr1BHuyRPBP9zLSzkw_CcFqJde2KzYw@mail.gmail.com> <20171206164801.GA1055@mail.laus.org> <CANCZdfp0AS-=xD8KvqgPkpFnM_7-Gc=CmLiHE9T=qo0_d1zYwg@mail.gmail.com> <20171206222155.GA1792@mail.laus.org> <CANCZdfoQQjDi-vhyLTkxEekHqoSncO0nvwE6qbhEXiMiELhhFQ@mail.gmail.com> <20171207001720.GA2058@mail.laus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 6, 2017 at 5:17 PM, Thomas Laus <lausts@acm.org> wrote: > Warner Losh [imp@bsdimp.com] wrote: > > You can just build the boot blocks at each step if you'd like to save > some > > time on the binary search. > > > > cd stand > > make cleandir obj depend > > make -j XX > > sudo -E make install > > > Warren: > > I built and loaded r326500 successfully. It looks like the problem is > after r326500 and before r326662. OK. Still a fair number of changes, including changes to geli to fix warnings... 326585-326594 is a flurry of changes. Then another in the 326609-326610 range. There's one other trivial one. I'd wager that if '500 works, the breakage will be somewhere in the first range, which suggests 326590 might be a good, next pivot. There's also a few just after '500 that might break things as well if I messed something up. '504 and '507 both touch this stuff directly... Good luck! Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp22GO%2BzQfJN=KvVpbSy0n_Cek_0rTZp2Og%2Bc-MeSQeNg>