|
2019-07-10 11:05:58 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2019-07-10 11:05:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2019-07-10 11:05:58 0 [Note] InnoDB: Uses event mutexes 2019-07-10 11:05:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 2019-07-10 11:05:58 0 [Note] InnoDB: Number of pools: 1 2019-07-10 11:05:58 0 [Note] InnoDB: Using SSE2 crc32 instructions 2019-07-10 11:05:58 0 [Note] InnoDB: Initializing buffer pool, total size = 64M, instances = 1, chunk size = 64M 2019-07-10 11:05:58 0 [Note] InnoDB: Completed initialization of buffer pool 2019-07-10 11:05:58 0 [Note] InnoDB: Setting file '.\ibdata1' size to 12 MB. Physically writing the file full; Please wait ... 2019-07-10 11:05:58 0 [Note] InnoDB: File '.\ibdata1' size is now 12 MB. 2019-07-10 11:05:58 0 [Note] InnoDB: Setting log file .\ib_logfile101 size to 16777216 bytes 2019-07-10 11:05:58 0 [Note] InnoDB: Setting log file .\ib_logfile1 size to 16777216 bytes 2019-07-10 11:05:58 0 [Warning] InnoDB: Retry attempts for writing partial data failed. 2019-07-10 11:05:58 0 [ERROR] InnoDB: Write to file .\ib_logfile101 failed at offset 0, 512 bytes should have been written, only 0 were written. Operating system error number 203. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded. 2019-07-10 11:05:58 0x2b54 InnoDB: Assertion failure in file d:\winx64-packages\build\src\storage\innobase\fil\fil0fil.cc line 4524 InnoDB: Failing assertion: req_type.is_dblwr_recover() || err == DB_SUCCESS InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 190710 11:05:58 [ERROR] mysqld got exception 0x80000003 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.3.8-MariaDB key_buffer_size=67108864 read_buffer_size=524288 max_used_connections=0 max_threads=65537 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 85620 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. |
|
|
沙发#
发布于：2019-07-10 20:40
配置有问题，参数设置太太太太大了，磁盘空间不能满足配置。建议面板找到备份和恢复，进去恢复到出厂配置。
|
|
