How to Extend Dremio AWSE EBS Volume – Dremio Support

Overview

If there is a requirement to extend the the EBS volume (/dev/sdf) for Dremio AWSE deployments, then the following steps can be used to extend and then expand the volume so that it is reflected correctly in the AWS EC2 Instance 'Storage' tab of the Project instance the volume is attached to as well as the Linux df command on the coordinator instance.

Applies To

All versions of Dremio AWSE deployments.

Details

The below steps explain how to extend the EBS volume and then expand it to reflect the additional disk space

Increase the size of the new cluster's EBS volume (/dev/sdf) via AWS UI https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/requesting-ebs-volume-modifications.html#modify-ebs-volume
Then login in to your cluster's coordinator node and run: sudo lsblk and note the size of the extended EBS volume (/var/dremio_ebs)
Then run: sudo blkid
Copy and keep a note of the UUID for /dev/nvme1n1: LABEL="c1"
Edit /etc/fstab to change the entry /dev/nvme1n1 /mnt/c1 to UUID=…. /mnt/c1 with the UUID value you copied from Step #6 (NOTE this step is a preventative measure against the /var/dremio_ebs directory ended up on /mnt/c1 after a re-boot of the instance/VM).
Then Expand the filesystem for the EBS volume to utilize this disk space you increased in Step #4 with the information from the following link https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html
e.gsudo resize2fs /dev/nvme2n1
NOTE: Note that device and partition naming differs for Xen instances and Nitro instances. To determine whether your instance is Xen-based or Nitro-based, use the describe-instance-types AWS CLI command per the above AWS docs link.
Now run df -hT and confirm you see the correctly reflected disk size for /var/dremio_ebs

Overview

Applies To

Details

Further Reading

Related articles