Bug 5957 - Image not correctly created if 'ptest-pkgs' is in IMAGE_FEATURES
Summary: Image not correctly created if 'ptest-pkgs' is in IMAGE_FEATURES
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.6 M5
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-03-13 05:37 UTC by Chen Qi
Modified: 2014-03-24 01:26 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chen Qi 2014-03-13 05:37:36 UTC 
How to reproduce?
1. Add 'ptest-pkgs' to EXTRA_IMAGE_FEATURES in local.conf
2. bitbake core-image-minimal
3. Either trying to start the image or loop mounting it for examination would reveal the bug.

The odd thing is, if 'ptest-pkgs' is not in IMAGE_FEATURES, everything would be fine.

//Chen Qi
Comment 1 Paul Eggleton 2014-03-13 10:49:35 UTC 
I can't quite figure out from this report - what is the actual failure observed?
Comment 2 Saul Wold 2014-03-13 14:47:40 UTC 
Can you please provide more information
Comment 3 Chen Qi 2014-03-14 01:28:02 UTC 
The image cannot correctly start up. A lot of files are missing, including the whole /etc directory.

//Chen Qi
Comment 4 Robert Yang 2014-03-19 08:42:50 UTC 
This is because there is no inode left, we can change EXTRA_IMAGECMD_ext2 ?= "-i 8192" to "-i 4096" to fix it, or use a higher IMAGE_OVERHEAD_FACTOR.

Another problem is that there is no error information in the log.do_rootfs, there are error messages when I manually run the mke2fs commands.