vbr vbr | 6 Jan 19:39 2012
Picon

genext2fs: couldn't allocate a block (no free space)

Hi,

I am using buildroot 2011.11 with x86_64 and hitting this issue after enabling valgrind which made my target fatter:
genext2fs: couldn't allocate a block (no free space)

I made this change to work around this issue increasing the number of BLOCKS, but it's probably not the right thing to do:

Index: fs/ext2/genext2fs.sh
===================================================================
--- fs/ext2/genext2fs.sh        (revision 92473)
+++ fs/ext2/genext2fs.sh        (working copy)
<at> <at> -29,7 +29,7 <at> <at>
     # size ~= superblock, block+inode bitmaps, inodes (8 per block), blocks
     # we scale inodes / blocks with 10% to compensate for bitmaps size + slack
     BLOCKS=$(du -s -c -k $TARGET_DIR | grep total | sed -e "s/total//")
-    BLOCKS=$(expr 500 + \( $BLOCKS + $INODES / 8 \) \* 11 / 10)
+    BLOCKS=$(expr 500 + \( $BLOCKS + $INODES / 8 \) \* 14 / 10)
     set -- $ <at> -b $BLOCKS
 fi

I also searched in the mailing list history and found a similar thread but no conclusion seemed to have emerged.
Any advice?

Thanks
Vincent

_______________________________________________
buildroot mailing list
buildroot@...
http://lists.busybox.net/mailman/listinfo/buildroot
Peter Korsgaard | 7 Jan 20:36 2012

Re: genext2fs: couldn't allocate a block (no free space)

>>>>> "vbr" == vbr vbr <vvvg77@...> 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
vbr vbr | 9 Jan 23:25 2012
Picon

Re: genext2fs: couldn't allocate a block (no free space)

INODES=1010
BLOCKS=98925
genext2fs: couldn't allocate a block (no free space)

Tried incrementing gradually from 11 and ended up at 14.

Thanks
Vincent


On Sat, Jan 7, 2012 at 11:36 AM, Peter Korsgaard <jacmet-2zL2ArBv0bUdnm+yROfE0A@public.gmane.org> wrote:
>>>>> "vbr" == vbr vbr <vvvg77 <at> 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

_______________________________________________
buildroot mailing list
buildroot@...
http://lists.busybox.net/mailman/listinfo/buildroot

Gmane