MySQL не запускается - Unable to lock ./ibdata1, error: 11

:: Stopping MySQL Server                                                 [FAIL] 
:: Starting MySQL Server                                                 [FAIL] 

111024 22:14:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
111024 22:14:49 InnoDB: The InnoDB memory heap is disabled
111024 22:14:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111024 22:14:49 InnoDB: Compressed tables use zlib 1.2.5
111024 22:14:49 InnoDB: Initializing buffer pool, size = 128.0M
111024 22:14:49 InnoDB: Completed initialization of buffer pool
111024 22:14:49 InnoDB: highest supported file format is Barracuda.
111024 22:14:49  InnoDB: Waiting for the background threads to start
111024 22:14:50 InnoDB: 1.1.8 started; log sequence number 3327631
111024 22:14:50 [Note] Event Scheduler: Loaded 0 events
111024 22:14:50 [Note] /usr/bin/mysqld: ready for connections.
Version: '5.5.16-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  Source distribution
111027 18:25:25 [ERROR] /usr/bin/mysqld: Disk is full writing './hpclub/ibf_posts.MYD' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
111027 18:25:25 [ERROR] /usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111027 18:25:46 [ERROR] /usr/bin/mysqld: Incorrect key file for table '/tmp/#sql_3b5_0.MYI'; try to repair it
111027 18:25:46 [ERROR] Got an error from unknown thread, /build/src/mysql-5.5.16/storage/myisam/mi_write.c:223
111027 18:25:47 [ERROR] /usr/bin/mysqld: Incorrect key file for table '/tmp/#sql_3b5_0.MYI'; try to repair it
111027 18:25:47 [ERROR] Got an error from unknown thread, /build/src/mysql-5.5.16/storage/myisam/mi_write.c:223
111027 18:25:47 [ERROR] /usr/bin/mysqld: Incorrect key file for table '/tmp/#sql_3b5_0.MYI'; try to repair it
111027 18:25:47 [ERROR] Got an error from unknown thread, /build/src/mysql-5.5.16/storage/myisam/mi_write.c:223
111027 18:26:25 [ERROR] /usr/bin/mysqld: Disk is full writing './mysql-bin.000012' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
111027 18:26:25 [ERROR] /usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111027 18:36:25 [ERROR] /usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111027 18:44:25 [ERROR] /usr/bin/mysqld: Disk is full writing './mysql-bin.000012' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
111027 18:44:25 [ERROR] /usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111027 18:45:25 [ERROR] /usr/bin/mysqld: Disk is full writing './mysql-bin.000012' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
111027 18:45:25 [ERROR] /usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111027 18:55:25 [ERROR] /usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111027 19:00:26 [Note] /usr/bin/mysqld: Normal shutdown
111027 19:00:26 [Note] Event Scheduler: Purging the queue. 0 events
111027 19:00:28 [Warning] /usr/bin/mysqld: Forcing close of thread 100540  user: 'WebDevelopment'
111027 19:00:28 [Warning] /usr/bin/mysqld: Forcing close of thread 99722  user: 'WebDevelopment'
111027 19:00:28 [Warning] /usr/bin/mysqld: Forcing close of thread 99624  user: 'root'
111027 19:01:25 [ERROR] Error writing file 'mysql-bin' (errno: 28)
111027 19:01:25 [ERROR] Error writing file 'mysql-bin' (errno: 28)
111027 19:01:26 [ERROR] /usr/bin/mysqld: Incorrect key file for table './hpclub/ibf_posts.MYI'; try to repair it
111027 19:03:50 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
111027 19:03:50 InnoDB: The InnoDB memory heap is disabled
111027 19:03:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111027 19:03:50 InnoDB: Compressed tables use zlib 1.2.5
111027 19:03:50 InnoDB: Initializing buffer pool, size = 128.0M
111027 19:03:50 InnoDB: Completed initialization of buffer pool
111027 19:03:50 InnoDB: highest supported file format is Barracuda.
111027 19:03:50  InnoDB: Waiting for the background threads to start
111027 19:03:51 InnoDB: 1.1.8 started; log sequence number 3327631
111027 19:03:51 [Note] Recovering after a crash using mysql-bin
111027 19:03:51 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 1044014, event_type: 2
111027 19:03:51 [Note] Starting crash recovery...
111027 19:03:51 [Note] Crash recovery finished.
111027 19:03:52 [Note] Event Scheduler: Loaded 0 events
111027 19:03:52 [Note] /usr/bin/mysqld: ready for connections.
Version: '5.5.16-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  Source distribution
111028 19:25:31 [Note] /usr/bin/mysqld: Normal shutdown
111028 19:25:31 [Note] Event Scheduler: Purging the queue. 0 events
111028 19:25:31  InnoDB: Starting shutdown...
111028 19:25:33  InnoDB: Shutdown completed; log sequence number 3327641
111028 19:25:33 [Note] /usr/bin/mysqld: Shutdown complete
111028 19:25:33 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended
111028 19:25:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
111028 19:25:49 InnoDB: The InnoDB memory heap is disabled
111028 19:25:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111028 19:25:49 InnoDB: Compressed tables use zlib 1.2.5
111028 19:25:49 InnoDB: Initializing buffer pool, size = 128.0M
111028 19:25:49 InnoDB: Completed initialization of buffer pool
111028 19:25:49 InnoDB: highest supported file format is Barracuda.
111028 19:25:49  InnoDB: Waiting for the background threads to start
111028 19:25:50 InnoDB: 1.1.8 started; log sequence number 3327641
/usr/bin/mysqld: Disk is full writing './mysql-bin.~rec~' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111028 19:27:45 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
111028 19:27:45 InnoDB: The InnoDB memory heap is disabled
111028 19:27:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111028 19:27:45 InnoDB: Compressed tables use zlib 1.2.5
111028 19:27:45 InnoDB: Initializing buffer pool, size = 128.0M
111028 19:27:45 InnoDB: Completed initialization of buffer pool
111028 19:27:45 InnoDB: highest supported file format is Barracuda.
111028 19:27:45  InnoDB: Waiting for the background threads to start
111028 19:27:46 InnoDB: 1.1.8 started; log sequence number 3327641
/usr/bin/mysqld: Disk is full writing './mysql-bin.~rec~' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111028 20:05:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
111028 20:05:25 InnoDB: The InnoDB memory heap is disabled
111028 20:05:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111028 20:05:25 InnoDB: Compressed tables use zlib 1.2.5
111028 20:05:25 InnoDB: Initializing buffer pool, size = 128.0M
111028 20:05:25 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
111028 20:05:25  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error111028 20:07:05 mysqld_safe mysqld from pid file /var/lib/mysql//.pid ended
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs
111028 20:38:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
111028 20:38:34 [Warning] option 'net_buffer_length': unsigned value 8388608 adjusted to 1048576
111028 20:38:34 InnoDB: The InnoDB memory heap is disabled
111028 20:38:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111028 20:38:34 InnoDB: Compressed tables use zlib 1.2.5
111028 20:38:34 InnoDB: Initializing buffer pool, size = 128.0M
111028 20:38:34 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
111028 20:38:34  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to 111028 20:40:14 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended
/usr/bin/mysqld: Retry in 60 secs. Message reprinted in 600 secs

Как это исправить?

cat my.cnf 
# MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# MySQL programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, see:
# http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MySQL clients
[client]
#password	= your_password
port		= 3306
socket		= /var/run/mysqld/mysqld.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port		= 3306
socket		= /var/run/mysqld/mysqld.sock
datadir		= /var/lib/mysql
skip-external-locking
key_buffer_size = 512M
max_allowed_packet = 10M
table_open_cache = 64
sort_buffer_size = 20M
net_buffer_length = 8M
read_buffer_size = 256M
read_rnd_buffer_size = 512M
myisam_sort_buffer_size = 8M
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
skip-networking
# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin
# binary logging format - mixed recommended
binlog_format=mixed
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id	= 1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
Обратите внимание на эту строчку вашего лога:
111027 18:25:25 /usr/bin/mysqld: Disk is full writing ‘./hpclub/ibf_posts.MYD’ (Errcode: 28). Waiting for someone to free space… (Expect up to 60 secs delay for server to continue after freeing disk space)
 
Зарегистрироваться или войдите чтобы оставить сообщение.