Bug 231 - Meet error message prompt when extracting qemu root fs
Summary: Meet error message prompt when extracting qemu root fs
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium minor
Target Milestone: 0.9 M4
Assignee: Mark Hatle
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-08-25 20:33 UTC by liping Ke
Modified: 2010-12-21 06:09 UTC (History)
9 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description liping Ke 2010-08-25 20:33:48 UTC
when we running poky-extract-sdk<poky-sdk-tarball>
<extract-dir>, we met below error:
lke@lke-nhm:/media/contrib/contrib.git/build_new$ poky-extract-sdk
tmp/deploy/images/poky-image-sdk-qemux86.tar.bz2
/home/lke/unfs/kernels/ Extracting rootfs tarball using pseudo...
/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/pseudo -P 
/opt/poky/sysroots/i586-pokysdk-linux/usr tar -C 
"/home/lke/unfs/kernels/" -xjf 
"tmp/deploy/images/poky-image-sdk-qemux86.tar.bz2" tar:
./dev/initctl: Cannot mkfifo: Invalid argument tar: Exiting with 
failure status due to previous errors SDK image successfully extracted 
to /home/lke/unfs/kernels/ 

And also Paste Scott's comment below
Yes, I saw this too - it is due to an error when tar is extracting a FIFO (something like /dev/initctl if I'm remembering correctly). File a minor bug on this, it may be that pseudo can't handle FIFOs.
Comment 1 Mark Hatle 2010-09-08 09:11:27 UTC
pseudo is supposed to handle fifos.  So this should not be a problem.

Can you look at /home/lke/unfs/kernels/ and tell me what filesystem that mount point is using?  There are some filesystem types that do not support fifos.  If you happen to be using one this could trigger that error.
Comment 2 Mark Hatle 2010-09-08 10:15:00 UTC
Confirmed with the pseudo author this is a defect in pseudo.
Comment 3 Mark Hatle 2010-09-08 10:21:10 UTC
Upstream is working on a fix....
Comment 4 Mark Hatle 2010-09-09 08:14:19 UTC
I am unable to run the command: poky-extract-sdk
tmp/deploy/images/poky-image-sdk-qemux86.tar.bz2

What is the configure, commands and steps to generate the poky-image-sdk-qemux86.tar.bz2 file?

I have tried simply running bitbake poky-image-sdk, and I get a .hdimage file, not a tar.bz2.
Comment 5 Mark Hatle 2010-09-09 12:48:22 UTC
Fixed in upstream commit:

e3765ee9c9c2bccaa32fbe6426d4eb1bbcd214e7

Pull request for the fix will be submitted soon.
Comment 6 Mark Hatle 2010-09-10 07:44:13 UTC
Fix has been checked in...
Comment 7 liping Ke 2010-09-11 18:57:41 UTC
Hi, Mark
Did not see the e3765ee9c9c2bccaa32fbe6426d4eb1bbcd214e7 on the poky/master tree. Is this the commit number of contrib master?

I still meet this error with poky/master last Friday tree. I will verify the latest cs on Monday. When verified, I will change status to verified.

Thanks,
criping
Comment 8 liping Ke 2010-09-19 22:58:39 UTC
Verified this bug has been fixed with latest tip of master.
(cs: d1ff9aa4f, Sep 16, RP).