一、六个表，每个表几千万数据，i7CPU+16G内存，Debian8.8平台(Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux)，循环读总记录数总是崩溃，

Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'  

暂记如下：

170714 21:20:55  InnoDB: Error: page 15049 log sequence number 35190829121722

InnoDB: is in the future! Current system log sequence number 8532983240.[出自:jiwo.org]
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 15049.
InnoDB: You may have to recover from a backup.
170714 21:20:55  InnoDB: Page dump in ascii and hex (16384 bytes):

len 16384; hex d77d530800003ac900003ac800003aca0000200180de80ba45...........

......................................................................................................................................................（——省略若干二进制字符）

4N3 3 2f1 1 0{/ /:. - -P, , +j* *&) ( (;' & &U% % $j# #'" ! !B     d    =|   < R 8j ' 5 F 3\ t . F c } < V n ( A c { ;
InnoDB: End of page dump
170714 21:20:55  InnoDB: Page checksum 2310221000, prior-to-4.0.14-form checksum 1433651835
InnoDB: stored checksum 3615314696, prior-to-4.0.14-form stored checksum 2802571131
InnoDB: Page lsn 8193 2162065594, low 4 bytes of lsn at page end 2162065594
InnoDB: Page number (if stored to page already) 15049,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 55
InnoDB: Page may be an index page where index id is 69
InnoDB: (index "PRIMARY" of table "ipwarn"."SMTP")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 15049.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
170714 21:20:55  InnoDB: Assertion failure in thread 140304765708032 in file buf0lru.c line 1989
InnoDB: Failing assertion: bpage->buf_fix_count == 0
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/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:20:55 UTC - mysqld got signal 6 ;
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=167772160
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 494157 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
stack_bottom = 0 thread_stack 0x1e0000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7f9b66594f43]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7f9b66481634]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f9b65c7c890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f9b64672067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f9b64673448]
/usr/sbin/mysqld(+0x5c502d)[0x7f9b6667202d]
/usr/sbin/mysqld(+0x5ca3a3)[0x7f9b666773a3]
/usr/sbin/mysqld(+0x5be8d6)[0x7f9b6666b8d6]
/usr/sbin/mysqld(+0x5ee8d9)[0x7f9b6669b8d9]
/usr/sbin/mysqld(+0x576b68)[0x7f9b66623b68]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f9b65c75064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f9b6472562d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
170714 21:20:55 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170714 21:20:55 [Warning] option 'innodb-autoextend-increment': unsigned value 134217728 adjusted to 1000
170714 21:20:55 [Note] Plugin 'FEDERATED' is disabled.
170714 21:20:55 InnoDB: The InnoDB memory heap is disabled
170714 21:20:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170714 21:20:55 InnoDB: Compressed tables use zlib 1.2.8
170714 21:20:55 InnoDB: Using Linux native AIO
170714 21:20:55 InnoDB: Initializing buffer pool, size = 128.0M
170714 21:20:55 InnoDB: Completed initialization of buffer pool
170714 21:20:55 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
170714 21:20:55  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...
170714 21:20:56  InnoDB: Waiting for the background threads to start
170714 21:20:57 InnoDB: 5.5.55 started; log sequence number 8532983240
170714 21:20:57 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170714 21:20:57 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170714 21:20:57 [Note] Server socket created on IP: '0.0.0.0'.
170714 21:20:57 [Note] Event Scheduler: Loaded 0 events
170714 21:20:57 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.55-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)