From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2929] New: genext2fs: couldn't allocate a block (no free space)
Date: Fri, 10 Dec 2010 09:28:03 +0000 (UTC) [thread overview]
Message-ID: <bug-2929-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2929
Summary: genext2fs: couldn't allocate a block (no free space)
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: andyg1001 at hotmail.co.uk
CC: buildroot at uclibc.org
Estimated Hours: 0.0
fs/ext2/genext2fs.sh is incorrectly calculating the size required to create an
ext2 image file, and it seems to happen when the size of the image exceeds
500Mb (but I haven't done precise testing to determine this).
This is the command genext2fs.sh is using:
genext2fs -d /home/test/buildroot-2010.11/target -U
/home/test/buildroot-2010.11/images/rootfs.ext2 -b 525096 -N 5242
du on the target directory returns 508712
find | wc -l in the target directory returns 4842
Modifying the call to genext2fs with -b 529712 (i.e. 508712+21000) makes an
image without errors and e2fsck rootfs.ext2 tells me "4440/5720 files,
529506/529712 blocks", so it should be possible to create the image with 529506
blocks, but 21000 seems a good enough "guess".
Does this information help? If you need further information or testing, let me
know.
Thanks
Andy
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-12-10 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 9:28 bugzilla at busybox.net [this message]
2010-12-30 22:35 ` [Buildroot] [Bug 2929] genext2fs: couldn't allocate a block (no free space) bugzilla at busybox.net
2012-07-07 3:36 ` bugzilla at busybox.net
2013-05-26 14:22 ` bugzilla at busybox.net
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=bug-2929-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.