Red Hat Bugzilla – Bug 1260800
Fedora 22 Cloud vagrant image does not extend filesystem to disk size
Last modified: 2015-09-08 02:08:16 EDT
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):
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.
[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
I'd expect to see the filesystem grown to fill the virtual disk.
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.
I also filed this on the Cloud SIG Trac.
This is based on the trail in the bug below, which also concerns the cloud base vagrant image.
Redirect 1: https://fedorahosted.org/rel-eng/ticket/6192
(In reply to Victor Costan from comment #1)
> I also filed this on the Cloud SIG Trac.
Thanks. That is the right place. This tracker is just for Vagrant package issues.