Date: Wed, 18 Oct 2017 16:58:32 +0000 From: Glen Barber <gjb@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org, David Boyd <David.Boyd49@twc.com>, "mckusick@mckusick.com" <mckusick@mckusick.com> Subject: Re: VM images for 12.0-CURRENT showing checksum failed messages Message-ID: <20171018165832.GU55623@FreeBSD.org> In-Reply-To: <20171018164022.GT55623@FreeBSD.org> References: <1508255864.5659.3.camel@twc.com> <2094438.bITRq4LixK@ralph.baldwin.cx> <20171018150155.GA28174@FreeBSD.org> <1740653.LGy8gQVNSR@ralph.baldwin.cx> <20171018164022.GT55623@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--U7F658e60E1K4csu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 18, 2017 at 04:40:22PM +0000, Glen Barber wrote: > On Wed, Oct 18, 2017 at 09:28:40AM -0700, John Baldwin wrote: > > On Wednesday, October 18, 2017 03:01:55 PM Glen Barber wrote: > > > On Wed, Oct 18, 2017 at 07:49:00AM -0700, John Baldwin wrote: > > > > On Tuesday, October 17, 2017 11:57:44 AM David Boyd wrote: > > > > > The FreeBSD-12.0-CURRENT-amd64-20171012-r324542.vmdk image displa= ys > > > > > many checksum failed messages when booted. (see attachment). > > > > >=20 > > > > > I think this started about 20170925. > > > > >=20 > > > > > I have VirtualBox VM's running 10.4-STABLE, 11.1-STABLE and 12.0- > > > > > CURRENT. > > > > >=20 > > > > > Only the 12.0-CURRENT image exhibits this behavior. > > > > >=20 > > > > > This is easily fixed by "fsck -y /" in single-user mode during th= e boot > > > > > process. > > > > >=20 > > > > > I can test any updates at almost any time. > > > >=20 > > > > I wonder if the tool creating the snapshot images wasn't updated to= generate > > > > cg checksums when creating the initial filesystem. Glen, do you kn= ow which > > > > tool (makefs or something else?) is used to generate the UFS filesy= stem > > > > in VM images for snapshots? (In this case it appears to be a .vmdk= image) > > > >=20 > > >=20 > > > mkimg(1) is used. > >=20 > > Does makefs generate the UFS image fed into mkimg or does mkimg generat= e the > > UFS partition itself? > >=20 >=20 > Sorry, I may have understated a bit. >=20 > First, mdconfig(8) is used to create a md(4)-backed disk, onto which > newfs(8) is run, followed by the installworld/installkernel targets. >=20 > Next, mkimg(1) is used to feed the resultant md(4)-based <format>.img > filesystem (after umount(8)) to create the final output image. >=20 Following offline discussion, the issue appears to be the build machine kernel is older than the newly-built newfs(8). Glen --U7F658e60E1K4csu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEVVuz/A7vpH93hEhKuWzd6q+LXtAFAlnniDgACgkQuWzd6q+L XtCTkQ//Yi+QQdjtJlGyUqBQ2WYLFc4uTo+hPoiDizUaCZ1BBhM7ynP6+On6M3lm adJyncYAxg7LNBA9ip/i2nj5oBc5x6E9VwqSBo00VGvlpNWPZY4yJI0GWEFKcDo7 T6vFmzOJR5b+xRBIRhM4XPwtw8KhNerfuMO5pbD7pIuWH5OQVYQXpd6PItCrF8hC 3UXuNz+a9TK377luVY5ZwFyfwXcg+1HKEN0GOpndbToEmnEmfhYQKDsQsredi9XY K+1NfPBvvmHgFEUHH2Q3LFhvuVilYtR8p5wc4yjdnvGR97kUqj3cuLx/iuDJ4+hn 8fS+oGuOaQwBLxME5Lem+oKkB/cA7jbFkbyx/zEVXeIoladLNBHHcoG99Vd/3Iei hfeoSrMC7Sg4ha6a7qww2vOa7nHrKVbBAPnZ7zqqOnQPrrDCxPEibg33t/5ye87m X46oFalXaLSHyUXPK7sR6xOmJ88Kp0Fjmmq8kgnjZJZtJGrGdLGdf/TirZagKecY j+HskS/bYp8j2U9tupp/CnK2WOzxy+PhRF+ctkfkOyfBmmY18Yty/LxUi0x7/4tG pqXQjds+VjXLNPpKoh+zH18egeK264waDt9cxbwWNrW5FQlXMr8XeHDuUpXRjwmD CLml8avbvhPNcJQqGreNQVwKRiyIK+T+/hgMnv9dwj5fddT+dnA= =9ZRP -----END PGP SIGNATURE----- --U7F658e60E1K4csu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171018165832.GU55623>