Loving OpenShift, but having more than the three projects that already cost more than I earn from them I run an OpenShift Origin Virtual Machine on my home server.
So today I was trying to get Uptime running on OpenShift via uptime-openshift. A truly wonderful way of installing applications, except that it didn’t go so well:
$ rhc app create uptime nodejs-0.10 mongodb-2.4 --from-code=//github.com/rkmallik/uptime-openshift Application Options ------------------- Domain: origin Cartridges: nodejs-0.10, mongodb-2.4 Source Code: //github.com/rkmallik/uptime-openshift Gear Size: default Scaling: no Creating application 'uptime' ... The server did not respond correctly. This may be an issue with the server configuration or with your connection to the server (such as a Web proxy or firewall). Please verify that you can access the OpenShift server //172.16.3.3/broker/rest/domain/origin/applications
Or…
$ rhc app create uptime nodejs-0.10 mongodb-2.4 --from-code=//github.com/rkmallik/uptime-openshift Application Options ------------------- Domain: origin Cartridges: nodejs-0.10, mongodb-2.4 Source Code: //github.com/rkmallik/uptime-openshift Gear Size: default Scaling: no Creating application 'uptime' ... Unpacking premade journal tar: journal/prealloc.1: Wrote only 2048 of 10240 bytes tar: Exiting with failure status due to previous errors
What’s going on? It turns out I was running low on disk space. The virtual machine image was only 8 GB and there was too little disk space left when the Mongo cartridge wanted to install the pre-allocated journals!
So, time to enlarge the disk! In short, the steps I took were:
- Convert virtual machine disk image to .vdi format
- Enlarge .vdi disk image
- Add partition with new disk space
- Add new partition to LVM volume group
- Extend LVM logical volume
- Resize file system
Now, let’s dive into the details!
Convert virtual machine disk image to .vdi format
Shutdown the virtual machine first!
As the VirtualBox user on the hypervisor, in the directory for the virtual machine:
$ VBoxManage clonehd origin-vm.vmdk origin-vm.vdi --format VDI 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Clone hard disk created in format 'VDI'. UUID: 646d9ed4-c751-45a3-9f08-0946e11591c9
Enlarge .vdi disk image
As the VirtualBox user on the hypervisor, in the directory for the virtual machine:
$ VBoxManage modifyhd origin-vm.vdi --resize 81920 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Enlarge it with as much as you want to allow the disk image to grow on the hypervisor! The unit is megabytes.
Now detach the .vmdk file and attach the .vdi file from the virtual machine. I did this with phpVirtualBox, so the corresponding command line is left as an exercise for the reader.
Delete the the .vmdk file, or keep it as backup if you like.
Add partition with new disk space
Start the virtual machine and login. Default root password is changeme. Being a Linux user for about 15 years, I’m no stranger to fdisk:
# fdisk /dev/sda
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sector
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 3
First sector (16777216-167772159, default 16777216):
Using default value 16777216
Last sector, +sectors or +size{K,M,G} (16777216-167772159, default 167772159):
Using default value 167772159
Command (m for help): t
Partition number (1-4): 3
Hex code (type L to list codes): 8e
Changed system type of partition 3 to 8e (Linux LVM)
Command (m for help): p
Disk /dev/sda: 85.9 GB, 85899345920 bytes
255 heads, 63 sectors/track, 10443 cylinders, total 167772160 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
Disk identifier: 0x0003c6cc
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1026047 512000 83 Linux
/dev/sda2 1026048 16777215 7875584 8e Linux LVM
/dev/sda3 16777216 167772159 75497472 8e Linux LVM
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
If told to reboot, do that. Otherwise Linux will not show the new partition.
Add new partition to LVM volume group
# vgextend vg_broker /dev/sda3 No physical volume label read from /dev/sda3 Physical volume /dev/sda3 not found Physical volume "/dev/sda3" successfully created Volume group "vg_broker" successfully extended
Extend LVM logical volume
Use all available space:
# lvextend -l +100%FREE /dev/mapper/vg_broker-lv_root Extending logical volume lv_root to 78,71 GiB Logical volume lv_root successfully resized
Resize file system
First find out the LSize in sectors:
# lvs --units s LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lv_root vg_broker -wi-ao---- 165060608S lv_swap vg_broker -wi-ao---- 1671168S
Second, resize the file system. Change capital S to lower-case:
# resize2fs /dev/mapper/vg_broker-lv_root 165060608s resize2fs 1.41.12 (17-May-2010) Filesystem at /dev/mapper/vg_broker-lv_root is mounted on /; on-line resizing required old desc_blocks = 1, new_desc_blocks = 5 Performing an on-line resize of /dev/mapper/vg_broker-lv_root to 20632576 (4k) blocks. The filesystem on /dev/mapper/vg_broker-lv_root is now 20632576 blocks long.
Done!
If only I remembered why I needed more disk space?!