Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why is extfs filesystem mandatory?
Date: Tue, 7 Sep 2010 16:55:46 +0200	[thread overview]
Message-ID: <20100907165546.06ed2a29@surf> (raw)
In-Reply-To: <4C863CDD.8020805@jdines.net>

Hello,

On Tue, 07 Sep 2010 09:23:41 -0400
"James J. Dines" <jdines@jdines.net> wrote:

> While trying to build a large system I keep getting an error stating
> that there is no room left on the device during the generation of the
> ext2 filesystem.  It is my understanding that this is due to a hard
> upper limit imposed by the genext2fs utility.

Hum, interesting. It is not the first time we have report from people
saying that fairly big filesystems cause failures while generating the
ext2 image. I don't know if it's a genext2fs problem, or if it's our
script that computes the number of inodes and blocks needed that does
something wrong. Would be good if someone could have a look into this.

> This would not be an issue for me if I could simply disable said step,
> however there seems to be no way to disable generation of the ext2
> filesystem in the menuconfig.
> 
> Is there a reason why this cannot be disabled?

make menuconfig
 -> Target filesystem options
   -> disable 'ext2 root filesystem'

Works here. It doesn't work for you ?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-09-07 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 13:23 [Buildroot] Why is extfs filesystem mandatory? James J. Dines
2010-09-07 14:55 ` Thomas Petazzoni [this message]
2010-09-07 16:34   ` James J. Dines
2010-09-07 16:53     ` Quotient Remainder
2010-09-07 17:42       ` James J. Dines
2010-09-07 19:03         ` Thomas Petazzoni

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=20100907165546.06ed2a29@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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