#120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size
------------------------------+--------------------
Reporter: pwnall | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Future
Component: Cloud Base Image | Keywords:
------------------------------+--------------------
Copied from RHBZ #1260800, based on responses seen on other bugs related
to the Vagrant image.
Description of problem:
The Vagrant image for Fedora 22 cloud does not extend the filesystem to
fill up the entire disk.
Version-Release number of selected component (if applicable):
https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86...
/Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-virtualbox.box
How reproducible:
Always
Steps to Reproduce:
1. Set up a new Vagrant box using the Fedora 22 cloud base box.
2. vagrant ssh
3. Inspect the partition table.
Actual results:
[vagrant@localhost ~]$ sudo fdisk -l /dev/sda
Disk /dev/sda: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe02b2711
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 6146047 6144000 3G 83 Linux
Expected results:
I'd expect to see the filesystem grown to fill the virtual disk.
Additional info:
This is a serious obstacle to deploying Fedora Cloud for me. I need to be
able to test things out in a Vagrant box before pushing things out to
production. The 3G filesystem makes it impossible for me to load
everything I need into the VM.
Please let me know if there is any other information I can provide to help
narrow this down.
--
Ticket URL: <
https://fedorahosted.org/cloud/ticket/120>
cloud <
https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System