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

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

[vbr vbr]

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)
@@ -29,7 +29,7 @@
     # 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 -- $@ -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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120106/b278b444/attachment.html>

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

[Peter Korsgaard]

>>>>> "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

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

[vbr vbr]

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@uclibc.org> wrote:

> >>>>> "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 part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120109/4595f7eb/attachment.html>