Comments on: InnoDB Tablespace Corruption

By: John

John — Fri, 22 Jan 2010 18:10:22 +0000

The fact that terabytes of data could be so easily corrupted is kind of unsettling. The incremental backup for just one day’s worth of data takes us hours. Restoring all of the backups would take weeks if not months. Guess this is why those with money go with Oracle

By: James Day

James Day — Tue, 19 Jan 2010 11:41:18 +0000

You should check whether your disk system respects fsyncs. One way to get out of sync like this is out of order writing and losing a change that the server thinks is safely on disk.

By: Log Buffer #170: a Carnival of the Vanities for DBAs | The Pythian Blog

Log Buffer #170: a Carnival of the Vanities for DBAs | The Pythian Blog — Fri, 20 Nov 2009 17:45:15 +0000

[...] Anuganti also was surprised, in his case by InnoDB Tablespace Corruption: “When . . . InnoDB crashes, it automatically recovers during the next [...]

By: Venu Anuganti

Venu Anuganti — Wed, 18 Nov 2009 22:25:45 +0000

No, 5.0.77

By: Justin Swanhart

Justin Swanhart — Wed, 18 Nov 2009 21:53:59 +0000

Are you using the InnoDB plugin?

By: Martin

Martin — Wed, 18 Nov 2009 05:33:01 +0000

Last week it happened in our company, but its not with disk full instead one of the disk went bad in RAID; and server crashed.