From owner-freebsd-current@freebsd.org Wed Oct 18 22:30:38 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 0FE5EE45755 for ; Wed, 18 Oct 2017 22:30:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C83256C7F0; Wed, 18 Oct 2017 22:30:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id EDB6410A8C0; Wed, 18 Oct 2017 18:30:29 -0400 (EDT) From: John Baldwin To: Glen Barber Cc: freebsd-current@freebsd.org, David Boyd , "mckusick@mckusick.com" Subject: Re: VM images for 12.0-CURRENT showing checksum failed messages Date: Wed, 18 Oct 2017 09:49:16 -0700 Message-ID: <3514274.MTfVLsneXj@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20171018164022.GT55623@FreeBSD.org> References: <1508255864.5659.3.camel@twc.com> <1740653.LGy8gQVNSR@ralph.baldwin.cx> <20171018164022.GT55623@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 18 Oct 2017 18:30:30 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean 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 22:30:38 -0000 On Wednesday, October 18, 2017 04:40:22 PM 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 displays > > > > > many checksum failed messages when booted. (see attachment). > > > > > > > > > > I think this started about 20170925. > > > > > > > > > > I have VirtualBox VM's running 10.4-STABLE, 11.1-STABLE and 12.0- > > > > > CURRENT. > > > > > > > > > > Only the 12.0-CURRENT image exhibits this behavior. > > > > > > > > > > This is easily fixed by "fsck -y /" in single-user mode during the boot > > > > > process. > > > > > > > > > > I can test any updates at almost any time. > > > > > > > > I wonder if the tool creating the snapshot images wasn't updated to generate > > > > cg checksums when creating the initial filesystem. Glen, do you know which > > > > 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) > > > > > > > > > > mkimg(1) is used. > > > > Does makefs generate the UFS image fed into mkimg or does mkimg generate the > > UFS partition itself? > > > > Sorry, I may have understated a bit. > > First, mdconfig(8) is used to create a md(4)-backed disk, onto which > newfs(8) is run, followed by the installworld/installkernel targets. > > Next, mkimg(1) is used to feed the resultant md(4)-based .img > filesystem (after umount(8)) to create the final output image. Hmm, so I suspect you are using an older kernel, but I wonder if you are also using an older newfs or a newer newfs? If the newfs is the same as as the running kernel, then this means that upgrading from a pre-cg-sum kernel to a cg-sum kernel will have similar issues. -- John Baldwin