请问一下这是为啥
2022-12-28 17:58:56
ygx
|
2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-12-28 17:50:07 140576082810752 [Note] InnoDB: The InnoDB memory heap is disabled 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Compressed tables use zlib 1.2.3.4 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Using SSE crc32 instructions 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Initializing buffer pool, size = 512.0M 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Completed initialization of buffer pool 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Highest supported file format is Barracuda. 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: The log sequence numbers 4852356 and 4852356 in ibdata files do not match the log sequence number 4852748 in the ib_logfiles! 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... InnoDB: wrong number of columns in SYS_INDEXES record InnoDB: wrong number of columns in SYS_INDEXES record InnoDB: wrong number of columns in SYS_INDEXES record InnoDB: wrong number of columns in SYS_INDEXES record InnoDB: wrong number of columns in SYS_INDEXES record InnoDB: wrong number of columns in SYS_INDEXES record 2022-12-28 17:50:07 140576082810752 [Note] InnoDB: Creating tablespace and datafile system tables. 2022-12-28 17:50:07 140576082810752 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. 2022-12-28 17:50:07 7fda6b7ad780 InnoDB: Assertion failure in thread 140576082810752 in file dict0crea.cc line 1903 InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS 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.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. |
于涛 |
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 可以参考这个mysql官网手册尝试在数据库配置文件里将forcing-innodb-recovery相关配置改下值看下 |
ygx
|
这个已经试过了 结果还是一样
|
于涛 |
innodb_force_recovery =1 这个参数范围是1-6 ,1不行的话,可以考虑逐步增加参数值试一下。 |
1/1
1