From owner-freebsd-current@freebsd.org Wed Oct 18 16:58:35 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1146E3E8CA for ; Wed, 18 Oct 2017 16:58:35 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6AB21664; Wed, 18 Oct 2017 16:58:35 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 8FB3E2BC6; Wed, 18 Oct 2017 16:58:34 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 18 Oct 2017 16:58:32 +0000 From: Glen Barber To: John Baldwin Cc: freebsd-current@freebsd.org, David Boyd , "mckusick@mckusick.com" Subject: Re: VM images for 12.0-CURRENT showing checksum failed messages Message-ID: <20171018165832.GU55623@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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="U7F658e60E1K4csu" Content-Disposition: inline In-Reply-To: <20171018164022.GT55623@FreeBSD.org> User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 16:58:35 -0000 --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 .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--