Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Oct 2017 16:40:22 +0000
From:      Glen Barber <gjb@FreeBSD.org>
To:        John Baldwin <jhb@freebsd.org>
Cc:        freebsd-current@freebsd.org, David Boyd <David.Boyd49@twc.com>, "mckusick@mckusick.com" <mckusick@mckusick.com>
Subject:   Re: VM images for 12.0-CURRENT showing checksum failed messages
Message-ID:  <20171018164022.GT55623@FreeBSD.org>
In-Reply-To: <1740653.LGy8gQVNSR@ralph.baldwin.cx>
References:  <1508255864.5659.3.camel@twc.com> <2094438.bITRq4LixK@ralph.baldwin.cx> <20171018150155.GA28174@FreeBSD.org> <1740653.LGy8gQVNSR@ralph.baldwin.cx>

next in thread | previous in thread | raw e-mail | index | archive | help

--MI2pJyvBeFc4alSb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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).
> > > >=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 g=
enerate
> > > cg checksums when creating the initial filesystem.  Glen, do you know=
 which
> > > tool (makefs or something else?) is used to generate the UFS filesyst=
em
> > > in VM images for snapshots?  (In this case it appears to be a .vmdk i=
mage)
> > >=20
> >=20
> > mkimg(1) is used.
>=20
> Does makefs generate the UFS image fed into mkimg or does mkimg generate =
the
> UFS partition itself?
>=20

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 <format>.img
filesystem (after umount(8)) to create the final output image.

Glen


--MI2pJyvBeFc4alSb
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEVVuz/A7vpH93hEhKuWzd6q+LXtAFAlnng/EACgkQuWzd6q+L
XtCr6w/+N42fm6CoKraq7ZNN2M7jx5/zNLg8PxU097IPSu+9wTr3ZXdb1iroVBF6
qr5sag/c48jvJjv/t16Ffsr2jGDaDZhNMnEImq9TqkEXCE0wVhfpAWlRwqXItNpn
pZpVS0dXFbSUaMnLb1t/0S3I+4mIE0LaEK1rZP4vgr7A71jmbx/usL3S3+BHwSHo
8vpjEzT+TcJ0fx8Uq/fBVUjXl03INmRysssrfWXH2aShf3DdzOrC5i1+uyRoOofd
2cppFHM9YEdq3QjNa4u9H08ZZcG20Gow3ezrueDSdvp6atvU8r+36zakfnQJ/PJ6
8LlkgIORKUk4LdxM4s29Dy1ScTXWs2EsYfg/wPXU3HvCqiOJAixn3EyCs5Exqr6M
XUdF2ZCa1rgZ8qPjPrMtc4tjWkRJnG8cdEQwyH3UnWz4jR/YOsXDSi6+g+uHIt4N
r8PYp+cFaagKjONMbTDhn85BMg/s/wleHYgNNr9Quq3WDWwoTVonVj5YrwBHkrkW
JQHt3cu5CelV0mgl5sbPM8FYq6xrRDLVdORKX93UL1DcgrSUS1ofxuH5zyeqeBQH
jt3QYA0HQuMs404NpHsy0kFzbwcW5kHnx00VMyVfLBDCcpyPO1GYok4hs0vy9cjM
2P0XjxO199LSpX6tu3/Fh9d4NH6we27rx4e/wR3KqQfiYQlysI8=
=XV86
-----END PGP SIGNATURE-----

--MI2pJyvBeFc4alSb--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171018164022.GT55623>