14.2.5.1. Dealing with InnoDB Initialization Problems
If InnoDB prints an operating system error
during a file operation, usually the problem has one of the
following causes:
You did not create the InnoDB data file
directory or the InnoDB log directory.
mysqld does not have access rights to
create files in those directories.
mysqld cannot read the proper
my.cnf or my.ini
option file, and consequently does not see the options that
you specified.
The disk is full or a disk quota is exceeded.
You have created a subdirectory whose name is equal to a
data file that you specified, so the name cannot be used as
a filename.
There is a syntax error in the
innodb_data_home_dir or
innodb_data_file_path value.
If something goes wrong when InnoDB attempts
to initialize its tablespace or its log files, you should delete
all files created by InnoDB. This means all
ibdata files and all
ib_logfile files. In case you have already
created some InnoDB tables, delete the
corresponding .frm files for these tables
(and any .ibd files if you are using
multiple tablespaces) from the MySQL database directories as
well. Then you can try the InnoDB database
creation again. It is best to start the MySQL server from a
command prompt so that you see what is happening.
