Documentation Home
MySQL 9.4 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 41.2Mb
PDF (A4) - 41.3Mb
Man Pages (TGZ) - 262.8Kb
Man Pages (Zip) - 368.8Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb


MySQL 9.4 Reference Manual  / ...  / The InnoDB Storage Engine  / InnoDB Troubleshooting  /  Troubleshooting InnoDB I/O Problems

17.20.1 Troubleshooting InnoDB I/O Problems

The troubleshooting steps forInnoDB 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 whenInnoDB attempts to initialize its tablespace or its log files, delete all files created byInnoDB: allibdata files and all redo log files (#ib_redoN files). If you created anyInnoDB tables, also delete any.ibd files from the MySQL database directories. Then try initializingInnoDB again. For easiest troubleshooting, start the MySQL server from a command prompt so that you see what is happening.

Runtime Problems

IfInnoDB prints an operating system error during a file operation, usually the problem has one of the following solutions:

  • Make sure theInnoDB data file directory and theInnoDB log directory exist.

  • Make suremysqld has access rights to create files in those directories.

  • Make suremysqld can read the propermy.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 theinnodb_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.