Crash Recovery Problem
I've got MySQL 5.0.55a running on a Windows XP system. All tables in the active database on the system are innodb. The startup log says that innodb recovery completed and that connections are available. Meanwhile, mysql is writing to the hdd at around 2MB/sec according to process explorer. I can connect to the server fine until I run a query against the database. Then no other connections can issue any command whatsoever. The mysql client just freezes up, and I can't make any new connections to the server either. After a period of time, mysqld-nt.exe crashed and one thread is left running, still writing to the drive at approx 2MB/sec. Does anyone out there have any idea what's going wrong here? I'm stumped. -- Grant Limberg [EMAIL PROTECTED]
InnoDB table recovery problem - not beeing able to start database server
Hi. Please help. During long delete operation from one InnoDB table there was PC shutdown due to power supply failure. After that I was unable to start database server so I have started it with set-variable = innodb_force_recovery=4 option and I have dropped all databases with InnoDB tables. Still I am unable to start database server normally. Following is the part of Err file: 030630 11:58:36 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 0 3895685648 InnoDB: Doing recovery: scanned up to log sequence number 0 3895685632 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1777810 row operations to undo InnoDB: Trx id counter is 0 22060800 InnoDB: Starting rollback of uncommitted transactions InnoDB: Rolling back trx with id 0 22060495, 1777810 rows to undo InnoDB: Progress in percents: 1InnoDB: Dump of the tablespace extent descriptor: len 40; hex 00950004aa aafeff; asc ..; InnoDB: Serious error! InnoDB is trying to free page 32306 InnoDB: though it is already marked as free in the tablespace! InnoDB: The tablespace free space info is corrupt. InnoDB: You may need to dump your InnoDB tables and recreate the whole InnoDB: database! InnoDB: If the InnoDB recovery crashes here, see section 6.1 InnoDB: of http://www.innodb.com/ibman.html about forcing recovery. 030630 11:58:37 InnoDB: Assertion failure in thread 580 in file D:\mysql-4.0.12 \innobase\fsp\fsp0fsp.c line 2689 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 030630 11:58:37 mysqld-max-nt: Got signal 11. Aborting! 030630 11:58:37 Aborting 030630 11:58:37 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 030630 11:58:37 mysqld-max-nt: Shutdown Complete Please help B.Sc.E.E Ivan Tomasic -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB table recovery problem - not beeing able to start database server
Ivan, if you have already dumped all InnoDB tables, then there is no need to keep ibdata files and ib_logfiles. You can delete them and recreate them from scratch and reimport the tables. But in the printout which you pasted below you do not have innodb_force_recovery set to 4? When I test 4.0.14, I get a printout which tells the option is set to 4: C:\mysql-4.0.13\mysql-4.0.13\client_debugmysqld --console 030630 16:49:40 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 16 1350394126 InnoDB: Doing recovery: scanned up to log sequence number 16 1350394126 030630 16:49:41 InnoDB: Flushing modified pages from the buffer pool... 030630 16:49:41 InnoDB: Started InnoDB: !!! innodb_force_recovery is set to 4 !!! mysqld: ready for connections Note that innodb_force_recovery only helps you to dump your tables. I have intentionally blocked inserts and updates if innodb_force_recovery 0, because it is not a good idea to use a corrupt database. If the disk or the Windows OS lies to InnoDB about when it really has written a page to disk, you can easily get this kind of corruption at a power outage. The free page bitmap can be out-of-sync with other data structures in the tablespace. Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, foreign keys, and a hot backup tool for MySQL Order MySQL support from http://www.mysql.com/support/index.html Subject: InnoDB table recovery problem - not beeing able to start database server From: Ivan Tomasic Date: Mon, 30 Jun 2003 12:10:08 +0200 Hi. Please help. During long delete operation from one InnoDB table there was PC shutdown due to power supply failure. After that I was unable to start database server so I have started it with set-variable = innodb force recovery=4 option and I have dropped all databases with InnoDB tables. Still I am unable to start database server normally. Following is the part of Err file: 030630 11:58:36 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 0 3895685648 InnoDB: Doing recovery: scanned up to log sequence number 0 3895685632 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1777810 row operations to undo InnoDB: Trx id counter is 0 22060800 InnoDB: Starting rollback of uncommitted transactions InnoDB: Rolling back trx with id 0 22060495, 1777810 rows to undo InnoDB: Progress in percents: 1InnoDB: Dump of the tablespace extent descriptor: len 40; hex 00950004aa aafeff; asc ...Ľ¬¬¬¬¬¬¬¬¬¬¬¬â- ...; InnoDB: Serious error! InnoDB is trying to free page 32306 InnoDB: though it is already marked as free in the tablespace! InnoDB: The tablespace free space info is corrupt. InnoDB: You may need to dump your InnoDB tables and recreate the whole InnoDB: database! InnoDB: If the InnoDB recovery crashes here, see section 6.1 InnoDB: of http://www.innodb.com/ibman.html about forcing recovery. 030630 11:58:37 InnoDB: Assertion failure in thread 580 in file D:\mysql-4.0.12 \innobase\fsp\fsp0fsp.c line 2689 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 030630 11:58:37 mysqld-max-nt: Got signal 11. Aborting! 030630 11:58:37 Aborting 030630 11:58:37 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 030630 11:58:37 mysqld-max-nt: Shutdown Complete Please help B.Sc.E.E Ivan Tomasic -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Recovery Problem
Ives, Thursday, January 24, 2002, 5:04:09 AM, you wrote: IS Hi there, IS yesterday my mysql server (running under irix) has gone away IS and took one table with it IS so i tried to recover the data with isamchk -o table_name IS unfortunalty during the recoveryprocess half of the data IS will be thrown away - is there any way to avoid this? IS bevore recovery: datafile: 4111857 byte - 1498 data sets IS after revovery: datafile: 1936768 byte - 759 data sets IS is there any way to keep the data inside without getting IS it thrown out? even if there will be some pointers pointing IS anywhere behind the end of the file... IS becouse i need the date - even if it will maybe a litte IS damaged... Try to use mysqlcheck or myisamchk. Look at: http://www.mysql.com/doc/T/a/Table_maintenance.html http://www.mysql.com/doc/U/s/Using_mysqlcheck.html See also: http://www.mysql.com/doc/D/i/Disaster_Prevention.html -- For technical support contracts, goto https://order.mysql.com/ This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - 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
Recovery Problem
Hi there, yesterday my mysql server (running under irix) has gone away and took one table with it so i tried to recover the data with isamchk -o table_name unfortunalty during the recoveryprocess half of the data will be thrown away - is there any way to avoid this? bevore recovery: datafile: 4111857 byte - 1498 data sets after revovery: datafile: 1936768 byte - 759 data sets is there any way to keep the data inside without getting it thrown out? even if there will be some pointers pointing anywhere behind the end of the file... becouse i need the date - even if it will maybe a litte damaged... thanks for any suggestions and help greetings dalini - 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
Recovery Problem
Hi All, I'm trying to recover data from a table after all rows in the table were accidentally deleted. I have looked at the .MYD file and all of the information still seems to be there, albeit, flagged as deleted (I assume). Is there any way to recover this information, and undelete it? and if so, How? I don't fancy the idea of having to type everything in again. Any help would be much appreciated. rgds, Paul Kelly. Software Architect TERMINAL FOUR Software Ltd. 1, Herbert Street, Dublin 2, Ireland. T: +353 1 2403110 F: +353 1 6615504 - 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
Recovery Problem
Hi All, sorry if this is duplicated... I'm trying to recover data from a table after all rows in the table were accidentally deleted. I have looked at the .MYD file and all of the information still seems to be there, albeit, flagged as deleted (I assume). Is there any way to recover this information, and undelete it? and if so, How? I don't fancy the idea of having to type everything in again. Any help would be much appreciated. rgds, Paul Kelly. Software Architect TERMINAL FOUR Software Ltd. 1, Herbert Street, Dublin 2, Ireland. T: +353 1 2403110 F: +353 1 6615504 - 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
RE: Recovery Problem
I have been told that once deleted you can not get the data back (can some one correct me)... Have you got all your update logs or binary logs? If you have you should be able to run the sql quires form there and so just recreate your data! This mite be stating the obvious but like any data base they has humane users backups are needed! I hope this help? Simon -Original Message- From: Paul Kelly [mailto:[EMAIL PROTECTED]] Sent: 25 June 2001 17:16 To: '[EMAIL PROTECTED]' Subject: Recovery Problem Hi All, sorry if this is duplicated... I'm trying to recover data from a table after all rows in the table were accidentally deleted. I have looked at the .MYD file and all of the information still seems to be there, albeit, flagged as deleted (I assume). Is there any way to recover this information, and undelete it? and if so, How? I don't fancy the idea of having to type everything in again. Any help would be much appreciated. rgds, Paul Kelly. Software Architect TERMINAL FOUR Software Ltd. 1, Herbert Street, Dublin 2, Ireland. T: +353 1 2403110 F: +353 1 6615504 - 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
