Hello,=0A=0AI copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole database directory) from one crashed machine to another.=0AI find that I cannot start database to get the database data any more.=0AI tried innodb_force_recovery=1=0Aor innodb_force_recovery=4, it doesn't help.=0A=0AHere is the error message I got:=0A130620 00:47:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql=0AInnoDB: Error: tablespace size stored in header is 456832 pages, but=0AInnoDB: the sum of data file sizes is only 262080 pages=0AInnoDB: Cannot start InnoDB. The tail of the system tablespace is=0AInnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an=0AInnoDB: inappropriate way, removing ibdata files from there?=0AInnoDB: You can set innodb_force_recovery=1 in my.cnf to force=0AInnoDB: a startup if you are trying to recover a badly corrupt database.=0A130620 0:47:08 [ERROR] Plugin 'InnoDB' init function returned error.=0A130620 0:47:08 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.=0A130620 0:47:09 [Note] Event Scheduler: Loaded 0 events=0A130620 0:47:09 [Note] /usr/libexec/mysqld: ready for connections.=0AVersion: '5.1.52' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution=0AInnoDB: Error: trying to access page number 10929 in space 0,=0AInnoDB: space name ./ibdata1,=0AInnoDB: which is outside the tablespace bounds.=0AInnoDB: Byte offset 0, len 16384, i/o type 10.=0AInnoDB: If you get this error at mysqld startup, please check that=0AInnoDB: your my..cnf matches the ibdata files that you have in the=0AInnoDB: MySQL server.=0A130620 0:47:09 InnoDB: Assertion failure in thread 2985618288 in file fil/fil0fil.c line 4123=0AInnoDB: We intentionally generate a memory trap.=0AInnoDB: Submit a detailed bug report to http://bugs.mysql.com.=0AInnoDB: If you get repeated assertion failures or crashes, even=0AInnoDB: immediately after the mysqld startup, there may be=0AInnoDB: corruption in the InnoDB tablespace. Please refer to=0AInnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html=0AInnoDB: about forcing recovery.=0A130620 0:47:09 - mysqld got signal 6 ;=0AThis could be because you hit a bug. It is also possible that this binary=0Aor one of the libraries it was linked against is corrupt, improperly built,=0Aor misconfigured. This error can also be caused by malfunctioning hardware.=0AWe will try our best to scrape up some info that will hopefully help diagnose=0Athe problem, but since we have already crashed, something is definitely wrong=0Aand this may fail.=0A=0Ais there a way to start the database again?=0AThanks for your help in advance.=0A=0APeter

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