MySQL服务器崩溃了,无法启动实例

时间:2018-12-10 23:03:19

标签: mysql mysqli mysql-workbench

我的情况是我的驱动器空间已满,并且mysql实例崩溃了。我们已经扩展了存储空间并尝试在线启动服务,但出现以下错误,

2018-12-10T22:53:05.835471Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.18) starting as process 5754 ...
2018-12-10T22:53:05.840553Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-12-10T22:53:05.840599Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-12-10T22:53:05.840610Z 0 [Note] InnoDB: Uses event mutexes
2018-12-10T22:53:05.840620Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-12-10T22:53:05.840629Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-12-10T22:53:05.840642Z 0 [Note] InnoDB: Using Linux native AIO
2018-12-10T22:53:05.841126Z 0 [Note] InnoDB: Number of pools: 1
2018-12-10T22:53:05.841344Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2018-12-10T22:53:05.843531Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-12-10T22:53:05.856154Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-12-10T22:53:05.858870Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-12-10T22:53:05.873301Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-12-10T22:53:05.881677Z 0 [ERROR] InnoDB: Trying to access page number 4294967295 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
2018-12-10T22:53:05.881697Z 0 [ERROR] InnoDB: Server exits.

有人可以帮助解决这个问题吗?

谢谢

0 个答案:

没有答案