CentOS 6 (x86_64) - with Updates HVM
CentOS.org | 2002_01Linux/Unix, CentOS 6 - 64-bit Amazon Machine Image (AMI)
Don't Use This AMI
This AMI can not be resized. As with the other reviews this NEEDS to be addressed. What can you do with a 8GB drive?
- Leave a Comment |
- Mark review as helpful
Root partition resize
The AMI needs to be updated so that the root partition could be resized in automated way (even if needs to go through a reboot).
Can't mount root device on another instance
Sometimes I need to extend the root partition, so I try mount root device on another instance, but it fails. I hope to improve this part in the future.
Root partition has only 8GB
This image is good, with a minimal installation. But it's impossible to increase root partition..
xvda 202:0 0 18G 0 disk
└─xvda1 202:1 0 8G 0 part /
Still some major unsolved issues.
- root login only out of the box - this can be fixed, but it's more foot work for every users.
- Still very, very difficult to resize root partition. This is very painful, the only practical workaround is fix this partitioning situation manually and keep those large AMIs ($$$). CentOS on HVM is the only linux OS I am aware of that insists on partitioning the root partition like this when the root partition is resized (to 100G in this case):
root@ip-172-31-20-225 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 100G 0 disk
└─xvda1 202:1 0 8G 0 part /
This makes nearly impossible to automate the deployment of those images on a larger root partition. The disturbing thing is that this is done right with the Paravirtual CentOS AMIs and root partitions can be resized at instance launch time and adjusted with simply running 'resize2fs'. This is maddening for those of us that cannot live with a default 8G root partition because we run software that insists very hard on using more space there.
Hope this can be addressed eventually.