From owner-freebsd-current@freebsd.org Wed Oct 18 18:07:28 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 BDABAE4078D for ; Wed, 18 Oct 2017 18:07:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F29E64297 for ; Wed, 18 Oct 2017 18:07:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22f.google.com with SMTP id 72so6971437itk.3 for ; Wed, 18 Oct 2017 11:07:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AZi/NELw2DZSRrqVixXwmWK2W1rNnIu6R4NfvPwEGF0=; b=0aR5jStpZf41kR2N05M7zC71B9zJhSGa8tJZE0VNfAvdyz+sW4hvRRSfsIVpCE+x2Q 4IaH/esO8464nyhy57Mui1d+oiHsyazW7Z+LEep/Izm2YKd+8t1TLgklsIZIZ4w1JfWU ZhQ1THMbamW52zOQX8WJ6uhVWmywhqRZJaHikb648V2BKJjlKgNVUxnglv6pvYHC/Ejj bbf2nRH9m8BUjGQ8ykxpnenQsPiuPW11QkC2GlC/U8L/VVSFtvy8Yl5t1+1zg35/cjOk 7UybXCDbomKAhLurA/V3uTnT4qi+Wf0tOPwdzkMGuywoIofC4nmBXskdK0sbdZI20KbM g3PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AZi/NELw2DZSRrqVixXwmWK2W1rNnIu6R4NfvPwEGF0=; b=G5c+/4yMjdwdAZIDadO93x+Wx87YyFZaRUUI/mRALwrhJkWCqOs5qLvOp6Fhug2Mop qanfV/lGQeT23QXHCKZbFSc24vYkyh0IAGRdyYJ2twle77bwvR/uakGzs+heiZeEATSX aFVbYFDtdRF7bLxMPgV/3GJsecpy5zXVCMyMZ86I+OziW/PouLU+71C/xNrDzrFf6WpP RGLAdqDv4cNtEzlqEoqLo7ZHAxbts5ESFxZvDWvBRET3KkJTKL5FSiTLp2dW4MSdjUMD cyryB+RlpNgdEmlXr8o7oJoA9wY8QOT+qfeepKhy24VIcawMqvZu81I/+oIYP9uIsXfl O7UQ== X-Gm-Message-State: AMCzsaUniuu/dMhZHk8Ncw7tXKTHHVxzqVwY8qOyZ+C0OHKaZ9vHWf/K y1V79Q2pCHCNNNuBzLzSgN2XpIYIkcz5eBf1/buvEQ== X-Google-Smtp-Source: ABhQp+QPk5olMLyyHWZpxOevNhB0GEC7pG8DuSez5DJjlu3aR9AEy/wt38AHHP57mjB7FPI3UURxTCAVSeHeA+C4BSs= X-Received: by 10.36.184.5 with SMTP id m5mr11571922ite.69.1508350047749; Wed, 18 Oct 2017 11:07:27 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.57.22 with HTTP; Wed, 18 Oct 2017 11:07:27 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:e17a:e8bd:b0d5:9334] 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> From: Warner Losh Date: Wed, 18 Oct 2017 12:07:27 -0600 X-Google-Sender-Auth: 5c_9dKS_hivfl0-Z_8SZxEN_0ro Message-ID: Subject: Re: VM images for 12.0-CURRENT showing checksum failed messages To: Glen Barber Cc: John Baldwin , FreeBSD Current , David Boyd , "mckusick@mckusick.com" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 18:07:28 -0000 On Wed, Oct 18, 2017 at 10:40 AM, 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. > NanoBSD has moved to using makefs from a tree in the host + metadata information. That avoids the whole mdconfig issue. Might not be a bad idea for the release build if pkg src isn't going to solve that. Warner