| Summary: | No enough disk space with qemu sato images | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Yi Zhao <yi.zhao> |
| Component: | meta-yocto | Assignee: | Edwin Zhai <edwin.zhai> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | dvhart, elizabeth.flanagan, jiajun.xu, liang.li2, liangliang.wang, poky.bs.watcher, poky.watcher, sgw, shane.wang, wenhuax.fan, yi.zhao |
| Version: | unspecified | ||
| Target Milestone: | 1.1 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Yi Zhao
2011-06-16 01:02:39 UTC
The same issue also occurs on qemumips-sato image. Image location: http://autobuilder.yoctoproject.org/nightly/20110613-1/ Tree/Branch: Poky/master Commit: e5f3cc34df74c08c8cab3e1cf9207fafaec6cb9a the same issues on qemuppc sato images from nightly build 20110613-1: http://autobuilder.pokylinux.org/nightly/20110613-1/machines/qemu/qemuppc/ free space when boot the sato images: root@qemuppc:/var/lib/rpm# df -h Filesystem Size Used Available Use% Mounted on /dev/root 158.1M 133.7M 16.4M 89% / tmpfs 40.0K 0 40.0K 0% /mnt/.psplash none 251.1M 80.0K 251.0M 0% /dev tmpfs 251.1M 64.0K 251.0M 0% /var/volatile tmpfs 251.1M 0 251.1M 0% /media/ram and no such issues on qemuppc sato images from nightly build 20110527-1 http://autobuilder.pokylinux.org/nightly/20110527-1/: free space when boot the sato images: oot@qemuppc:~# df -h Filesystem Size Used Available Use% Mounted on /dev/root 269.0M 223.9M 31.5M 88% / tmpfs 40.0K 0 40.0K 0% /mnt/.psplash none 60.7M 76.0K 60.6M 0% /dev tmpfs 60.7M 64.0K 60.6M 0% /var/volatile tmpfs 60.7M 0 60.7M 0% /media/ram root@qemuppc:~# Saul, is this just a result of the updated image sizing mechanism? This bug also exist in qemux86 sato image. Edwin will expand the qemu image size by changing the parameter of bitbake. We need discuss the policy to do that first to avoid objections from the community, i.e., how many percents of image size should be increased? Image size is tunable via some parameter when building. Pls. see meta/conf/bitbake.conf: image_size = rootfs * IMAGE_OVERHEAD_FACTOR(default 1.3) + IMAGE_ROOTFS_EXTRA_SPACE Issue here is that end user's requirement are different depends on their own needs. Some of them probably want to run oracle in disk image, but yocto disk image is hard to support it. Yi, What's the requirement from your daily test? Saul can give comments, so we can enlarge some factor to meet the requirement. BTW, another option is to make and add another free disk image by yourself if the test allow files from another disk. Thanks, Edwin (In reply to comment #6) > Image size is tunable via some parameter when building. Pls. see > meta/conf/bitbake.conf: > > image_size = rootfs * IMAGE_OVERHEAD_FACTOR(default 1.3) + > IMAGE_ROOTFS_EXTRA_SPACE > > Issue here is that end user's requirement are different depends on their own > needs. Some of them probably want to run oracle in disk image, but yocto disk > image is hard to support it. > > Yi, > What's the requirement from your daily test? Saul can give comments, so we can > enlarge some factor to meet the requirement. > > BTW, another option is to make and add another free disk image by yourself if > the test allow files from another disk. > > Thanks, > Edwin There are some zypper test cases in my weekly testing. I need to install/remove 4 packages by using zypper. I re-test with 20110625 build, when boot up the sato image at first time: ################### root@qemuarm:~# df -h Filesystem Size Used Available Use% Mounted on /dev/root 145.5M 120.6M 17.5M 87% / devtmpfs 60.2M 108.0K 60.1M 0% /dev tmpfs 40.0K 0 40.0K 0% /mnt/.psplash none 60.2M 108.0K 60.1M 0% /dev tmpfs 60.2M 64.0K 60.2M 0% /var/volatile tmpfs 60.2M 0 60.2M 0% /media/ram root@qemuarm:~# root@qemuarm:~# du /var/lib/rpm/ -sh 3.4M /var/lib/rpm/ ################### When I add a zypper repo, rpm will initialize some db file and create a log file, these files will cost about 10MB space. ################### root@qemuarm:~# zypper ar http://192.168.7.1/rpmrepo rpmrepo Adding repository 'rpmrepo' [done] Repository 'rpmrepo' successfully added Enabled: Yes Autorefresh: No URI: http://192.168.7.1/rpmrepo root@qemuarm:/var/lib# df -h Filesystem Size Used Available Use% Mounted on /dev/root 145.5M 129.8M 8.2M 94% / devtmpfs 60.2M 108.0K 60.1M 0% /dev tmpfs 40.0K 0 40.0K 0% /mnt/.psplash none 60.2M 108.0K 60.1M 0% /dev tmpfs 60.2M 236.0K 60.0M 0% /var/volatile tmpfs 60.2M 0 60.2M 0% /media/ram root@qemuarm:~# du /var/lib/rpm/ -sh 12.7M /var/lib/rpm/ #################### Then I install the first package: ################### root@qemuarm:~# zypper in man Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: man 1 new package to install. Overall download size: 125.0 KiB. After the operation, additional 246.0 KiB will be used. Continue? [y/n/?] (y): y Retrieving package man-1.6f-r0.armv5te (1/1), 125.0 KiB (246.0 KiB unpacked) Retrieving: man-1.6f-r0.armv5te.rpm [done] Installing: man-1.6f-r0 [done] root@qemuarm:~# df -h Filesystem Size Used Available Use% Mounted on /dev/root 145.5M 132.8M 5.3M 96% / devtmpfs 60.2M 108.0K 60.1M 0% /dev tmpfs 40.0K 0 40.0K 0% /mnt/.psplash none 60.2M 108.0K 60.1M 0% /dev tmpfs 60.2M 2.6M 57.6M 4% /var/volatile tmpfs 60.2M 0 60.2M 0% /media/ram root@qemuarm:~# du /var/lib/rpm/ -sh 15.3M /var/lib/rpm/ ###################### You can see the 'man' package only uses 125KB + 246KB space. But the rpm db file will increase about 3MB. Then I install the second package, the free space is not enough: ####################### root@qemuarm:~# zypper in mc Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: mc ncurses-terminfo 2 new packages to install. Overall download size: 1.4 MiB. After the operation, additional 4.3 MiB will be used. Continue? [y/n/?] (y): y Retrieving package ncurses-terminfo-5.7-r1.armv5te (1/2), 529.0 KiB (1.6 MiB unpacked) Retrieving: ncurses-terminfo-5.7-r1.armv5te.rpm [done] Retrieving package mc-4.7.5-r0.armv5te (2/2), 927.0 KiB (2.7 MiB unpacked) Retrieving: mc-4.7.5-r0.armv5te.rpm [done] Installing: ncurses-terminfo-5.7-r1 [done] Installing: mc-4.7.5-r0 [error] Installation of mc-4.7.5-r0 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: Install/Erase problems: installing package mc-4.7.5-r0.armv5te needs 3MB on the / filesystem Abort, retry, ignore? [a/r/i] (a): ######################### For a large rootfs, for example, sato-sdk image has 80MB free space. When rpm db file has initialized. There is still enough space to install other packages. However, for a small rootfs, only less than 20MB free space, and the rpm db file will use more than 10MB. It is difficult to install other packages. So I think for a small rootfs, in order to complete the testing, 30MB space is required. And this issue maybe relate with bug 1174. Hi Saul, I remember that you will ask Beth to increase IMAGE_ROOTFS_EXTRA_SPACE on autobuilder. So there is no other fixing required for the bug, right? Verified it with 20110708 build Now there is enough space to complete the testing. Image location: http://autobuilder.yoctoproject.org/nightly/20110708-1/ Tree/Branch: Poky/1.1_M2 Poky Commit: 9f4eaeef33da5595748253d59d95c7ca548e28fa |