After I ran the command
fly volumes create data \
--snapshot-id vs_blahblahblahblah \
--size 10 \
-a app_name
The volume status is stuck on restoring.
After I ran the command
fly volumes create data \
--snapshot-id vs_blahblahblahblah \
--size 10 \
-a app_name
The volume status is stuck on restoring.
Hm… What does fly vol list say, in full, at the moment?
ID STATE NAME SIZE REGION ZONE ENCRYPTED ATTACHED VM CREATED AT
vol_re8z2jynky68z8dr created data 35GB nrt fe01 true d8d9ee3c975978 3 weeks ago
vol_42l6e37017xj180r restoring data 10GB nrt a21b true 2 hours ago
Two hours… I would try restoring into a different region. It sounds like there might be isolated network problems in the system right now.
(Snapshot restores download from S3, I believe.)
Hi @Paste,
That restore hit an error because there was insufficient space. It’s a snapshot of a 35GB volume, but the volume you’re restoring to is only 10GB.
If you change the --size to 35 (or don’t specify a size) the restore should succeed.
I’ll look into why we don’t validate the size upfront, and also what we can do improve error reporting here.
We’ve improved the validation here: there’s now a useful error message if volume is too small for the snapshot.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.