Hi, Each night I replicate a server running a 4.1 version of mysql via mysqldump and then import to a box running a 5.0.18-standard. It has been working well for some four or five months. Suddenly, the job started failing during the import. After stepping through the job, I determined that attempting to drop the first database causes mysql to crash.
There are about seven or eight tables in said database, mostly empty, with about five or six records total in the database in question mysql> drop database AccountingAdminDB; ERROR 2013 (HY000): Lost connection to MySQL server during query Per the mysql docs, I first tried rebooting the machine, to no avail. Interestingly, I can read all of the records in the all of the associated files. Check table on each table did not turn up anything. File permissions look ok. I use innodb file per table for most tables. The data directories and subordinates all use mysql.mysql as the owner and group. The data files are rw by owner. A mysql.error.log file is being generated: 060901 9:45:18 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... 060901 9:45:24 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 68 3744135056. InnoDB: Doing recovery: scanned up to log sequence number 68 3744135056 InnoDB: Last MySQL binlog file position 0 0, file name 060901 9:45:24 InnoDB: Started; log sequence number 68 3744135056 060901 9:45:24 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.18-standard' socket: '/srv/mysql/lx07sock' port: 3307 MySQL Community Edition - Standard (GPL) InnoDB: Error: trying to access page number 464309120 in space 0, InnoDB: space name /srv/mysql/lx07/ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10 060901 10:03:37InnoDB: Assertion failure in thread 2934508464 in file fil0fil.c line 3869 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. 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 against 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=268435456 read_buffer_size=8384512 max_used_connections=2 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2719343 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a40170 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xaee8cd1c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x815bbb0 0xffffe420 0x82f2c3e 0x82f2c3e 0x82ea23c 0x8308090 0x83074ee 0x82b5e4f 0x826ff01 0x82a7ed6 0x82a813c 0x82a825c 0x8282ec0 0x8282bfb 0x82979e2 0x820cd73 0x81fffdb 0x8212f00 0x82128b4 0x8211cce 0x8211509 0x81728bf Stack trace seems successful - bottom reached Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x8a5fde8 = drop database AccountingAdminDB thd->thread_id=57 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. 060901 10:03:37 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... 060901 10:03:37 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 68 3744135066. InnoDB: Doing recovery: scanned up to log sequence number 68 3744135066 InnoDB: Last MySQL binlog file position 0 0, file name 060901 10:03:37 InnoDB: Started; log sequence number 68 3744135066 060901 10:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.18-standard' socket: '/srv/mysql/lx07sock' port: 3307 MySQL Community Edition - Standard (GPL) It seems that the innodb table space may be corrupted in some way. Since this is a backup server, I can certainly destroy the data directories and re-import all of the data, but it seems counter-intuitive to wipe over everything and reinstall. Isn't there some sort of repair facility to fix up the innodb table space? Or at least validate that it's ok? Thank you! Regards, Rich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
