Bug 743 - [UNFS] rootfs parse incorrectly if *-image-* is given
Summary: [UNFS] rootfs parse incorrectly if *-image-* is given
Status: VERIFIED FIXED
Alias: None
Product: ADT
Classification: Yocto Project Subprojects
Component: kernel analysis (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: High major
Target Milestone: 1.0 M4
Assignee: Scott Garman
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-02-20 20:55 UTC by Jiajun Xu
Modified: 2011-03-16 08:21 UTC (History)
8 users (show)

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

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 Jiajun Xu 2011-02-20 20:55:57 UTC 
Testing Env:    
Host: Ubuntu 10.04 LTS
Kernel: 2.6.32-21-generic-pae
commit information: 0a8f4f45b66ad5d51dea91a406a17555252dfe42

If I use a folder name including "-image-" for UNFS rootfs, poky-qemu will be confused and generate a wrong name for rootfs. It causes poky-export-rootfs failure.

Check following log, the rootfs folder I use is "/home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/", but poky-qemu change it to "/home/jxu49/osel/poky-weekly/build/tmp/deploy/images//home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/-qemux86-64.nfs".
############
jxu49@vt-nhm4:~/osel/poky-weekly/build$ poky-qemu nfs /home/jxu49/osel/poky-weekly/build/tmp/deploy/images/bzImage-2.6.37+git1+5a32d7fe3b817868ebb697d2d883d743903685ae_1+343c06b25b221aa7f7019aee83b2d976041fddce-r15-qemux86-64-20110213053156.bin /home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/
Set MACHINE to [qemux86-64] based on kernel [/home/jxu49/osel/poky-weekly/build/tmp/deploy/images/bzImage-2.6.37+git1+5a32d7fe3b817868ebb697d2d883d743903685ae_1+343c06b25b221aa7f7019aee83b2d976041fddce-r15-qemux86-64-20110213053156.bin]
Assuming /home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/ really means /home/jxu49/osel/poky-weekly/build/tmp/deploy/images//home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/-qemux86-64.nfs

Continuing with the following parameters:
KERNEL: [/home/jxu49/osel/poky-weekly/build/tmp/deploy/images/bzImage-2.6.37+git1+5a32d7fe3b817868ebb697d2d883d743903685ae_1+343c06b25b221aa7f7019aee83b2d976041fddce-r15-qemux86-64-20110213053156.bin]
ROOTFS: [/home/jxu49/osel/poky-weekly/build/tmp/deploy/images//home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/-qemux86-64.nfs]
FSTYPE: [nfs]
Acquiring lockfile for tap0...
Using preconfigured tap device 'tap0'
poky-export-rootfs restart /home/jxu49/osel/poky-weekly/build/tmp/deploy/images//home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/-qemux86-64.nfs
Error: '/home/jxu49/osel/poky-weekly/build/tmp/deploy/images//home/jxu49/osel/poky-weekly/build/tmp/work/qemux86-64-poky-linux/poky-image-sato-sdk-1.0-r0/qemuimagetest/tmp/rootfs/-qemux86-64.nfs' does not exist
Usage: /home/jxu49/osel/poky-weekly/scripts/poky-export-rootfs {start|stop|restart} <nfs-export-dir>
Releasing lockfile of preconfigured tap device 'tap0'
############
Comment 2 Jiajun Xu 2011-03-15 08:52:36 UTC 
Verify the bug with commit information a33a2cc024f9c9147c92c5da70d8fbb631b968f9, which is RC3 build. The bug is fixed.