Hi Imran, you are talking about 3 different levels here to reach your goal of resizing a volume. First level is the volume itself. This is what you can do within CS. After that you need to extend the partition and then you need to expand the filesystem. The last to levels you need to do within the os of the server.
What we do is using cloud-init within our template to automate this. But our templates do not use LVM. Our templates are checking at boot if the root volume has been extended and expanding the partition and the filesystem. If you want to know more about it, I can give you more details. Mit freundlichen Grüßen / With kind regards, Swen Brüseke -----Ursprüngliche Nachricht----- Von: Imran Ahmed [mailto:[email protected]] Gesendet: Donnerstag, 3. August 2017 12:00 An: [email protected] Betreff: Instance with a larger disk size then Template Hi All, I am creating an instance with a 300GB disk from a CentOS 7 template that has 5GB disk (LVM Based). The issue is that the root LVM partition inside the new VM instance still shows 5GB . The device size (/dev/vda) however shows 300GB. The question is what is the best strategy to resize the root LVM partition so that I could use all 300G. Kind regards, Imran - proIO GmbH - Geschäftsführer: Swen Brüseke Sitz der Gesellschaft: Frankfurt am Main USt-IdNr. DE 267 075 918 Registergericht: Frankfurt am Main - HRB 86239 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
