I think we chose option 30GB but we still got 8GB hard disk only. Where to change that?

Also after we created the launch can we still change the main hard disk size?

this is the result of df -h

Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1      8.0G  4.3G  3.4G  57% /
udev            288M  8.0K  288M   1% /dev
tmpfs           119M  164K  118M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            296M     0  296M   0% /run/shm
/dev/xvdf        22G   11G   11G  50% /media/newdrive

A way to increase this without creating a new instance will also be appreciated :D

closed as not a real question by EEAA, Shane Madden, Michael Hampton, HopelessN00b, gWaldo Aug 30 '12 at 17:24

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

  • what is the instance type? Did you create a separate EBS volume and attach it? – Chida Aug 30 '12 at 5:50
  • I think I created additional ebs volume and attach it, but I like to keep databases file in default location. – user4951 Aug 30 '12 at 6:10
  • what is your instance type? post your df -h – Chida Aug 30 '12 at 6:53
  • isntance type is ubuntu12. I know it defaults to 8GB. But I want something bigger – user4951 Aug 30 '12 at 8:18
  • See here -- aws.amazon.com/ec2/instance-types I don't think any instance has 8GB storage. So you could be looking at this incorrectly. If you post the df -h from the OS, it will help. – Chida Aug 30 '12 at 9:01

You can change the size of your root disk (provided it is an EBS backed instance) as described here: http://alestic.com/2010/02/ec2-resize-running-ebs-root I would suggest to test this on a throw-away instance first however...

The best (and easiest) option is to give the desired space on instance launch - see the --block-device parameter on the launch call: http://docs.amazonwebservices.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RunInstances.html


Many "out of the box" linux instances from AWS have 8 GB on their primary volumes. When launching the instance, you are givin the option increase the size of the primary volume (for example, increase it to 30 GB).

However, after the instance is launched, the filesystem on your volume is still going to report 8 GB. This is because the volume size was increased, but the filesystem was not. So you need to do this manually, after the fact.

Use resize2fs to resize your filesystem:

resize2fs /dev/sda1
  • The newer Ubuntu images instances from Canonical automatically do resize2fs on startup. So if you start your machine with the 30GB harddisk, you will instantly have the storage available after booting. – j0nes Aug 30 '12 at 13:30
  • What about windows? – user4951 Aug 30 '12 at 17:02
  • I use the newer ubuntu images. I think it's still using 8GB. After launching it, can I change the size? – user4951 Aug 30 '12 at 17:06
  • For Windows, you would go into the Disk Management tool to increase the size of your partition to fill the entire volume. There is also the DISKPART command line tool as well. – Matt Houser Aug 31 '12 at 12:58
  • 3
    resize2fs /dev/xvda1 >> resize2fs 1.42.9 (4-Feb-2014) >> The filesystem is already 26212055 blocks long. Nothing to do! >> What is issue i dont understand – harsh4u Jul 9 '14 at 12:53

Not the answer you're looking for? Browse other questions tagged or ask your own question.