From owner-freebsd-current@freebsd.org Wed Oct 18 14:49:06 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 800A3E3AE9B for ; Wed, 18 Oct 2017 14:49:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (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 5F45E80579; Wed, 18 Oct 2017 14:49:06 +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 03F2A10AB01; Wed, 18 Oct 2017 10:49:05 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: David Boyd , "mckusick@mckusick.com" , "gjb@freebsd.org" Subject: Re: VM images for 12.0-CURRENT showing checksum failed messages Date: Wed, 18 Oct 2017 07:49 -0700 Message-ID: <2094438.bITRq4LixK@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <1508255864.5659.3.camel@twc.com> References: <1508255864.5659.3.camel@twc.com> 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 10:49:05 -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 14:49:06 -0000 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) -- John Baldwin