Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Oct 2022 20:01:44 +0000
From:      Glen Barber <gjb@freebsd.org>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>, Warner Losh <imp@bsdimp.com>
Subject:   Re: Snapshot stable/13-n252734-56533712694 first boot "gpart: arg0 'ufs/rootfs': Invalid argument"; also, an alignment question . . .
Message-ID:  <20221017200144.GK30607@FreeBSD.org>
In-Reply-To: <3DA3BC90-D234-4B37-9125-E7A70F16DD08@yahoo.com>
References:  <3DA3BC90-D234-4B37-9125-E7A70F16DD08.ref@yahoo.com> <3DA3BC90-D234-4B37-9125-E7A70F16DD08@yahoo.com>

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

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

On Mon, Oct 17, 2022 at 12:30:40PM -0700, Mark Millard wrote:
> [While the example is an aarch64 context, the issue should be
> more general.]
>=20
>=20
> Issue #0:
>=20
> After dd'ing:
>=20
> FreeBSD-13.1-STABLE-arm64-aarch64-RPI-20221014-56533712694-252734.img
>=20
> to the USB3 media booting got a notice:
>=20
> gpart: arg0 'ufs/rootfs': Invalid argument
>=20
> Showing some context:
>=20
> . . .
> Setting hostuuid: 30303031-3030-3030-3265-373238346338.
> Setting hostid: 0xd2f9b0de.
> Starting file system checks:
> /dev/ufs/rootfs: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/ufs/rootfs: clean, 498385 free (1281 frags, 62138 blocks, 0.1% fragm=
entation)
> Growing root partition to fill device
> random: randomdev_wait_until_seeded unblock wait
> random: randomdev_wait_until_seeded unblock wait
> random: unblocking device.
> GEOM_PART: da0s2 was automatically resized.
>   Use `gpart commit da0s2` to save changes or `gpart undo da0s2` to rever=
t them.
> da0s2 resized
> da0s2a resized
> gpart: arg0 'ufs/rootfs': Invalid argument
> super-block backups (for fsck_ffs -b #) at:
> . . .=20
>=20
> It looks like the line in question in /etc/rc.d/growfs is:
>=20
>         gpart commit "$rootdev"
>=20
> where the prior code:
>=20
>         FSTYPE=3D$(mount -p | awk '{ if ( $2 =3D=3D "/") { print $3 }}')
>         FSDEV=3D$(mount -p | awk '{ if ( $2 =3D=3D "/") { print $1 }}')
>         case "$FSTYPE" in
>         ufs)
>                 rootdev=3D${FSDEV#/dev/}
>                 ;;
>=20
> assigned rootdev based on:
>=20
> For FSTYPE:
> # mount -p | awk '{ if ( $2 =3D=3D "/") { print $3 }}'
> ufs
>=20
> For FSDEV:
> # mount -p | awk '{ if ( $2 =3D=3D "/") { print $1 }}'
> /dev/ufs/rootfs
>=20
> So: ufs/rootfs
>=20
> I'd guess that the problem is that after the gpart resize -i . . .
> activities the label ufs/rootfs is no longer effective for
> gpart (until the growfs -y completes?).
>=20
> Whatever the cause, gpart is rejecting the ufs/rootfs
> notation.
>=20
>=20
>=20
> Issue #1 (unsure of the intent, so checking):
>=20
> # gpart show
> =3D>       63  468862065  da0  MBR  (224G)
>          63       1985       - free -  (993K)
>        2048     102400    1  fat32lba  [active]  (50M)
>      104448  468757680    2  freebsd  (224G)
>=20
> =3D>        0  468757680  da0s2  BSD  (224G)
>           0        128         - free -  (64K)
>         128  468757552      1  freebsd-ufs  (224G)
>=20
> Reviewing the alignments (one is differently
> aligned than the others):
>=20
> The first is good:
>=20
>        2048     102400    1  fat32lba  [active]  (50M)
>=20
> aligns to 512*2048 =3D=3D 1 MiByte.
>=20
> The second is likely good:
>=20
>      104448  468757680    2  freebsd  (224G)
>=20
> aligns to 512*104448 =3D=3D 51 MiByte, so a 1 MiByte multiple
> as the alignment.
>=20
> But the 3rd is less aligned (the freebsd-ufs line):
>=20
>      104448  468757680    2  freebsd  (224G)
>=20
> =3D>        0  468757680  da0s2  BSD  (224G)
>           0        128         - free -  (64K)
>         128  468757552      1  freebsd-ufs  (224G)
>=20
> aligns to 512*104448 + 512*128 but 512*128 is a
> 64 KiByte offset, so: 51 MiByte + 64 KiByte.
>=20
> This is not 1 MiByte aligned but is 64 KiByte aligned.
> Is that the intended alignment for the freebsd-ufs
> area?
>=20

I am going to have to defer to our resident experts on this, to be
honest.

Glen


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

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

iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmNNtKEACgkQAxRYpUeP
4pNyuA//Yi4U4DaanQ+Cy0bjokWq4bTuWiElYWemOVE99ybgI7rF5s4mfwHc9Ut6
IN5t/WygnZqn6bUYzR/J2JBcbvFPmHeHxKEWZhcXj87OlOmnd1BVRgnKRoOlzgc/
zzmiL/LS1BjZ5VL1fQtUH21SaI5A+LDbW5t7PiwfGTDisROXo+N66mIM8XZeV3jM
QP7mOC4fkOKXBQIVz7wgCK99jti8RCWZn+Vw6/nks/OJmP/AzYXOKagYZug4bjBa
QUPZBRb6XHyIXmDT/m+A6hD3C9niPtfcqpvrGePf73MylMj7UCmKNhF+xc6Xm9Wa
Ox4Qu3WcxmCFBrQ55xsdOn2BVD+QwGPH0yLVwEvGoof1oSWy2R0VpjGz5G/76iYD
YN+CPC18wr/mxwnYegqH4qHeNY4KMcI62TxgT0VpRyuvw0wJkTPam/s5kW57MthF
hATlf0guQAnhiXUfy7gOHado8BRvizVHDbB+sn8JK9chGJstg5moUXs2Q8RjyMPb
Fpt/N4fPeg/cYzsrs3DC8U58D/vXNR5Cz0/TjuFxlJqR8ltGFXUA/XorEB6ogcZE
RC5nv+ZSN6W6zOn1grTY/5aqBufZLxSqDeTvo89DVpzEFvDhUozfpZCJm4MLbqaG
r11L9FThWGEoCH8yQwaQktmyffb8RETW+ddoMxPZsFnBzzeTTGw=
=wX0q
-----END PGP SIGNATURE-----

--94oXV8jP6EZ84voN--



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