This page shows how to attach and detach additional volumes to an existing server.
Each BareMetal Cloud Instance can have up to 15 volumes, including the root volume.
The type of disk to host your volumes usse the LSSD technology: Local solid state drive, to deliver fast disk I/O.
Note: Flexible Volumes are available on BareMetal Cloud Instances. For Virtual Cloud Instances the volume size is fixed, depending on the offer.
LSSD volumes are transferred close to your instance.
When you start a instance for the first time, your volume files are downloaded from the volumes store to the local storage devices (LSSD).
Each time you start or stop a instance, the volumes are downloaded or uploaded to the volumes store. The larger the amount of data to transfer, the longer the upload or download duration.
We work constantly on optimizing the transfer time of local storage devices to the volumes store.
There are five steps to attach a volume to an existing instance
Important: An instance must be powered off to attach or detach a volume.
In the Control Panel, click Volumes in the compute section.
1 . Click the Create Volume button.
2 . The volume-creation window displays. Enter the required information for your volume:
1 . In the Volumes list click on Attach to server next to the concerned volume.
2 . In the “Attach Volume” window, select the instance on which you want to attach the volume.
3 . Once the volume is attached to your instance, you can use
lsblk to determine its name. Please note that the name might be different depening on the instance type you use. It might be something like
/dev/nbdX for a BareMetal instance or
/dev/vdX for a Virtual Cloud Instance.
As exemplified below, the additional volume is named vdb:
root@scw-8838b4:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 46.6G 0 disk |-vda1 252:1 0 46.5G 0 part / `-vda15 252:15 0 100M 0 part /boot/efi vdb 252:16 0 46.6G 0 disk
If the new volume has never been formatted, you need to format the volume using
mkfs before you can mount it.
1 . The following command creates an
ext4 file system on the volume:
1 . To mount the device manually as /mnt/data, run the following commands:
To mount the additional volume automatically, you can create a systemd script that will mount your volumes automatically during the boot of your cloud instance.
1 . If not yet done, create the directory into you want to mount your volume:
mkdir -p /mnt/data
2 . As the volume is empty by default, you have to create a filesystem before you can use it. To format it with with an
ext4 filesystem, use the following command:
mkfs -t ext4 /dev/nbd1
3 . To get the
UUID of your volume, run the command
blkid and take a note of the ID as you will need it in the next step.
4 . Create or edit the file that corresponds to the path of your directory
nano /etc/systemd/system/mnt-data.mount and edit is as following: The file name of the script must correspond to the path where you mount the volume (
UUID with the ID of your volume.
5 . Now reload systemd:
6 . Launch the script to mount the volume:
systemctl start mnt-data.mount 7 . Finally enable the script to mount your volume automatically during boot:
systemctl enable mnt-data.mount
Your volume will automatically be mounted after a reboot. You can run the
df -h command, this command will list all your devices and where they are mounted:
1 . On the details page of a instance, click on Volumes to view the list of connected volumes.
2 . Click on “Detach”, then confirm that you want to detach the volume: