[google-cloud-sql-discuss] Tablespace free space info is corrupted

Hello,

After a mistake (too much requests) our Cloud SQL got corrupted and keeps restarting.

After some research, this could solve the problem:

[mysqld]

innodb_force_recovery = 1

But we do not have access to system configuration.

So... We accepted that we have lost 1 day and start the recovering work.

Obs: We tried to clone the instance, but the clone never started.

Two questions:

- Is it possible to Google Support recover the database?

- We can't delete the clone instance because of its status (PENDING_CREATE). How to proceed?

Part of the log message:

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

12:03:13 UTC - mysqld got signal 6 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed,

something is definitely wrong and this may fail.

Thank you,

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/8cbd33d7-13b2-4b19-8667-80bdd6a05c8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.