New: genext2fs: couldn't allocate a block (no free space)
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
Signature · 3 lines
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.
[Buildroot] [Bug 2929] genext2fs: couldn't allocate a block (no free space)
https://bugs.busybox.net/show_bug.cgi?id=2929
Peter Korsgaard <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED--- Comment #1 from Peter Korsgaard <[email protected]> --- Hi,
I've implemented better ext2 size estimation in git (eeea3ea6a88a8) - Could you give it a try?
Signature · 3 lines
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.
[Buildroot] [Bug 2929] genext2fs: couldn't allocate a block (no free space)
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=2929
Sean Mathews <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |mathewss at nutech.com
Resolution|FIXED |--- Comment #2 from Sean Mathews <[email protected]> 2012-07-07 03:36:58 UTC ---
genext2fs presumes block sizes are 1024 but genext2fs.sh looks at the total
blocks on the local file system where the block size may be different. In my case it was 4096 so this error shows up still in this case.
Signature · 3 lines
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.
[Buildroot] [Bug 2929] genext2fs: couldn't allocate a block (no free space)
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=2929
Yann E. MORIN <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
CC| |yann.morin.1998 at free.fr
Resolution| |INVALID--- Comment #3 from Yann E. MORIN <[email protected]> 2013-05-26 14:21:11 UTC --- Sean,
Estimating the number of blocks is done with a call to: 'du -k' where '-k' means 'assume 1KiB blocks' (see: man du). So your issue is probably /slightly/ different.
If you manage to reproduce this issue, please reopen this bug and report back with a bit more information: buildroot's .config file, host file system...
Regards,
Yann E. MORIN.
Signature · 3 lines
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.