Post Jobs

mysql还原后启动出问题

MySQL crash:InnoDB redo log error的解决

mysql还原后启动出问题 5C
2018-04-15 15:18:11 24653 [Note] Plugin ‘FEDERATED’ is disabled.
2018-04-15 15:18:11 24653 [Note] InnoDB: Using atomics to ref count
buffer pool pages
2018-04-15 15:18:11 24653 [Note] InnoDB: The InnoDB memory heap is
disabled
澳门新葡亰平台游戏,2018-04-15 15:18:11 24653 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2018-04-15 15:18:11 24653 [Note] InnoDB: Memory barrier is not used
2018-04-15 15:18:11 24653 [Note] InnoDB: Compressed tables use zlib
1.2.3
2018-04-15 15:18:11 24653 [Note] InnoDB: Using Linux native AIO
2018-04-15 15:18:11 24653 [Note] InnoDB: Using CPU crc32
instructions
2018-04-15 15:18:11 24653 [Note] InnoDB: Initializing buffer pool,
size = 128.0M
2018-04-15 15:18:11 24653 [Note] InnoDB: Completed initialization of
buffer pool
2018-04-15 15:18:11 24653 [Note] InnoDB: Setting log file
./ib_logfile101 size to 48 MB
2018-04-15 15:18:11 24653 [Note] InnoDB: Setting log file
./ib_logfile1 size to 48 MB
2018-04-15 15:18:12 24653 [Note] InnoDB: Renaming log file
./ib_logfile101 to ./ib_logfile0
2018-04-15 15:18:12 24653 [Warning] InnoDB: New log files created,
LSN=48585617787
2018-04-15 15:18:12 24653 [Note] InnoDB: Highest supported file format
is Barracuda.
2018-04-15 15:18:12 7ffa03794740 InnoDB: Error: page 7 log sequence
number 254015752729
InnoDB: is in the future! Current system log sequence number

 

  1. InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB:

    InnoDB: for more information.
    2018-04-15 15:18:12 7ffa03794740 InnoDB: Error: page 1 log sequence
    number 249801886007
    InnoDB: is in the future! Current system log sequence number
  2. InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB:

    InnoDB: for more information.
    2018-04-15 15:18:12 7ffa03794740 InnoDB: Error: page 3 log sequence
    number 73815057441
    InnoDB: is in the future! Current system log sequence number
  3. InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See

InnoDB: Progress in percents: 1120731  9:56:59  InnoDB: Error: page 9
log sequence number 5746244819174

InnoDB: is in the future! Current system log sequence number
5706919300319.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files.

===================================

innodb redo log 出错  www.2cto.com  

发表评论

电子邮件地址不会被公开。 必填项已用*标注

相关文章

网站地图xml地图