SSH into the running instance and confirm everything is in order via df -ah.attach the new EBS volume to the EC2 instance ( Important! If this is your root device be sure it to name it exactly as the root device of the instance as it was mentioned e.g (/dev/sda1) or (/dev/xdva1) otherwise it will be attached as a block device and not a root device and you will not be able to start the instance as there will be no root device listed for the instance.).create a new (larger) EBS volume from the created snapshot.create a snapshot of the detached EBS volume.detach the EBS volume from the stopped instance.Most of the outlined steps can be performed via the AWS Management Console as well, which avoids dealing with the Amazon EC2 API Tools this boils down to: If you properly prepare the steps he describes (I highly recommend to test them with a throw away EC2 instance first to get acquainted with the procedure, or automate it via a tailored script even), you should be able to finish the process with a few minutes downtime only indeed. Larger copy, without needing to start a new instance. Minutes), it is possible to change out the root EBS volume with a The process is outlined in Eric Hammond's excellent article Resizing the Root Disk on a Running EBS Boot EC2 Instance:Īs long as you are ok with a little down time on the EC2 instance (few This snapshot features enables you to solve your problem in turn, insofar you can replace your current 8GB EBS root storage (/dev/xvda1) with one more or less as large as you desire. data put there is reasonably safe and survives instance failures you can increase flexibility and durability even further by taking regular snapshots of your EBS volume, which are stored on Amazon S3, featuring the well known 99.999999999% durability. This is the so called Root Device Storage of your Amazon EBS-backed EC2 instance, which facilitates Amazon EBS for flexibility and durability in particular, i.e. Solution: resize /dev/xvda1 (/) to gain desired storage Of course you might store huge indexes there for example, but must be prepared to rebuild these after the storage has been cleared for whatever reason (instance reboot, hardware failure. only put temporary data there you can afford to lose or rebuild easily, like a swap file or strictly temporary data in use during computations. In particular, this ephemeral storage will be lost on stop/start cycles and can generally go away, so you definitely don't want to put anything of lasting value there, i.e. This is the so called ephemeral storage of your Amazon EC2 instance and its characteristics are vastly different than the of the persistent Amazon EBS storage in use elsewhere. Workaround: use /dev/xvdb (/mnt) for temporary data Please suggest me the possible solution for this.Is it possible to use the same /dev/xvdb partition with another instance. Is there a way i can allocate some diskspace to / from /dev/xvdb or Any other Ways. Now i am getting i have enough disk space in /dev/xvdb. This Instance type is m1.large with 8GB EBS. Removed all unnecessary files from server.īut Still I am not getting enough space.Now i have Tried these thing for getting some extra space on / partition df -ah say this Filesystem Size Used Avail Use% Mounted on I am running Ubuntu 11.04 instance for my Web Server on AWS cloud, now i am getting there is no disk space in / partition of my server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |