Question

Created a new volume of 20Gb, but dh -f shows size as 368M

From the dashboard, I created a new volume of 20Gb.

I followed the mount instructions, and got it mounted. Specifically, I did this (copy pasting here what I copy pasted from the configuration instructions)

# Create a mount point for your volume:
$ mkdir -p /mnt/ek_core_backup

# Mount your volume at the newly-created mount point:
$ mount -o discard,defaults,noatime /dev/disk/by-id/scsi-0DO_Volume_ek-core-backup /mnt/ek_core_backup

# Change fstab so the volume will be mounted after a reboot
$ echo '/dev/disk/by-id/scsi-0DO_Volume_ek-core-backup /mnt/ek_core_backup ext4 defaults,nofail,discard 0 0' | sudo tee -a /etc/fstab

Then I rebooted my droplet. Volumes dashboard indicates it’s attached to the droplet, and I can access it via cd /mnt/ek_core_backup on the terminal.

However, when I tried copying files to it, it complained of size being full for the new mounted point.

Running dh -f thus revealed the /dev/sda mounted on /mnt/ek_core_backup is just showing 368M as max size. Obviously that’s not the expected size.

Am I missing a step?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello @seanmavley

You can check our tutorial on How to mount volumes here

https://docs.digitalocean.com/products/volumes/how-to/mount/

Looking at the provided commands the mount command has one less argument which should not cause issues like this one, but you can still try to complete the process by following the article.

If you’re still experiencing the issue you can also reach out to our support team.

Regards

For anyone curious, the instructions here will get your volume to show up as expected: https://askubuntu.com/a/1076087/101644

However, I’m just curious if this behavior with volumes is expected, as in, a newly created volume only shows a fraction of the total size.