Date: Wed, 1 Jun 2022 11:04:53 -0700 From: Robert Montano <irontree043111@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: Mark Millard <marklmi@yahoo.com>, bob prohaska <fbsd@www.zefox.net>, Free BSD <freebsd-arm@freebsd.org> Subject: Re: Mountroot problems on RPi3/aarch64 Message-ID: <CABzjivf9RBrp=ptx0UoKiH2jFnXT%2B8-fWCng7R5Lj0LKugp_kg@mail.gmail.com> In-Reply-To: <CANCZdfoG_jijAK9tC7WZ_h-ZDB7Qa=m19o46tthTDgTKsfG-Pw@mail.gmail.com> References: <20220601154142.GA41835@www.zefox.net> <5FA108CF-0973-4A53-A3B7-FA7BE41EB16D@yahoo.com> <CANCZdfoG_jijAK9tC7WZ_h-ZDB7Qa=m19o46tthTDgTKsfG-Pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000008f31e505e066baa6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you for your emails! On Wed, Jun 1, 2022, 9:29 AM Warner Losh <imp@bsdimp.com> wrote: > > > On Wed, Jun 1, 2022 at 10:17 AM Mark Millard <marklmi@yahoo.com> wrote: > >> On 2022-Jun-1, at 08:41, bob prohaska <fbsd@www.zefox.net> wrote: >> >> > Since about 05/29 mountroot has been failing on a Pi3 self-hosting >> -current, >> > using a usb mechanical hard disk. >> > >> > Anybody else seen this sort of behavior? >> >> You do not report much context. FreeBSD version? UFS? ZFS? >> And so on. >> >> However, there has been today (for main): >> >> git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integrity >> checks when reading a superblock >> >> that is for fixing boot problems in UFS contexts. See: >> >> >> https://lists.freebsd.org/archives/dev-commits-src-main/2022-June/006977= .html >> >> This is for fixes related to the 2022-May-27 change: >> >> =E2=80=A2 git: 076002f24d35 - main - Do comprehensive UFS/FFS su= perblock >> integrity checks when reading a superblock. Kirk McKusick >> > > I'd expect these to fix only the boot loader issues, not the mountroot > issues, but it wouldn't hurt to try... p3 is aarch64 which is UEFI which > had the right MAXPHYS in the boot loader... though since the change is i= n > the tree, it wouldn't hurt to try it... > > Warner > --0000000000008f31e505e066baa6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Thank you for your emails!</div><br><div class=3D"gmail_q= uote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 1, 2022, 9:29 AM Wa= rner Losh <<a href=3D"mailto:imp@bsdimp.com">imp@bsdimp.com</a>> wrot= e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo= rder-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr= "><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_= attr">On Wed, Jun 1, 2022 at 10:17 AM Mark Millard <<a href=3D"mailto:ma= rklmi@yahoo.com" target=3D"_blank" rel=3D"noreferrer">marklmi@yahoo.com</a>= > wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px = 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2= 022-Jun-1, at 08:41, bob prohaska <<a href=3D"mailto:fbsd@www.zefox.net"= target=3D"_blank" rel=3D"noreferrer">fbsd@www.zefox.net</a>> wrote:<br> <br> > Since about 05/29 mountroot has been failing on a Pi3 self-hosting -cu= rrent,<br> > using a usb mechanical hard disk.=C2=A0 <br> > <br> > Anybody else seen this sort of behavior? <br> <br> You do not report much context. FreeBSD version? UFS? ZFS?<br> And so on.<br> <br> However, there has been today (for main):<br> <br> git: bc218d89200f - main - Two bug fixes to UFS/FFS superblock integrity ch= ecks when reading a superblock<br> <br> that is for fixing boot problems in UFS contexts. See:<br> <br> <a href=3D"https://lists.freebsd.org/archives/dev-commits-src-main/2022-Jun= e/006977.html" rel=3D"noreferrer noreferrer" target=3D"_blank">https://list= s.freebsd.org/archives/dev-commits-src-main/2022-June/006977.html</a><br> <br> This is for fixes related to the 2022-May-27 change:<br> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A2 git: 076002f24d35 - main - Do compreh= ensive UFS/FFS superblock integrity checks when reading a superblock. Kirk = McKusick<br></blockquote><div><br></div><div>I'd expect these to fix on= ly the boot loader issues, not the mountroot issues, but it wouldn't hu= rt to try...=C2=A0 p3 is aarch64 which is UEFI which had the right MAXPHYS = in the boot loader...=C2=A0 though since the change is in the tree, it woul= dn't hurt to try it...</div><div><br></div><div>Warner</div></div></div= > </blockquote></div> --0000000000008f31e505e066baa6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABzjivf9RBrp=ptx0UoKiH2jFnXT%2B8-fWCng7R5Lj0LKugp_kg>