We just had our first major problem with CLIMB. We attempted to re-size an instance, which failed. It sent the instance into an error state and we re-booted to get it working again. When we logged back on to the instance, it was a ‘clean’ instance, similar to if we had just launched it.
This was also the case for the volume attached to the instance. Which was surprising and alarming.
The instance is catanscombe and the volume was Cat.
Is there anything that can be done to recover this? We would really appreciate it.
Couple of questions, first ; did GVL remount the volume automatically onto /mnt ? If you have a single volume attached the GVL will autoremount it to /mnt.
Second, how did you create the filesystem? I ask because there are two ways of doing it (you can do mkfs directly on the volume or you can do fdisk on the volume and then mkfs), and I wonder if the issue might be related to that.
I know the others are looking into this, just wanted to check the above!