MYSQL启动不了，日志，可以帮看下吗

疯狂痴呆

lnmpa

1. 141230 22:50:02 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
   
2. 141230 22:50:02 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
   
3. 141230 22:50:02  InnoDB: Initializing buffer pool, size = 8.0M
   
4. 141230 22:50:02  InnoDB: Completed initialization of buffer pool
   
5. InnoDB: The log sequence number in ibdata files does not match
   
6. InnoDB: the log sequence number in the ib_logfiles!
   
7. 141230 22:50:02  InnoDB: Database was not shut down normally!
   
8. InnoDB: Starting crash recovery.
   
9. InnoDB: Reading tablespace information from the .ibd files...
   
10. InnoDB: Restoring possible half-written data pages from the doublewrite
    
11. InnoDB: buffer...
    
12. 141230 22:50:02  InnoDB: Started; log sequence number 0 44243
    
13. 14:50:02 UTC - mysqld got signal 11 ;
    
14. This could be because you hit a bug. It is also possible that this binary
    
15. or one of the libraries it was linked against is corrupt, improperly built,
    
16. or misconfigured. This error can also be caused by malfunctioning hardware.
    
17. We will try our best to scrape up some info that will hopefully help
    
18. diagnose the problem, but since we have already crashed,
    
19. something is definitely wrong and this may fail.
    
20. 
    
21. key_buffer_size=16777216
    
22. read_buffer_size=262144
    
23. max_used_connections=0
    
24. max_threads=151
    
25. thread_count=0
    
26. connection_count=0
    
27. It is possible that mysqld could use up to
    
28. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133331 K  bytes of memory
    
29. Hope that's ok; if not, decrease some variables in the equation.
    
30. 
    
31. Thread pointer: 0x0
    
32. Attempting backtrace. You can use the following information to find out
    
33. where mysqld died. If you see no messages after this, something went
    
34. terribly wrong...
    
35. stack_bottom = 0 thread_stack 0x30000
    
36. [0x839997e]
    
37. [0x81e2c44]
    
38. [0xb7740400]
    
39. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    
40. information that should help you find out what is causing the crash.
    
41. 141230 22:50:02 mysqld_safe mysqld from pid file /usr/local/mysql/var/debian.pid ended

复制代码

licess

首先检查硬盘或分区占用情况，再看https://bbs.vpser.net/thread-13040-1-1.html