Hello,

When resizing the Droplet, the block device is increased when the resize uses the CPU, Memory and Disk option. In most cases, the next boot will detect this within the software running on the Droplet and kick off some steps to update this.

This can fail however at 100% disk usage ( as some space is still required for temporary files ) or when the particular release of software installed on the Droplet doesn’t accomplish this. The platform isn’t able to determine this however, as we limit the access to the partition/data of the Droplet. You can however address this after clearing up sufficient space to operate with these steps:

1. Check current filesystem size of /dev/vda1:
   lsblk

2. If you see the block device is larger than the partition, you will need to grow the primary partition of your Droplet:
   growpart /dev/vda 1

3. Grow the filesystem on the partition:
   resize2fs /dev/vda1

4. Re-check the filesystem size to ensure it is filling the disk:

df -h

You should now be fully utilizing the space.

Please let us know if you have any additional questions, and have a wonderful day!

Cheers,
Sri Charan