4:31 p.m.
#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
10:08 a.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jpeeler):
This seems to be the same as https://fedorahosted.org/cloud/ticket/109
While I'm commenting I'll go ahead and add that the version of vagrant-
libvirt in Fedora 22 doesn't have the "machine_virtual_size", which I
would consider to be part of the full solution. (I believe 0.0.30 has it.)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:1>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
1:26 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jpeeler):
I was wrong, vagrant-libvirt 0.0.31 was just tagged, which contains the
machine_virtual_size option.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:2>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2:58 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by dustymabe):
hey jpeeler.. so it sounds like with F23 everything will working. Do you
agree? If so I'll go ahead and close this.
In the mean time do you have steps to workaround this? This works:
growpart --dry-run /dev/vda 1 && growpart /dev/vda 1 && resize2fs
/dev/vda1
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:3>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
3:59 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jpeeler):
As long as vagrant-libvirt gets rebased the first part of the problem will
be solved. But I considered this ticket to include automatic resizing of
the image rather than doing manually as you indicated. I personally was
more interested in the atomic image, but both are important. Here's what
I've been doing for the centos atomic image:
config.vm.provision :shell, inline: <<-SHELL
growpart /dev/vda 2
pvresize /dev/vda2
lvresize -l +100%FREE /dev/atomicos/docker-pool
SHELL
I suspect usage of cloud-init is the key to automating, but the centos
atomic image doesn't have cloud-init (fedora does though it seems, hrm).
Finally, there are instructions to add a new disk
(http://www.projectatomic.io/docs/quickstart/), but I prefer to just
resize as that is a lot more automatable.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:4>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
6:05 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jasonbrooks):
Replying to [comment:4 jpeeler]:
I suspect usage of cloud-init is the key to automating, but the centos
atomic
image doesn't have cloud-init (fedora does though it seems, hrm).
Finally, there are instructions to add a new disk
(http://www.projectatomic.io/docs/quickstart/), but I prefer to just
resize as that is a lot more automatable.
jpeeler, centos atomic has cloud-init.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:5>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
6:13 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jpeeler):
Ah good! You're right - I checked the wrong image. I'm sure cloud-init can
be used here to do this somehow, right?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:6>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
6:50 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jasonbrooks):
I'm sure it could:
http://cloudinit.readthedocs.org/en/latest/topics/examples.html -- there
are ways to run arbitrary commands in there.
I've been using the add a second disk method, with a vagrantfile like
this: https://gist.github.com/jasonbrooks/b84117ada0ec1f7dab61, although,
that one is for plain centos, and includes some lines not needed for
atomic.
I'd like to see us have an automatically resizing base disk, though, w/
something like this new vagrant-libvirt option.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:7>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
11:02 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by dustymabe):
I'm not sure I understand.. You shouldn't have to use cloud-init at all.
The images from F22 Cloud base vagrant image was broken because the root
fs didn't extend to the full 40G. The F23 cloud base vagrant image has
been fixed so that it will use the whole 40G by default. You won't need to
extend the partition/fs at all unless 40G isn't enough.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:8>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
4 p.m.
#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 | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by jpeeler):
Cloud-init usage allows automatic dynamic resizing and might be the best
option to allow vagrant to nicely mirror what happens with most cloud
images. The F22 vagrant image wasn't technically broken, it was just small
at 3G. I would say that the situation with a static 40G image is only
slightly better now, because if somebody wants a smaller image they'll
have to umount the filesystem since (I think) online resizing only works
for growing the size. And again, if somebody wants something larger than
40GB they'll have to resize the filesystems/partitions themselves as well.
Hope that's clear - the whole point is to properly utilize the newly
available "machine_virtual_size" option in vagrant-libvirt.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:9>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2:16 a.m.
New subject: [cloud] #120: Fedora 22 Cloud vagrant image does not extend
filesystem to disk size
#120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size
------------------------------+---------------------
Reporter: pwnall | Owner:
Type: defect | Status: closed
Priority: normal | Milestone: Future
Component: Cloud Base Image | Resolution: fixed
Keywords: |
------------------------------+---------------------
Changes (by kushal):
* status: new => closed
* resolution: => fixed
Comment:
Closing this ticket as part of trac clean up process. If you want to
reopen, please reopen it after we move to pagure.io as atomic-wg.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/120#comment:10>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2757
days inactive
3159
days old
10 comments
1 participants
participants (1)
-
Fedora Cloud Trac Tickets