MySQL doesn't start after moving data files.
Hello everyone,
I was loading a large amount of data (300 GB) when I ran out of space. I then stopped mysql and changed my datadir to a different location, as follow:
1. stopped mysql
2. changed my my.cnf modifying datadir=/new/location
3. copied my mysql/ directory to new location.
4. started mydql. and I am getting this error:
2016-05-28 08:49:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-05-28 08:49:10 0 [Note] mysqld (mysqld 5.6.25) starting as process 14540 ...
2016-05-28 08:49:10 14540 [Note] Plugin 'FEDERATED' is disabled.
mysqld: Table 'plugin' is read only
2016-05-28 08:49:10 14540 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2016-05-28 08:49:10 14540 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-05-28 08:49:10 14540 [Note] InnoDB: The InnoDB memory heap is disabled
2016-05-28 08:49:10 14540 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-05-28 08:49:10 14540 [Note] InnoDB: Memory barrier is not used
2016-05-28 08:49:10 14540 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-05-28 08:49:10 14540 [Note] InnoDB: Using Linux native AIO
2016-05-28 08:49:10 14540 [Note] InnoDB: Not using CPU crc32 instructions
2016-05-28 08:49:10 14540 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-05-28 08:49:10 14540 [Note] InnoDB: Completed initialization of buffer pool
2016-05-28 08:49:10 14540 [Note] InnoDB: Highest supported file format is Barracuda.
2016-05-28 08:49:10 14540 [Note] InnoDB: 128 rollback segment(s) are active.
2016-05-28 08:49:10 14540 [Note] InnoDB: Waiting for purge to start
07:49:10 UTC - mysqld got signal 11 ;
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.
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68105 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x3b)[0x8e3a6b]
mysqld(handle_fatal_signal+0x491)[0x673f91]
/lib64/libpthread.so.0(+0xf130)[0x7fa78f011130]
mysqld(my_realpath+0x87)[0x8e0ce7]
mysqld(_Z19find_or_create_fileP10PFS_threadP14PFS_file_classPKcjb+0x9c)[0x90b83c]
mysqld[0x931c94]
mysqld[0xaf88ea]
mysqld[0xaf8f5c]
mysqld[0xb00a2b]
mysqld[0xac8f4b]
mysqld[0xaafb50]
mysqld[0xa94683]
mysqld[0xa39f38]
mysqld[0xa36add]
mysqld[0xa38747]
mysqld[0xa06f85]
mysqld[0xa5eb6e]
mysqld[0xa50b9c]
/lib64/libpthread.so.0(+0x7df5)[0x7fa78f009df5]
/lib64/libc.so.6(clone+0x6d)[0x7fa78dedb1ad]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Have I missed something? Please advise.