Hongliu, what do you do mean with 'copying tables to another disk'? What did you do? Did you kill the mysqld server? What is the MySQL version and what OS?
The assertion below means the rollback of a transaction is trying to free a database page which already is free. Thus the tablespace free space info is corrupt. Please see http://www.innodb.com/ibman.html#Forcing_recovery about forcing recovery. The setting set-variable = innodb_force_recovery = 4 in my.cnf will probably bring your database up so that you can dump your tables and recreate a new InnoDB database. I added now diagnostic code to fsp0fsp.c which may help to track the problem if it reappears. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com ----- Original Message ----- From: ""LiuHongliu"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Thursday, May 30, 2002 9:16 AM Subject: about crash > dear support: > i am a user of innodb,but today i meet a big problem. > i am copying all innondb table to the other disk,then in progressing ,i > interupt the command. > now the mysql couldn't start. > > now the error below: > > 020530 12:33:54 mysqld started > 020530 12:33:56 InnoDB: Database was not shut down normally. > InnoDB: Starting recovery from log files... > InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 2 1225053951 > InnoDB: 3 uncommitted transaction(s) which must be rolled back > InnoDB: Trx id counter is 0 181405952 > InnoDB: Starting rollback of uncommitted transactions > InnoDB: Rolling back trx with id 0 181404428 > InnoDB: Assertion failure in thread 137175040 in file fsp0fsp.c line 2464 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > mysqld got signal 11; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked agaist 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 > > key_buffer_size=134213632 > record_buffer=1044480 > sort_buffer=6291448 > max_used_connections=0 > max_connections=200 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 1563866 K > bytes of memory > Hope that's ok, if not, decrease some variables in the equation > > 020530 12:33:56 mysqld ended > > > help me plz. thank you > > automan > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
