Bug 7132 - wic not respecting --size parameter when file system contents larger than requested size
Summary: wic not respecting --size parameter when file system contents larger than req...
Status: RESOLVED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.8 M4
Assignee: Ed Bartosh
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-01-13 15:17 UTC by Phlip Balister
Modified: 2015-04-04 14:14 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

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 Phlip Balister 2015-01-13 15:17:07 UTC 
So I am working on an image for a 4GB sd card. I want to use the --size parameters on the partitions to control how large the sd card image gets, without it going over a size that can reliably fit on a 4GB SD card (4G is not 4G in SD card space)

After some tests, I tried:

part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4 --size 1


For the root partition. The result was an SD card with a root partition sized based on the contents of the rootfs.

The desired behavior is for wic to exit with an error letting the user know the image will be larger than requested.
Comment 1 Ed Bartosh 2015-04-04 14:14:55 UTC 
This doesn't look like a bug to me as --size option is to specify minimum partition size. Here is the quote from wic kickstart reference explaining that:

  --size: The minimum partition size. Specify an integer value
          such as 500. Multipliers k, M ang G can be used. If
          not specified, the size is in MB.
          You do not need this option if you use --source.

However, adding new command line option to specify maximum partition size does make sense from my point of view. Please, create another bugzilla issue if you still need it.