InnoDB Corrupted databases (innodb_force_recovery not working)
am 14.12.2009 22:12:27 von Lukas------=_NextPart_000_0082_01CA7D0A.863E8670
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey there,
=20
I have recently imported the database files from a crashed server and I =
am
currently trying to get the new server running with the old data.
=20
However, after starting the MySQL Server, I only get the following error
message:
=20
091214 20:51:46 mysqld started
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
InnoDB: Error: page n:o stored in the page read in is 538976288, should =
be
3!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
InnoDB: You may have to recover from a backup.
091214 20:51:47 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
202020202020202020202020202020202020202020202020202020202020 2020202020202=
020
20202020202020202020202020202020202020202020202020202020202$
091214 20:51:47 InnoDB: Page checksum 1605920614, prior-to-4.0.14-form
checksum 3161919040
InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum
236985105
InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end =
10651
InnoDB: Page number (if stored to page already) 538976288,
InnoDB: space id (if created with >=3D MySQL-4.1.1 and stored already)
538976288
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
After that, the following error message is looped:
=20
091214 20:51:47 InnoDB: Error: trying to access tablespace 538976288 =
page
no. 538976288,
InnoDB: but the tablespace does not exist or is just being dropped.
=20
The MySQL server then is unusable and is taking 99% CPU ressources.
=20
I tried to use the innodb_force_recovery option in the my.cfg file, but =
that
did not change this behavior.
=20
Does anyone have an idea for me to restore the databases? I have no =
backup
and rely on getting this files back to work.
=20
Any help is appreciated, thanks in advance,
=20
Lukas
=20
________________________________
Lukas C. C. Hempel
=20
Delux Group - Approaching future.
=20
Postfach 10 02 10
D-48051 Münster
=20
This e-mail may contain confidential and/or privileged information. If =
you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
=20
Delux Credit:
Delux
Host:
Admin panel:
Paypal:
=20
Delux is a company of Lukas Hempel, Tax ID: 337/5105/2023
=20
------=_NextPart_000_0082_01CA7D0A.863E8670--