From owner-freebsd-current@freebsd.org Wed Oct 18 15:01:58 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 49692E3B520 for ; Wed, 18 Oct 2017 15:01:58 +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 2405E811CF; Wed, 18 Oct 2017 15:01:58 +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 184D91FB; Wed, 18 Oct 2017 15:01:57 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 18 Oct 2017 15:01:55 +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: <20171018150155.GA28174@FreeBSD.org> References: <1508255864.5659.3.camel@twc.com> <2094438.bITRq4LixK@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <2094438.bITRq4LixK@ralph.baldwin.cx> 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 15:01:58 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 displays > > 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 the 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 gener= ate > cg checksums when creating the initial filesystem. Glen, do you know whi= ch > tool (makefs or something else?) is used to generate the UFS filesystem > in VM images for snapshots? (In this case it appears to be a .vmdk image) >=20 mkimg(1) is used. Glen --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEVVuz/A7vpH93hEhKuWzd6q+LXtAFAlnnbOMACgkQuWzd6q+L XtD9qRAAv9VBnhGZ5bTf7Xd6qKVz8gaUAmd2CN3OY0wuiJpwKJj7uWsYF2+neAzt 2EiTZK7aofOd8O7U24Rf/NgMbHgqWJZFtJsnh0xTg+RBC142bazUd7p00r3gpL2A 46RVvrdaw23zrTsfvSiI0i0PnvrQ2Rgb+U6/0r8gbmTlrQF1WyLDp5CRPYN3r+ST hgWn5oOqrDT1Bd1iv6oSdWPh7UxwtwuVb1wjcvWLad1LezyGzRC9KGzkblskLU8c BjO0vrtlNOH0JbuQMB8+kjUkwIqx8oEBI7UPpMhjIijmEcmN6uHzEkvO0Q6MGb4E N+FVXzFofWEGmdVV9qUZyGyci78Sj6c2Fbj5momknDc5U3bcCAsGdFv5BQIekIJY eWQusRzNUYwoEhuyV46S6pflu69J8qNNMRe2q7WMQ1NPrJ/5XPgw7Wf8G5xdDzIH ojMh8HIXvg0upS1phelr23WDTHWNw0Y/HwHJHM5/zFDE3Vcf4rXd2c9zhEPDHjxq T21+nrB6+ARyypdtvv2fh40DLBiy3IJAbKT1JoYi+pcZ2egsBiZcmtYu87LNlA2/ Gr0wPP1m1JQ1t1geDAJjnJges7zOCU/nfWDjQGesVWWjjTvGI2zSpsDm2GWmQd59 zqfd9gNLSpPw46rpzyUKSdto/y8CZtEPpAhd+RdPtCKx+FK1MK8= =0CDW -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--