Guides - Configure and Mount a Volume
Block Storage is a scalable, high-speed, and fault tolerant storage service used to add additional storage to a Linode Compute Instance.
Once a Block Storage Volume has been attached to a Compute Instance, you need to perform a few additional steps before you can start using it. These steps include creating a file system (if you’re configuring a new Volume) and mounting the Volume to your Compute Instance’s system. To make configuration easier, all the necessary commands can be viewed directly in the Cloud Manager.
Log in to the Cloud Manager and click on the Volumes link in the sidebar.
Locate the desired Volume within the list and click the Show Config link, which may appear within the more options ellipsis dropdown menu.
The Volume Configuration panel appears and contains the commands needed to fully configure the Volume with your Compute Instance.
Enter each command that’s shown in the Volume Configuration panel, modifying them if needed. These configuration steps are also listed below:
Create a file system. If your Volume has not been used before, create an ext4 file system on the Volume.
Skip this step if you wish to retain any data stored on an existing Volume. Creating a new file system will overwrite any existing data and result in data loss. You can view existing file systems on an unmounted volume with the following command:
If you do not receive output, there is currently no file system on this volume.
You can create an ext4 file system by running the following command, where
FILE_SYSTEM_PATHis your Volume’s file system path:
Create a mount point. This is the directory on your Linux system where the Block Storage files will be located.
Mount the Volume manually. Mount the Block Storage Volume to the directory you just created. After this is completed, you can access your files from that directory.
mount FILE_SYSTEM_PATH /mnt/BlockStorage1
Mount the Volume automatically. If you want to mount the new Volume automatically every time your Compute Instance boots, add the following line to your /etc/fstab file:
FILE_SYSTEM_PATH /mnt/BlockStorage1 ext4 defaults 0 2
If you plan on detaching the volume regularly or moving it between other Compute Instances, you may want to consider adding the flags
nofailto the /etc/fstab entry.
noatime- This will save space and time by preventing writes made to the file system for data being read on the volume.
nofail- If the volume is not attached, this will allow your server to boot/reboot normally without hanging at dependency failures if the volume is not attached.
FILE_SYSTEM_PATH /mnt/BlockStorage1 ext4 defaults,noatime,nofail 0 2
This page was originally published on