Hello,
We prepared a new KVM host (CentOS 6.2) that will replace our actual Cloudmin master (CentOS 5.8).
The new master's filesystem is ext4 formated (the old is in ext3).
All new VM's on that host are also ext4 formatted.
No problem to create new VM's and even clone them.
But the problem comes when we try to resize them. We get this message on the Cloudmin Master :
Warning - this disk cannot be safely resized. Cloudmin does not know what type of filesystem this disk contains, and so cannot properly resize it. This is most likely because the disk is not mounted on the virtual system.
Pretty scarry...
I read this thread : http://www.virtualmin.com/node/21609
But the package e2fsprogs progs is installed on CentOS 6.2. And according to the package doc, it provides e4fsprogs :
http://rpm.pbone.net/index.php3/stat/4/idpl/17697200/dir/scientific_linu...
We're really stuck, and we really need to expand some of those VMs.
Any ideas ?
Comments
Submitted by mcordas on Wed, 05/09/2012 - 19:52 Pro Licensee Comment #1
I tried with a test vm to force th FS resizing.
The LVM volume was indeed extended from 2GB to 4GB, but not the filesystem : i booted the VM and the FS is still at 2GB.
Submitted by JamieCameron on Wed, 05/09/2012 - 20:12 Comment #2
That error means that cloudmin couldn't find a command on the host to resize the ext4 filesystem on the VM.
Which Linux distribution and version is the host running?
Submitted by mcordas on Wed, 05/09/2012 - 20:14 Pro Licensee Comment #3
CentOS 6.2, like the VM. The Cloudmin Master is on CentOS 5.8.
Submitted by mcordas on Wed, 05/09/2012 - 20:16 Pro Licensee Comment #4
OK, found the error :
Replaced "UUID=cffe31...." with "/dev/vda1" int the VM's /etc/fstab file.
Now Cloudmin recognized the ext4 filesystem and was able to resize it....
Whew...
Submitted by JamieCameron on Wed, 05/09/2012 - 22:57 Comment #5
Ok, that explains it. Unfortunately when a VM is down, Cloudmin cannot map a UUID= entry in /etc/fstab like that to a partition .. so the expansion of the filesystem cannot be done reliably. That's why our standard images all use device paths like /dev/vda1 instead.
Submitted by mcordas on Thu, 05/10/2012 - 01:53 Pro Licensee Comment #6
OK, I understand.
Too bad Anaconda changed it's fstab policy. I'm sure other Cloudmin users will face the problem.
Thanks !
Submitted by Issues on Thu, 05/24/2012 - 02:18 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.