Luke, > Yup. Basically if I do a particular query from the command line, > I get the following error: > =============================== > InnoDB: Error: tried to read 16384 bytes at offset 1 3469819904. > InnoDB: Was only able to read -1. > 060327 8:25:41 InnoDB: Operating system error number 5 in a file > operation. > InnoDB: Error number 5 means 'I/O error'. > InnoDB: Some operating system error numbers are described at > InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html > InnoDB: File operation call: 'read'. > InnoDB: Cannot continue operation. > 060327 08:25:41 mysqld restarted > 060327 8:25: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... > 060327 8:25:42 InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 2 2096716847. > InnoDB: Doing recovery: scanned up to log sequence number 2 2096716847 > InnoDB: Last MySQL binlog file position 0 79, file name > ./ticketdb-bin.000015 > 060327 8:25:42 InnoDB: Flushing modified pages from the buffer pool... > 060327 8:25:42 InnoDB: Started; log sequence number 2 2096716847 > /opt/csw/mysql4/libexec/mysqld: ready for connections. > Version: '4.1.18-log' socket: '/tmp/mysql.sock' port: 3306 Source > distribution
It looks like your disk is having problems.What does 'dmesg' or /var/log/messages say. Thanks, Ravi -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
