Issue with Cloudmin disk size on creation for KVM - apparently since updating to latest version

Submitted by cruiskeen on Thu, 08/27/2015 - 11:40

I'm seeing an odd behavior in Cloudmin that I THINK must have occurred after updating to 8.3. Cloudmin is running on a CentOS 6.7 server and host systems are a mix of CentOS 6.7 and 7.1.

When I create a KVM system now, no matter what size I tell it to create for the disk, it just creates the disk at the size in the image. It SAYS it's expanding the disk while creating the system, but it finishes immediately and just goes on, apparently doing nothing.

After the VPS is created I can go in and change the disk size - that works fine. It just won't expand the disk while creating the system. This is annoying but not crucial in our workflow. This appears to happen on creating either 6.7 or 7.1 VPS's. It looks like it's completely consistent.

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Thu, 08/27/2015 - 22:51

It sounds like just the filesystem isn't being expanded - if you check at Resources -> Manage Disks after creation, does it show the correct size?

Submitted by cruiskeen on Sun, 08/30/2015 - 16:04

Sorry it took me so long to get back to you on this - yes, indeed that's what's happening -- the LVM volume expands, but the file system does not.

The volume is the right size but the file system has not grown.

Submitted by JamieCameron on Sun, 08/30/2015 - 16:29

Do you get any error message during creation of the VM, in particular at the stage where it is expanding the disk?

Submitted by cruiskeen on Sun, 08/30/2015 - 18:24

No error message - just moves along perfectly happily and looks like everything worked fine

Submitted by JamieCameron on Sun, 08/30/2015 - 19:22

Which filesystem are you using on the VM (like ext3 or ext4)? It's possible that if the VM uses ext4 but the host system is old enough that it doesn't support that filesystem type, you could see this problem.

Submitted by cruiskeen on Mon, 08/31/2015 - 11:38

Well, I thought about that, but this USED to work fine on the same systems. I'm trying to build with either ext3 or ext4. Thing is, I can after the fact go into cloudmin and change the file system size just fine - it works to change it later, but it doesn't expand the file system while initially provisioning the VPS. All of the systems are set up to use ext3 or ext4 (and of course the CentOS 7 systems know about XFS as well but I'm not using XFS for the root file system - just for add-ons).

Submitted by JamieCameron on Mon, 08/31/2015 - 21:56

Can you post the full output that you get from Cloudmin when creating a new VM with an expanded disk?

Submitted by cruiskeen on Thu, 09/10/2015 - 17:08

Hi -- sorry for dropping this - I'm currently on vacation. I'll be back in the office some time next week and will pick this up again then

Submitted by cruiskeen on Tue, 09/22/2015 - 11:18

Creating virtual system with KVM .. .. creation started with IP 69.4.98.221. Waiting for creation to complete ............................................ .. creation has completed successfully.

Creating swap file of 4 GB .. .. done

Removing missing disks from fstab file .. .. done

Expanding filesystem to 20 GB .. .. done

Mounting new instance's filesystem .. .. mounted on /mnt/kvm-virtualtest.cloudmin.cruiskeenconsulting.com

Setting root password .. .. done

Adding extra authorized SSH keys .. .. done

Updating configuration files with hostname and IP address .. .. done

Updating network configuration files .. .. done

Adding additional network configuration files .. .. done

Modifying /etc/fstab file .. .. already done

Allowing SSH logins by root .. .. already allowed

Setting SSH server port .. .. done

Un-mounting instance's filesystem .. .. done

Adding DNS entry virtualtest.cloudmin.cruiskeenconsulting.com. for IP address 69.4.98.221 .. .. done

Starting up new KVM instance .. .. done

Regenerating SSH host keys .. .. done

Setting password for existing Webmin install .. .. password changed successfully.

Opening firewall ports for Webmin .. .. done

Waiting for Webmin to start .. .. started successfully

Fetching current status ..

Note that although it SAYS it's expanding the disk it appears that what is happening is that it expands the logical volume, but not the file system.

Submitted by JamieCameron on Tue, 09/22/2015 - 23:04

That's odd - Virtualmin thinks it was able to resize OK, but clearly it didn't actually work.

If you shut down the VM and go to Resources -> Manage Disks, click on the first disk, and expand the size to say 22 GB, does it work OK?

Submitted by cruiskeen on Sat, 09/26/2015 - 17:10

Yes --- I can always expand the filesystem by hand after the creation - so it's mainly just annoying at the moment.

Submitted by JamieCameron on Sat, 09/26/2015 - 18:43

Any chance I can login to your Cloudmin system to debug this? Because it can't be re-produced on any of our test systems..

Submitted by cruiskeen on Thu, 10/01/2015 - 12:56

As mentioned in the other tickets - all my Cloudmin issues now seem to be gone. Even this one. I'm closing it.