I have been testing different combinations of ram/vcpu and went from standard to optimized and now trying to get back to standard and the resize doesn’t seem to be completing? I don’t want to refresh the page, not sure if that would be a bad thing or not?
ah, guess the resize page just barfed or something, ended up just powering the droplet back up and it’s back to my standard size I was shooting for.
Good to hear it worked out mate. One thing to reiterate real quick – we support such moves as long as the local disk size is equal or larger on the target (easy to expand a filesystem without corruption, our experience is the shrink is best done via a migration).
sure, as I said in the OP, I was doing a ram/vcpu only resize. I realize that resizing the disk is a whole different thing. Anyway, the resize page never did seem to finish (as in the loading gif on the resize button just continued). I finally decided to reload the page and then it just showed the target size that I was trying to set it to grayed out. I allowed it what should have been plenty of time and then powered back up and all was well, so just a page glitch I guess. The process obviously completed. Ty.