2010-12-02 06:10:42     couldn't allocate a block (no free space)

Document created by Aaronwu Employee on Aug 23, 2013
Version 1Show Document
  • View in full screen mode

2010-12-02 06:10:42     couldn't allocate a block (no free space)

Aymen Abdelwahed (TUNISIA)

Message: 96403   

 

Hi!!

 

I started getting the following message when rebuilding uClinux (Just after adding oProfile to the kernel)..

 

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

 

 

 

I tried to resolve the problem by removing oProfile but always the "no free space" error.

 

After than, I tried to control the number of blocks by modifying the "EXT2_BLOCKS" variable located in the Makefile.. (uClinux-dist/AnalogDevices/BF548-EZKIT/) from 16384 to 65536.. But, here my uImage size is 24.37MB :s

 

 

 

  EXT2_BLOCKS = 16384: Generates a free space error

 

  EXT2_BLOCKS =  24576: Generates a free space error

 

  EXT2_BLOCKS = 32768: Generates a free space error

 

  EXT2_BLOCKS = 32768: Generates an geant Kernel Image 24.37MB in size...

 

 

 

What can I do please?? Is there any solution to resolve the problem??

 

- Ayman

 

TranslateQuoteReplyEditDelete

 

 

2010-12-02 06:27:57     Re: couldn't allocate a block (no free space)

Mike Frysinger (UNITED STATES)

Message: 96406   

 

use initramfs instead of an ext2 root

 

also, make sure you dont have large useless files in your rootfs.  please read the FAQ for more info:

  docs.blackfin.uclinux.org/doku.php?id=faq (I get errors about "no free space" when generating EXT2 images)

QuoteReplyEditDelete

 

 

2010-12-02 08:16:58     Re: couldn't allocate a block (no free space)

Aymen Abdelwahed (TUNISIA)

Message: 96409   

 

I'm using uImage.initramfs which is 24MB in size.. The ext2 image size is around the 60MB :s.. (I think that I miss understood you)..

 

I'm trying to remove some non-needed applications from Kernel and initialize the EXT2_BLOCKS variable to 16384..

TranslateQuoteReplyEditDelete

 

 

2010-12-02 08:53:22     Re: couldn't allocate a block (no free space)

Mike Frysinger (UNITED STATES)

Message: 96412   

 

the ext2 filesystem is irrelevant to the kernel size when using initramfs.  if 24MB is too big, you need to go through your romfs and remove things.

 

once again, please refer to the faq (My uImage is too large to burn in my flash)

QuoteReplyEditDelete

 

 

2010-12-02 10:22:03     Re: couldn't allocate a block (no free space)

Aymen Abdelwahed (TUNISIA)

Message: 96415   

 

Thanks Mike.. I resolved the problem by removing the non needed files from the romfs.

 

- Ayman

Attachments

    Outcomes