From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] genext2fs: couldn't allocate a block (no free space)
Date: Sat, 07 Jan 2012 20:36:04 +0100 [thread overview]
Message-ID: <87zkdzgva3.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAOrAeonTZC0dXZnNLLfTjrcZHyiTGHRUWcKDO06mz3MOT0Y7CQ@mail.gmail.com> (vbr vbr's message of "Fri, 6 Jan 2012 10:39:42 -0800")
>>>>> "vbr" == vbr vbr <vvvg77@gmail.com> writes:
vbr> Hi,
vbr> I am using buildroot 2011.11 with x86_64 and hitting this issue after enabling
vbr> valgrind which made my target fatter:
vbr> genext2fs: couldn't allocate a block (no free space)
vbr> I made this change to work around this issue increasing the number
vbr> of BLOCKS, but it's probably not the right thing to do:
40% is probably a bit extreme. Out of interest, how many blocks did it
estimate before, and how many did you need?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-01-07 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 18:39 [Buildroot] genext2fs: couldn't allocate a block (no free space) vbr vbr
2012-01-07 19:36 ` Peter Korsgaard [this message]
2012-01-09 22:25 ` vbr vbr
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=87zkdzgva3.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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