Description:
Mysql server 5.0.36-enterprise-gpl crashes consistantly when the show tables command is issued from a remote connection. Client is version 14.7 distribution 4.1.22. Top shows no significant load. Below is the error log.
Number of processes running now: 0
081222 20:04:58 mysqld restarted
081222 20:04:58 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...
081222 20:04:58 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 500 1314937215.
InnoDB: Doing recovery: scanned up to log sequence number 500 1314937215
InnoDB: Last MySQL binlog file position 0 37911338, file name ./mysql-bin.000002
081222 20:04:58 InnoDB: Started; log sequence number 500 1314937215
081222 20:04:58 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.36-enterprise-gpl' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Enterprise Server (GPL)
InnoDB: Error: tried to read 16384 bytes at offset 0 4915200.
InnoDB: Was only able to read 8192.
081222 20:05:42 InnoDB: Operating system error number 0 in a file operation.
InnoDB: Error number 0 means 'Success'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
Number of processes running now: 0
081222 20:05:42 mysqld restarted
081222 20:05:42 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...
081222 20:05:42 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 500 1314937215.
InnoDB: Doing recovery: scanned up to log sequence number 500 1314937215
InnoDB: Last MySQL binlog file position 0 37911338, file name ./mysql-bin.000002
081222 20:05:42 InnoDB: Started; log sequence number 500 1314937215
081222 20:05:42 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.36-enterprise-gpl' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Enterprise Server (GPL)
InnoDB: Error: tried to read 16384 bytes at offset 0 4915200.
InnoDB: Was only able to read 8192.
081222 20:05:56 InnoDB: Operating system error number 0 in a file operation.
InnoDB: Error number 0 means 'Success'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
Number of processes running now: 0
081222 20:05:56 mysqld restarted
081222 20:05:56 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...
081222 20:05:56 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 500 1314937215.
InnoDB: Doing recovery: scanned up to log sequence number 500 1314937215
InnoDB: Last MySQL binlog file position 0 37911338, file name ./mysql-bin.000002
081222 20:05:56 InnoDB: Started; log sequence number 500 1314937215
How to repeat:
Connect remotely to MySql server 5.0.36. form Client version 14.7 distribution 4.1.22 (both linux). Issue the show tables command.
