Attach the volume during instance creation or later from instance actions. You can also attach via the API.
Once attached, the volume appears as a block device. Example: /dev/vdb.
/dev/vdb
Replace:
<DEVICE> with the device name (example: vdb or nvme1n1)
<DEVICE>
vdb
nvme1n1
<MOUNT_DIR> with your mount directory (example: data)
<MOUNT_DIR>
data
Attach the volume to the instance in the console. Or attach it via the API.
lsblk
Pick the new disk. Example: vdb or nvme1n1.
This erases all data on the device. Do not run this on a volume that already contains data.
sudo mkfs.ext4 /dev/<DEVICE>
sudo mkdir -p /mnt/<MOUNT_DIR> sudo mount /dev/<DEVICE> /mnt/<MOUNT_DIR>
Use the filesystem UUID to avoid device-name changes.
sudo blkid /dev/<DEVICE>
Then add an entry to /etc/fstab:
/etc/fstab
grep -qxF "UUID=<UUID> /mnt/<MOUNT_DIR> ext4 defaults,nofail 0 0" /etc/fstab || echo "UUID=<UUID> /mnt/<MOUNT_DIR> ext4 defaults,nofail 0 0" | sudo tee -a /etc/fstab
Currently instant clusters have fixed storage by default. Contact us via chat in the console or email us at [email protected]envelope if you need to adjust your cluster's storage.
Last updated 16 days ago
Was this helpful?