[LRUG] [devops] enlarge root volume on existing ec2 instance

[Viktor Trón]

Thanks to both of you.

I followed the steps used in Fred's excellent ref
http://alestic.com/2010/02/ec2-resize-running-ebs-root
It is using ec2 command line tools so geekproof.
FYI: you no longer need to run the resize2fs command on your instance, it
is automatically grown for you (at least on my ubuntu 12.04)

If you cringe at the command line but like clicking, the same process can
be done via the aws web console demonstrated in the well-suited medium of a
screencast here: http://alestic.com/2010/02/ec2-resize-running-ebs-root




On Fri, Jul 19, 2013 at 12:35 PM, Frederick Cheung <
frederick.cheung at gmail.com> wrote:

>
> On 19 Jul 2013, at 12:32, Viktor Trón <viktor.tron at gmail.com> wrote:
>
> > slightly off topic, but encouraged by recent devops wisdom.
> >
> > We need to have bigger disk on an existing ec2 instance.
> >
> > One approach even reading about gives me headache
> >
> http://stackoverflow.com/questions/550790/growing-amazon-ebs-volume-sizes
> > the accepted answer is from 2009 and lots of controversy.
> >
> > Another approach that might work is to turn off the instance (stop not
> terminate), create an AMI image from it then relaunch with a larger disk.
> >
>
> You can't change an EBS volume's size: you need to snapshot it and create
> a new volume from the snapshot. Once that's done you need to resize the
> filesystem. Whether that can be done on the root volume depends on the
> filesystem (i think recentish file systems like ext4 are fine). Eric
> Hammond has a walkthrough of this here:
> http://alestic.com/2010/02/ec2-resize-running-ebs-root
>
> Fred
>
> > any guidance appreciated.
> > Vik
> > _______________________________________________
> > Chat mailing list
> > Chat at lists.lrug.org
> > http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130720/5a16e874/attachment-0003.html>