Keywords: General - AWS - Technical issue - Other
bnsupport ID: dfa95335-f62a-10b0-2776-09cf5223e813
Really, I need your help!
My WordPress website, set up with WordPress by Bitnami suddenly became unavailable and it seems was run into full storage. Cause stopping the services and "no space left on device". But this issue has been fixed by removing some files using Filezilla.
After making the website works again, I have tried to increase the instance Volume size, from 10GB to 60GB.
I have modified the Volume as specified here exactly: https://docs.bitnami.com/aws/how-to/modify-ebs-volume
But when I run the command: "lsblk"
this is what I get:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 10G 0 disk
└─xvda1 202:1 0 10G 0 part /
loop0 7:0 0 55.4M 1 loop /snap/core18/1932
loop1 7:1 0 55.4M 1 loop /snap/core18/1944
loop3 7:3 0 32.3M 1 loop /snap/amazon-ssm-agent/2996
loop4 7:4 0 97.9M 1 loop /snap/core/10444
loop5 7:5 0 28.1M 1 loop /snap/amazon-ssm-agent/2333
loop6 7:6 0 97.9M 1 loop /snap/core/10577
Also this command: df -h
this is what I get:
Filesystem Size Used Avail Use% Mounted on
udev 488M 0 488M 0% /dev
tmpfs 100M 11M 89M 11% /run
/dev/xvda1 9.7G 7.6G 2.1G 79% /
tmpfs 496M 0 496M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 496M 0 496M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/1000
/dev/loop0 56M 56M 0 100% /snap/core18/1932
/dev/loop5 29M 29M 0 100% /snap/amazon-ssm-agent/2333
/dev/loop3 33M 33M 0 100% /snap/amazon-ssm-agent/2996
/dev/loop4 98M 98M 0 100% /snap/core/10444
/dev/loop1 56M 56M 0 100% /snap/core18/1944
/dev/loop6 98M 98M 0 100% /snap/core/10577
As you can see the "xvda" keeps in 10GB.
Also, I have tried to create a new Volume and attach it to my instance as mentioned here: https://docs.bitnami.com/aws/how-to/attach-ebs-volume/
On my AWS console front end, everything looks fine and the two volumes say attached. But when I run the previous command lines I got the same results. the "xvda" keeps in 10GB and the newly attached EBS Volume not shown.
I have tried to extend the Linux file system after resizing the volume as mentioned on the documentation of AWS: recognize-expanded-volume-linux - extend-linux-file-system
But How can I extend the Linux file system while I'm not able to see the new volume size or even the new attached volume?
I hope you could help me!
Thank you in advance.