MySQL 无法启动
自己服务器的虚拟主机管理平台无法访问,我ssh上服务器,查看到mysql没有启动,启动mysql时报错。于是查看下日志,之前没有看出来,细看时才看到,以下是其中重要的一段日志。
111116 13:12:09 mysqld started
111116 13:12:09 bdb: write: 0xb6bdbf78, 32: No space left on device
111116 13:12:09 bdb: PANIC: No space left on device
111116 13:12:09 bdb: txn_checkpoint: log failed at LSN [1 253936] DB_RUNRECOVERY: Fatal error, run database recovery
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that’s ok, if not, decrease some variables in the equation
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…
Bogus stack limit or frame pointer, fp=0xbfffb504, stack_bottom=0x6d726567, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort…
thd->query at 0x206b6267 is invalid pointer
thd->thread_id=12849
No space left on device,磁盘空间不足呀。df -h查看下,var用了100%,我把maillog清空了,有10G。