Re: git: 1dfcff294e44 - main - release: increase IMAGE_SIZE for arm, arm64, riscv

On Wed, Jul 13, 2022 at 08:13:27PM +0000, Glen Barber wrote:
> On Wed, Jul 13, 2022 at 12:06:55PM -0700, Mark Millard wrote:
> > Glen Barber <gjb_at_FreeBSD.org> wrote on
> > Date: Wed, 13 Jul 2022 18:37:34 UTC :
> > 
> > > The branch main has been updated by gjb:
> > > 
> > > URL: https://cgit.FreeBSD.org/src/commit/?id=1dfcff294e44d4b45813288ef4095c36abb22f0e
> > > 
> > > commit 1dfcff294e44d4b45813288ef4095c36abb22f0e
> > > Author:     Glen Barber <gjb@FreeBSD.org>
> > > AuthorDate: 2022-07-13 18:36:22 +0000
> > > Commit:     Glen Barber <gjb@FreeBSD.org>
> > > CommitDate: 2022-07-13 18:36:22 +0000
> > > 
> > >     release: increase IMAGE_SIZE for arm, arm64, riscv
> > >     
> > >     Related to:     PR 264032
> > >     MFC after:      5 minutes
> > >     Sponsored by:   Rubicon Communications, LLC ("Netgate")
> > 
> > I may have some evidence that, for example,
> > 
> > http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220708-a0b956f5ac5-256605.img.xz
> > 
> > and:
> > 
> > http://ftp3.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/13.1/FreeBSD-13.1-RELEASE-arm-armv6-RPI-B.img.xz
> > 
> > were not built fully via the /usr/src/release procedures
> > using modern builds of mdconfig and such. The below is
> > taken from a different list exchange.
> > 
> > QUOTE
> > I tried what it looks to me the /usr/src/release/
> > code would do initially for arm64/RPI.conf (but with
> > my file naming and an explicit -u0 style of use):
> > 
> > # truncate -s3072m mmjnk.test
> > # mdconfig -u0 -fmmjnk.test -x63 -y255
> > # gpart create -sMBR md0
> > md0 created
> > # gpart show md0
> > =>     63  6291393  md0  MBR  (3.0G)
> >       63  6291393       - free -  (3.0G)
> > # gpart add -t'!12' -a512k -s50m -b1m md0
> > md0s1 added
> > # gpart show md0
> > =>     63  6291393  md0  MBR  (3.0G)
> >       63     1985       - free -  (993K)
> >     2048   102400    1  fat32lba  (50M)
> >   104448  6187008       - free -  (3.0G)
> > 
> > I tried the same sequence in a chroot into a 13.0-RELEASE-p11
> > tree on an aarch64 main [so: 14] machine. I got the same result.
> > 
> > But such is not what the 13.1-RELEASE build produced, for
> > example:
> > 
> > # mdconfig -u0 -fFreeBSD-13.1-RELEASE-arm64-aarch64-RPI.img -x63 -y255
> > # gpart show md0
> > =>     63  6291393  md0  MBR  (3.0G)
> >       63     2016       - free -  (1.0M)
> >     2079   102312    1  fat32lba  [active]  (50M)
> >   104391  6187041    2  freebsd  (3.0G)
> >  6291432       24       - free -  (12K)
> > 
> > (There are no 13.1-STABLE snapshots available to download
> > and look at.)
> > 
> > Looking at the recent 14.0-CURRENT snapshot:
> > 
> > # mdconfig -u0 -fFreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220708-a0b956f5ac5-256605.img -x63 -y255
> > # gpart show md0
> > =>     63  6291393  md0  MBR  (3.0G)
> >       63     2016       - free -  (1.0M)
> >     2079   102312    1  fat32lba  [active]  (50M)
> >   104391  6187041    2  freebsd  (3.0G)
> >  6291432       24       - free -  (12K)
> > 
> > So, also not matching.
> > END QUOTE
> > 
> 
> There are no local configurations on the builders that would produce
> differing output.  Why, though, are you specifying '-x' and '-y' to
> mdconfig?  I think that may be obfuscating something when attaching the
> image as an md(4) device.
> 

Also, if you haven't already seen it, PR 264032 suggests there may be
a bug, notably this comment:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264032#c17

I forgot to include this in my reply.

Glen