From: daggs <daggs@gmx.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] configs/odroidc2: increase rootfs size to 124M
Date: Mon, 13 Sep 2021 23:20:42 +0200 [thread overview]
Message-ID: <trinity-87c6f8bc-6a3a-4831-971c-b0f35c4dc794-1631568042596@3c-app-mailcom-bs02> (raw)
In-Reply-To: <20210911194453.GU1053080@scaer>
Greetings Yan,
> Sent: Saturday, September 11, 2021 at 10:44 PM
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> To: "Dagg Stompler" <daggs@gmx.com>
> Cc: buildroot@buildroot.org
> Subject: Re: [Buildroot] [PATCH v2 1/2] configs/odroidc2: increase rootfs size to 124M
>
> Dagg,
>
> On 2021-09-11 19:25 +0300, Dagg Stompler spake thusly:
> > as result of e2fsprogs version bump, the image size required was
> > increased.
> > so to fix it and make sure there is enough size, set BR2_TARGET_ROOTFS_EXT2_SIZE
> > to 124M
>
> So, I was wondering what the reason for the size increase was, so I
> spawned a build in three conditions:
>
> - my server's Ubuntu 16.04
> - my laptop's Ubuntu 21.04
> - a docker Bullseye on my server (so, minus the kernel, a stock Debian
> Bullseye)
>
> In all three cases, the build succeeded with current master. The sice
> of the target/ directory is roughly 40MiB in all three cases, which is
> still far enoiugh from 60MiB that it should not cause any issue.
>
> So, I'm still not sure that the reason is "Debian Bullseye", or that the
> solution is "increase the filesystem size".
>
> Could you please try by aplying this patch to master, and rerun the
> build, and share the error message, please:
>
> diff --git a/fs/ext2/ext2.mk b/fs/ext2/ext2.mk
> index 74c99bd7b1..83c967c9df 100644
> --- a/fs/ext2/ext2.mk
> +++ b/fs/ext2/ext2.mk
> @@ -16,7 +16,7 @@ EXT2_MKFS_OPTS = $(call qstrip,$(BR2_TARGET_ROOTFS_EXT2_MKFS_OPTIONS))
> EXT2_LABEL = $(subst ",,$(BR2_TARGET_ROOTFS_EXT2_LABEL))
> #" Syntax highlighting... :-/ )
>
> -EXT2_OPTS = \
> +EXT2_OPTS = -v \
> -d $(TARGET_DIR) \
> -r $(BR2_TARGET_ROOTFS_EXT2_REV) \
> -N $(BR2_TARGET_ROOTFS_EXT2_INODES) \
>
it doesn't reproduces anymore with latest master
Dagg.
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-09-13 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 16:25 [Buildroot] [PATCH v2 1/2] configs/odroidc2: increase rootfs size to 124M Dagg Stompler
2021-09-11 16:25 ` [Buildroot] [PATCH 2/2] genimae/odroidc2: increase image size to 128M Dagg Stompler
2021-09-11 19:53 ` Yann E. MORIN
2021-09-11 19:44 ` [Buildroot] [PATCH v2 1/2] configs/odroidc2: increase rootfs size to 124M Yann E. MORIN
2021-09-13 21:20 ` daggs [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-87c6f8bc-6a3a-4831-971c-b0f35c4dc794-1631568042596@3c-app-mailcom-bs02 \
--to=daggs@gmx.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.