Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Is there a way to automatically detect the minimum required BR2_TARGET_ROOTFS_EXT2_SIZE?
Date: Sat, 10 Mar 2018 21:58:41 +0100	[thread overview]
Message-ID: <20180310205841.GA2097@scaer> (raw)
In-Reply-To: <CAFXrp_exNc=GtVqbuRmYqKiDNXgD+pawnCSmRH-1FrF2dxXgLQ@mail.gmail.com>

Ciro, All,

On 2018-03-10 16:14 +0000, Ciro Santilli spake thusly:
> https://stackoverflow.com/questions/49211241/is-there-a-way-to-automatically-detect-the-minimum-required-br2-target-rootfs-ex
> 
> I'm when making a big non-embedded image, I keep hitting the error:
> 
>     *** Maybe you need to increase the filesystem size
> (BR2_TARGET_ROOTFS_EXT2_SIZE)
> 
> and then I have to do a `du` on `output/target` to find out how big I
> have to make `BR2_TARGET_ROOTFS_EXT2_SIZE`.
> 
> Is there a way to automate this, or a decent workaround?

No, becaaue it is not reliable, see commit:

    c6bca8cef fs/ext2: Remove support for auto-calculation of rootfs size

In the end, it does nto make sense to do auto-calculation, because on an
embedded device, you have to now the layout and size of your storage.
So, you know what size you want your ext filesystem to be.

Regards,
Yann E. MORIN.

> Some workarounds I'm considering:
> 
> * put the big stuff under 9p:
> https://superuser.com/questions/628169/how-to-share-a-directory-with-the-host-without-networking-in-qemu
> * use CPIO and `-initrd`
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-03-10 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-10 16:14 [Buildroot] Is there a way to automatically detect the minimum required BR2_TARGET_ROOTFS_EXT2_SIZE? Ciro Santilli
2018-03-10 20:58 ` Yann E. MORIN [this message]
2018-03-11  9:57   ` Ciro Santilli
2018-03-12 17:24     ` Trent Piepho

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=20180310205841.GA2097@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox