Web lists-archives.com

innodb log sequence problem




Hello,

We are facing a strange innodb related problem. Our client ran mysql 5.1 on WinXP having file_per_table disabled. OS crashed after 5 years continuous running and our client of course does not have any backup (big company with own IT department so we do not have acces to their system and IT policy).
We received the mysql folders to see whether we can recover data somehow.

We installed a new myql 5.1 instance. Changed my.ini in program files\mysql\msql server 5.1 either changed bin folder all in all. We changed data folder as well to the crashed on containing all database folders with all .frm files ib_logfile0, ib_logfile1 and ibdata1 as well. Trying to start mysql service log says the following:

50805 16:58:28 [Note] Plugin 'FEDERATED' is disabled.
150805 16:58:28  InnoDB: Initializing buffer pool, size = 47.0M
150805 16:58:28  InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file .\ib_logfile0 is of different size 0 10485808 bytes
InnoDB: than specified in the .cnf file 0 25165824 bytes!
150805 16:58:28 [ERROR] Plugin 'InnoDB' init function returned error.
150805 16:58:28 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150805 16:58:28 [ERROR] Unknown/unsupported table type: INNODB
150805 16:58:28 [ERROR] Aborting

Strange is that ib_logfile0 is 10MB+48 bytes however as far as I know innodb_log_file_size system variable can only be added in M.

We tryed to remove ib_logfile0 and ib_logfile1 from data folder and tryed to start the instance again. Logfiles were created but got the following error mesage in error log:

150805 17:02:29 [Note] Plugin 'FEDERATED' is disabled.
150805 17:02:30  InnoDB: Initializing buffer pool, size = 47.0M
150805 17:02:30  InnoDB: Completed initialization of buffer pool
150805 17:02:30 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 24 MB
InnoDB: Database physically writes the file full: wait...
150805 17:02:30 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 24 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150805 17:02:31  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
150805 17:02:31  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 960999566:544833488, should be 0:7!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 7.
InnoDB: You may have to recover from a backup.
150805 17:02:31  InnoDB: Page dump in ascii and hex (16384 bytes):
hex...
150805 17:02:31 InnoDB: Page checksum 1094951825, prior-to-4.0.14-form checksum 1449969277 InnoDB: stored checksum 1467223489, prior-to-4.0.14-form stored checksum 87759728 InnoDB: Page lsn 1054562273 1692468334, low 4 bytes of lsn at page end 3304862103
InnoDB: Page number (if stored to page already) 544833488,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 960999566
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 7.
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/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.

We tried to start with system variable innodb_force_recovery set 1-6 none of them helped.

Does anyone have any idea how to recover?

Many thanks in advance.

Arpad Csepregi


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql