AWS Cloud9 - no space left on device

Question

Each time I start a new environment, after a few weeks of work I get /home/ubuntu/.rvm/gems/ruby-2.7.1/gems/rack-2.2.3/lib/rack/server.rb:433:in `close': No space left on device @ fptr_finalize_flush - /home/ubuntu/environment/corsego/tmp/pids/server.pid (Errno::ENOSPC)

So I have to regularly create a new working environment.

My stack that I install : t2.micro (1 GiB RAM + 1 vCPU) , Ubuntu Server 18.04 LTS

How can I just clean up space/unused files?

Cobaltous

Answer 1

You can run this script to resize your EBS volume.

Choe

What if I don't have access to a terminal anymore? (And I resized the volume 2 times already doesn't work) – Hegel

Correct-omundo! – Conjunct

Not working. Using Ubuntu image is giving me this error: ImportError: No module named urllib3 The urlib3 is installed – Iridectomy

Answer 2

I hope the resizing script commented by @Richard H Boyd solves anyone's problems, but I couldn't configure that script according to my environment parameters.

So I recommend resizing EBS volume manually.

1. Go to the Cloud9 Environments page.
2. Select the environment you want to resize and click "View details" button.
3. EC2 Instance >> Go To Instance
4. Select the instance and go to the "Storage" tab. And then click the Volume ID.
5. Select the Volume and click "Actions" button on the top right side. Then select "Modify volume".
6. Resize the volume as your wish. Then refresh the "Volumes" page.
7. After you complete modifying process, go to the "Instances" page again and Reboot the instance.
8. Wait about two minutes and reopen the Cloud9 environment.

After all of these steps, you can use the command below to control:

df -h

This is my output (Because I resized it as 20 GB):

/dev/xvda1       20G  9.5G  9.9G  50% /

Jackdaw

The script works well, but this is also a very valid approach. Recently I've been doing it your approach (via the GUI) more often than via the script – Cobaltous

Although this helped me in increasing the size but same was not reflecting in filesystem. I followed this to solve the issue youtube.com/watch?v=eIR_QprrE40 – Rosellaroselle

Answer 3

I had the same issue. To solve this I delete some files/directories that I no longer needed in Cloud9, then I had the space and I was able to save.

Triboluminescent

This just postpones the problem. In the end you will need to increase disc size – Cobaltous

Yes you are right. Rebooting the instance is a better solution. – Triboluminescent

I found an interesting fact. AWS lets you select 10GB volume but they also instal 8.4GB of data / libraries / lambda docker images so you are left with 1.3GB of usable space. – Eyesight

Once I've wiped out all files and that and worked. However, accessing IDE once again gives the same memory error. – Patency