Today I’ve been creating a few snapshots from existing volumes and then making new volumes from those snapshots. I also created some empty volumes. I’m observing some very inconsistent behavior. The following things have occurred a number of times: A newly created empty volume gets mounted to a directory named something like /mnt/.do-first-mount-ANrvB8Vrs and it’s size is 333MB instead of it being mounted to the place I requested with a size of 1 TB. If I detach the volume and re-attach it it goes to the right place, but I still have to manually resize the file system in order for it to use the full 1 TB The volume restored from a snapshot gets mounted to /mnt/.do-first-mount-ANrvB8Vrs The volume restored from a snapshot has the correct file system size, but is empty. Has anyone else observed anything like this?

Strange behaviour with volumes and snapshots

Posted March 19, 2020
DigitalOcean Volumes

Today I’ve been creating a few snapshots from existing volumes and then making new volumes from those snapshots. I also created some empty volumes. I’m observing some very inconsistent behavior. The following things have occurred a number of times:

A newly created empty volume gets mounted to a directory named something like /mnt/.do-first-mount-ANrvB8Vrs and it’s size is 333MB instead of it being mounted to the place I requested with a size of 1 TB. If I detach the volume and re-attach it it goes to the right place, but I still have to manually resize the file system in order for it to use the full 1 TB
The volume restored from a snapshot gets mounted to /mnt/.do-first-mount-ANrvB8Vrs
The volume restored from a snapshot has the correct file system size, but is empty.

Has anyone else observed anything like this?