Bug 138

Summary: qemumips poky-image-sato/sdk fail to boot
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Jiajun Xu <jiajun.xu>
Component: meta-yoctoAssignee: Kevin Tian <kevin.tian>
Status: VERIFIED FIXED QA Contact:
Severity: critical    
Priority: High CC: kevin.tian, liping.ke, poky.bs.watcher, poky.watcher, richard.purdie, sgw, susie.li, yongkang.you
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: mips   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---
Attachments:
Description Flags
qemumips poky-image-sato/sdk fail to boot none

Description Jiajun Xu 2010-07-22 07:44:58 UTC
Created attachment 20 [details]
qemumips poky-image-sato/sdk fail to boot

Testing Env:    
Host: Ubuntu 10.04 LTS
Kernel: 2.6.32-21-generic-pae
Poky gitinfo(used to build qemu-native):
0c3b1aa0a5461c9b5f3833feb091f7c8a459ca9b (git://git.pokylinux.org/poky.git)
all the images from weekly build (20100721) on autobuilder,
http://yoctobuild01.jf.intel.com/build-areas/weekly-release/build/build/tmp/deploy/images/.

With the qemumips poky-image-sato/sdk images from weekly builds 20100721, they fail to boot up with "No space" error.

Pls. see attachment.
Comment 1 Kevin Tian 2010-07-26 20:04:25 UTC
this perhaps due to inode limitation, but busybox 'df' doesn't report that information now... need more work to confirm
Comment 2 Kevin Tian 2010-07-26 20:46:39 UTC
this does come from inode limitation:

(sato pre boot)
Inode count:              6864
Block count:              270308
Reserved block count:     13515
Free blocks:              70938
Free inodes:              33

(sato after boot)
Inode count:              6864
Block count:              270308
Reserved block count:     13515
Free blocks:              69909
Free inodes:              0

Since free inode is empty now, "no space on device" error appears. SDK image has more available inodes:
(sdk)
Inode count:              17608
Block count:              581092
Reserved block count:     29054
Free blocks:              55675
Free inodes:              263

But it still suffers from potential "no space" risk soon. Actually I also checked no MIPS image generated at Jul.10, which looks more reasonable:
(07/10 sato)
Inode count:              28672
Block count:              229377
Reserved block count:     2049
Free blocks:              20559
Free inodes:              21816

It looks over 20,000 inodes are missing in current images. Even current x86 image has similar lackage risk:
(x86)
Inode count:              6216
Block count:              296704
Reserved block count:     14835
Free blocks:              59231
Free inodes:              153

Appears that the reason is it. I'll find appropriate fix soon
Comment 3 Kevin Tian 2010-07-26 21:31:58 UTC
it appears that this relates to recent genext2fs upgrade...
Comment 4 Kevin Tian 2010-07-27 00:12:40 UTC
I've sent out a fix to poky mailing list for this bug
Comment 5 Jiajun Xu 2010-07-27 05:49:22 UTC
Kevin,
I think a bug can be marked as FIXED only after the fixing patch is picked in tree and built in weekly/milestone build. 

BTW, for the inode bug, I think you may need to ask Saul put it into M2 brunch if we want it fixed in M2.
Comment 6 Saul Wold 2010-07-28 01:31:33 UTC
This has been integrated into the M2 branch
Comment 7 Jiajun Xu 2010-07-29 01:03:14 UTC
Verified with M2-20100728 build, the bug is fixed.
Comment 8 Dexuan Cui 2010-08-03 23:49:21 UTC
*** Bug 130 has been marked as a duplicate of this bug. ***