Bug 2209 - [self-hosted] genext2fs fails to generate rootfs without enough memory
Summary: [self-hosted] genext2fs fails to generate rootfs without enough memory
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: High major
Target Milestone: 1.2 M4
Assignee: Dexuan Cui
QA Contact:
URL:
Whiteboard: (1.2) The fix is already in poky mast...
Depends on:
Blocks:
 
Reported: 2012-03-31 01:25 UTC by Jiajun Xu
Modified: 2012-04-18 08:43 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiajun Xu 2012-03-31 01:25:02 UTC
tree/branch: poky/1.2_M4
commit: da6233ea034f35eff59306fdad31f318c340c359

With 1.2 M4 branch, self-hosted image fails to build out due to system has no enough memory for utility genext2fs. All testing for self-hosted-image is blocked by the failure.

The log is as below:
#########
/home/jxu49/osel/m4/self-hosted/tmp/sysroots/i686-linux/usr/sbin/prelink: /usr/lib/gettext/urlget: Using /lib/ld-linux-x86-64.so.2, not /lib64/ld-linux-x86-64.so.2 as dynamic linker
/home/jxu49/osel/m4/self-hosted/tmp/sysroots/i686-linux/usr/sbin/prelink: /usr/lib/gettext/hostname: Using /lib/ld-linux-x86-64.so.2, not /lib64/ld-linux-x86-64.so.2 as dynamic linker
/home/jxu49/osel/m4/self-hosted/tmp/sysroots/i686-linux/usr/sbin/preERROR: Function failed: do_rootfs (see /home/jxu49/osel/m4/self-hosted/tmp/work/qemux86_64-poky-linux/self-hosted-image-1.0-r6/temp/log.do_rootfs.32564 for further information)
link: /usr/lib/quilt/backup-files: Using /lib/ld-linux-x86-64.so.2, not /lib64/ld-linux-x86-64.so.2 as dynamic linker
Size after prelinking 345524.
genext2fs: not enough memory for filesystem
#########
Comment 1 Dexuan Cui 2012-04-02 06:09:56 UTC
Jiajun,
The below patch should have already fixed the bug
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346

You can re-start to test Build Appliance with the below commit(or a newer commmit):
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2cf38f0d769c8b2d39cccc952846249a1e6cea6b


For BA, at least I think there are 3 known issues:
1) we need Saul's patch to generate a big enough image, or else, bitbake would get a "no disk space available" error during a building;
You can work this around by using an extra big .vmdk file as the build directory.

2) the RUN Qemu functionality of the hob in the guest can't work: looks some packages are missing.

3) you can exit the hob that is automatically run, and run hob manually: during a build, you can notice some error messages printed in the shell terminal of the user builder.
Comment 2 Dexuan Cui 2012-04-05 05:55:27 UTC
(In reply to comment #1)
> Jiajun,
> The below patch should have already fixed the bug
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346
> 
> You can re-start to test Build Appliance with the below commit(or a newer
> commmit):
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2cf38f0d769c8b2d39cccc952846249a1e6cea6b
Jiajun, you can test by using the latest poky master plus a small patch from me:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=dcui/master&id=a8b5a3ed58d2a136867fc55b53443b59557c6459

> 
> For BA, at least I think there are 3 known issues:
> 1) we need Saul's patch to generate a big enough image, or else, bitbake would
> get a "no disk space available" error during a building;
> You can work this around by using an extra big .vmdk file as the build
> directory.
Saul has fixed the issue.

> 2) the RUN Qemu functionality of the hob in the guest can't work: looks some
> packages are missing.
I think this is still an issue.

> 3) you can exit the hob that is automatically run, and run hob manually: during
> a build, you can notice some error messages printed in the shell terminal of
> the user builder.
Looks I can't reproduce this with a newly-built image now.
Comment 3 Dexuan Cui 2012-04-12 01:38:43 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Jiajun,
> > The below patch should have already fixed the bug
> > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346
> > 
> > You can re-start to test Build Appliance with the below commit(or a newer
> > commmit):
> > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2cf38f0d769c8b2d39cccc952846249a1e6cea6b
> Jiajun, you can test by using the latest poky master plus a small patch from
> me:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=dcui/master&id=a8b5a3ed58d2a136867fc55b53443b59557c6459
> 
> > 
> > For BA, at least I think there are 3 known issues:
> > 1) we need Saul's patch to generate a big enough image, or else, bitbake would
> > get a "no disk space available" error during a building;
> > You can work this around by using an extra big .vmdk file as the build
> > directory.
> Saul has fixed the issue.
> 
> > 2) the RUN Qemu functionality of the hob in the guest can't work: looks some
> > packages are missing.
> I think this is still an issue.
> 
This issue(xterm/vte terminal) was fixed by Saul.


---
This bug itself was fixed by
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346


If anybody wants to try it, please use the 1.2_M4 tag that has more other fixes:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=1.2_M4&id=14286fe71e037ce895f01b51ac66a8986100b18f
Comment 4 Jiajun Xu 2012-04-18 08:43:55 UTC
Verify the bug as fixed with master commit 720fe9e371eef16da19df0885188aa0341ad2090.