在Linux下mysql不断出错重启，请问一下原因和解决方法

[kurt9]

版本是4.1.14，操作系统是red hat linux，用的都是innoDB
以下是两段LOG：

第一段：

Thread database.table_name Locked/Waiting Lock_type

8 mcoolwap.jc_news Locked - read Low priority read lock
30 mcoolwap.jc_news_attach Locked - read Low priority read lock
37 mcoolwap.pebook Locked - read Low priority read lock
40 mcoolwap.jc_room_content Locked - read Low priority read lock



InnoDB: Error: tried to read 16384 bytes at offset 1 804798464.
InnoDB: Was only able to read 8192.
060521 11:09:34 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
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.

Memory status:
Non-mmapped space allocated from system: 503808
Number of free chunks: 40
Number of fastbin blocks: 0
Number of mmapped regions: 14
Space in mmapped regions: 455815168
Maximum total allocated space: 0
Space available in freed fastbin blocks: 0
Total allocated space: 120528
Total free space: 383280
Top-most, releasable space: 125608
Estimated memory (with thread stack): 462413824


Number of processes running now: 0
060521 11:09:34 mysqld restarted
060521 11:09:34 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...
060521 11:09:34 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 898692468.
InnoDB: Doing recovery: scanned up to log sequence number 3 898729403
060521 11:09:34 InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97
98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 61201, file name
./localhost-bin.000106
060521 11:09:35 InnoDB: Flushing modified pages from the buffer pool...
060521 11:09:35 InnoDB: Started; log sequence number 3 898729403
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.14-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL
Community Edition - Standard (GPL)
InnoDB: Error: tried to read 16384 bytes at offset 1 804798464.
InnoDB: Was only able to read 8192.
060521 11:10:02 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
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.

Number of processes running now: 0
060521 11:10:03 mysqld restarted
060521 11:10:03 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...
060521 11:10:03 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 898772396.
InnoDB: Doing recovery: scanned up to log sequence number 3 898797835
060521 11:10:03 InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97
98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 34306, file name
./localhost-bin.000107
060521 11:10:03 InnoDB: Flushing modified pages from the buffer pool...
060521 11:10:03 InnoDB: Started; log sequence number 3 898797835
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.14-standard-log' socket: '/tmp/mysql.sock' port: 3306 MySQL
Community Edition - Standard (GPL)
InnoDB: Error: tried to read 16384 bytes at offset 1 804798464.
InnoDB: Was only able to read 8192.
060521 11:10:43 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
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.

第二段：
Thread database.table_name Locked/Waiting Lock_type

9 mcoolwap.jc_friend_mobile_uaLocked - write Concurrent insert lock
115 mcoolwap.jc_room_content Locked - read Low priority read lock
117 mcoolwap.website Locked - read Low priority read lock
119 mcoolwap.pebook Locked - write High priority write lock
130 mcoolwap.jc_news_attach Locked - read Low priority read lock
133 mcoolwap.jc_news Locked - read Low priority read lock
134 mcoolwap.user_friend Locked - read Low priority read lock



InnoDB: Error: tried to read 16384 bytes at offset 1 804798464.
InnoDB: Was only able to read 8192.
060521 23:58:31 InnoDB: Operating system error number 4 in a file operation.
InnoDB: Error number 4 means 'Interrupted system call'.
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.