2017-08-31 14:18:05 4122 [Note] InnoDB:
Database
was
not
shutdown normally!
2017-08-31 14:18:05 4122 [Note] InnoDB: Starting crash recovery.
2017-08-31 14:18:05 4122 [Note] InnoDB: Reading tablespace information
from
the .ibd files...
2017-08-31 14:18:05 4122 [ERROR] InnoDB: Attempted
to
open
a previously opened tablespace. Previous tablespace dev/tb_test uses spac
e ID: 1
at
filepath: ./dev/tb_test.ibd. Cannot
open
tablespace mysql/innodb_table_stats which uses
space
ID: 1
at
filepath: ./mysql/
innodb_table_stats.ibd
2017-08-31 14:18:05 2ad861898590 InnoDB: Operating system error number 2
in
a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must
create
InnoDB: directories yourself, InnoDB does
not
create
them.
InnoDB: Error: could
not
open
single-
table
tablespace file ./mysql/innodb_table_stats.ibd
InnoDB: We do
not
continue
the crash recovery, because the
table
may becomeInnoDB: corrupt if we cannot apply the log records
in
the InnoDB log
to
it.
InnoDB:
To
fix the problem
and
start mysqld:
InnoDB: 1) If there
is
a permission problem
in
the file
and
mysqld cannot
InnoDB:
open
the file, you should
modify
the permissions.
InnoDB: 2) If the
table
is
not
needed,
or
you can restore it
from
a backup,
InnoDB:
then
you can remove the .ibd file,
and
InnoDB will do a normal
InnoDB: crash recovery
and
ignore
that
table
.
InnoDB: 3) If the file system
or
the disk
is
broken,
and
you cannot remove
InnoDB: the .ibd file, you can
set
innodb_force_recovery > 0
in
my.cnf
InnoDB:
and
force
InnoDB
to
continue
crash recovery here.
150126 14:18:06 mysqld_safe mysqld
from
pid file /home/mysql/mysql_app/dbdata/liuyazhuang136.pid ended