Rechercher dans le manuel MySQL
15.20.1 Troubleshooting InnoDB I/O Problems
The troubleshooting steps for InnoDB
I/O
problems depend on when the problem occurs: during startup of the
MySQL server, or during normal operations when a DML or DDL
statement fails due to problems at the file system level.
Initialization Problems
If something goes wrong when InnoDB
attempts to
initialize its tablespace or its log files, delete all files
created by InnoDB
: all
ibdata
files and all
ib_logfile
files. If you already created some
InnoDB
tables, also delete any
.ibd
files from the MySQL database
directories. Then try the InnoDB
database
creation again. For easiest troubleshooting, start the MySQL
server from a command prompt so that you see what is happening.
Runtime Problems
If InnoDB
prints an operating system error
during a file operation, usually the problem has one of the
following solutions:
Make sure the
InnoDB
data file directory and theInnoDB
log directory exist.Make sure mysqld has access rights to create files in those directories.
Make sure mysqld can read the proper
my.cnf
ormy.ini
option file, so that it starts with the options that you specified.Make sure the disk is not full and you are not exceeding any disk quota.
Make sure that the names you specify for subdirectories and data files do not clash.
Doublecheck the syntax of the
innodb_data_home_dir
andinnodb_data_file_path
values. In particular, anyMAX
value in theinnodb_data_file_path
option is a hard limit, and exceeding that limit causes a fatal error.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-error-creating-innodb.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.