EBS Disk is full
We are almost running out of 16 TiB space on a EBS disk. The application can only mount to a single mount. For example: lets call it as app
We don't want to change the instance type. I was wondering if you could suggest how we can solve this?
Would it be ideal to add another EBS disk, move some of the old data to the new disk and then make symlinks on the old EBS volume to the moved data on the new EBS volume?
Thanks
- Newest
- Most votes
- Most comments
I'm assuming that the application can only deal with one directory instead of one mount. Something like:
/data - 16TB Volume
Where something like this would not work:
/data - 16TB Volume
/data2 - 16TB Volume
How about mounting the volumes in this manner:
/data/current - 16TB Volume
/data/old - 16TB Volume
You could also look at using Amazon EFS.
You can modify your volume and increase the size of your EBS Volume for details on how to do it see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/requesting-ebs-volume-modifications.html Once the Volume is increased you can extend the File System after the volume has been resized, for details on how to resize the File System see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html
I agree but we have hit the max limit on a single EBS volume of 16TB, hence I would like to ask if we should create another volume. move some old data to the new volume and then sym link
Thank you Nuno
You can also attach multiple volumes and RAID them together: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/raid-config.html
Thank you Rodney
Relevant content
AWS OFFICIALUpdated 10 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thank you. Our application can't cater
/data/currentand/data/old. The data is stored under/data/yyyy/mmand we can't mount 2 mount points as we need a single mount point EFS would cause performance issues, So EBS would be the correct choice.But the application does not mount the volumes, it is only dealing with paths into the file system, right? So, you could have each /data/yyyy mounted with a different volume. The application traversing the directory would be unaware that these are multiple volumes. It would be pretty easy to test.
Yes, I agree. the application can't cater for different paths such as
/data/currentand/data/old. Let's say it uses the path like/app/data/yyyy/mmwe usually create sym links under/appto point to a diff pathUsing sym links should work, but I'm not sure what additional benefit it gets you. You still have to mount the additional volumes. /app/data/2022 is the mount point for a 16TB volume. /app/data/2021 is the mount point for another 16TB volume. And so on.
Thank you very much for all your help.