Droplet from snapshot: not enough disk space

Posted on July 6, 2019

Hello, I would like to upgrade from standard droplet (160GB) to cpu optimized (25GB).

I then moved /var/www/vhosts from the droplet to a Volume, and now it takes up 7GB only. I then took a snapshot of 7GB.

So far, everything is ok.

But when I try to create a 25GB CPU Optimized droplet, I can’t select it because it says there’s not enough space … For some strange reason I believe that it reads not the snapshot space (7GB) but the droplet type (160GB).

Is it normal?

(I opened a ticket about 5 hours ago but no one answered, I learned that community answers are faster).

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!

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.

vWeb

July 6, 2019

I answer alone, it can be useful to someone.

After 9 hours (9 !!) the assistance answers me that it is not possible to create a 25GB droplet starting from a 7GB snapshot because the snapshot “remembers” that it was generated by a droplet called “160GB”.

I think it’s quite absurd, I want to think of a programming error, but I’m almost sure it’s done on purpose. It makes no sense.

The only way is to do is start from scratch: activate the droplet, reconfigure everything and import the data … bah

At this point, having to start from scratch, it is convenient to transport everything from their “northern competitors”, who at least respond instantly via chat.