Date: Sun, 7 Aug 2022 18:43:44 -0400 From: Glen Barber <gjb@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: Warner Losh <imp@bsdimp.com>, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Ed Maste <emaste@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Looks like the arm 20220805 snapshots are still odd, so probably kern.geom.part.mbr.enforce_chs=0 was still in use Message-ID: <0E0083BD-A749-4112-8FDA-62326EA95F8A@freebsd.org> In-Reply-To: <6AF28022-A8E7-46B3-B64E-99D217E9B6AC@yahoo.com> References: <6AF28022-A8E7-46B3-B64E-99D217E9B6AC@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Will do. I=E2=80=99ll commit the suggested change to main tomorrow.
Thank you for your vigilant investigation.
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Aug 7, 2022, at 3:50 PM, Mark Millard <marklmi@yahoo.com> wrote:
>=20
> =EF=BB=BFOn 2022-Aug-7, at 12:32, Glen Barber <gjb@freebsd.org> wrote:
>=20
>> Correct, it was set to =E2=80=9C0=E2=80=9D for these builds.
>>=20
>> I honestly do not have any idea where the problems you are seeing are cre=
eping in.
>>=20
>> Should it be set back to =E2=80=9C1=E2=80=9D? I=E2=80=99m not sure how t=
o proceed otherwise.
>=20
> My guess is that if the release/tools/arm.subr line:
>=20
> chroot ${CHROOTDIR} gpart add -t freebsd-ufs -a 64k ${mddev}s=
2
>=20
> was instead (note the added -b use):
>=20
> chroot ${CHROOTDIR} gpart add -t freebsd-ufs -b 64k -a 64k ${=
mddev}s2
>=20
> then the line:
>=20
> chroot ${CHROOTDIR} newfs -U -L rootfs /dev/${mddev}s2a
>=20
> would work as expected and things would still be aligned:
> no aliasing of BSD vs. freebsd-ufs. (In part this is by
> prior steps already having achieved alignment of BSD.)
>=20
> But I do not know how to classify doing so: Work around?
> Known required-procedure for -L rootfs to correctly
> identify the the freebsd-ufs /dev/${mddev}s2a ?
>=20
> Absent better information from folks that know more, I'd
> suggest trying such an adjusted release/tools/arm.subr
> next week, leaving kern.geom.part.mbr.enforce_chs=3D0 in
> place, if such an experiment can be reasonable.
>=20
>> Glen
>> Sent from my phone.
>> Please excuse my brevity and/or typos.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0E0083BD-A749-4112-8FDA-62326EA95F8A>