Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # mysqld --log-error=/root/mysql_wft_log
- 130803 18:00:04 [Note] Plugin 'FEDERATED' is disabled.
- 130803 18:00:04 InnoDB: The InnoDB memory heap is disabled
- 130803 18:00:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 130803 18:00:04 InnoDB: Compressed tables use zlib 1.2.3
- 130803 18:00:04 InnoDB: Using Linux native AIO
- 130803 18:00:04 InnoDB: Warning: innodb_file_io_threads is deprecated. Please use innodb_read_io_threads and innodb_write_io_threads instead
- 130803 18:00:04 InnoDB: Initializing buffer pool, size = 4.0G
- 130803 18:00:04 InnoDB: Completed initialization of buffer pool
- 130803 18:00:04 InnoDB: highest supported file format is Barracuda.
- InnoDB: Log scan progressed past the checkpoint lsn 537210815873
- 130803 18:00:04 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...
- InnoDB: Doing recovery: scanned up to log sequence number 537212366959
- InnoDB: Error: tried to read 16384 bytes at offset 0 4931584.
- InnoDB: Was only able to read 0.
- 130803 18:00:22 InnoDB: Operating system error number 5 in a file operation.
- InnoDB: Error number 5 means 'Input/output error'.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
- InnoDB: File operation call: 'read'.
- InnoDB: Cannot continue operation.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement