Bug #22667 Unable to lock /REP_MYSQL/mysql/innodb_file/ibdata1, error: 11
Submitted: 25 Sep 2006 15:08 Modified: 27 Sep 2006 7:54
Reporter: Jean-François BEAUD Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.22 OS:Linux (Linux 2.6.8.1-25mdkenterprise)
Assigned to: CPU Architecture:Any
Tags: InnoDB: using the same InnoDB data or log files.

[25 Sep 2006 15:08] Jean-François BEAUD
Description:

* mysqld_install_db   : OK
* mysqld_safe         : OK
* mysqladmin shutdown : OK
* mysqld_safe         : NOK

Cf. host.err 
<<<<<<<<<<<<<<
060925 13:47:16  mysqld started
InnoDB: The first specified data file /REP_MYSQL/mysql/innodb_file/ibdata1 did not exist:
InnoDB: a new database to be created!
060925 13:47:16  InnoDB: Setting file /REP_MYSQL/mysql/innodb_file/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060925 13:47:17  InnoDB: Log file /REP_MYSQL/mysql/innodb_log/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /REP_MYSQL/mysql/innodb_log/ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060925 13:47:18  InnoDB: Log file /REP_MYSQL/mysql/innodb_log/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /REP_MYSQL/mysql/innodb_log/ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060925 13:47:19  InnoDB: Log file /REP_MYSQL/mysql/innodb_log/ib_logfile2 did not exist: new to be created
InnoDB: Setting log file /REP_MYSQL/mysql/innodb_log/ib_logfile2 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
060925 13:47:20  InnoDB: Started; log sequence number 0 0
060925 13:47:20 [Note] /logiciel/mysql/5.0.22/libexec/mysqld: ready for connections.
Version: '5.0.22-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
060925 13:48:08 [Note] /logiciel/mysql/5.0.22/libexec/mysqld: Normal shutdown

060925 13:48:08  InnoDB: Starting shutdown...
060925 13:48:10  InnoDB: Shutdown completed; log sequence number 0 43655
060925 13:48:10 [Note] /logiciel/mysql/5.0.22/libexec/mysqld: Shutdown complete

060925 13:48:10  mysqld ended

060925 13:48:31  mysqld started
InnoDB: Unable to lock /REP_MYSQL/mysql/innodb_file/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
060925 13:48:31  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock /REP_MYSQL/mysql/innodb_file/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 /REP_MYSQL/mysql/innodb_file/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 /REP_MYSQL/mysql/innodb_file/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 /REP_MYSQL/mysql/innodb_file/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 /REP_MYSQL/mysql/innodb_file/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 /REP_MYSQL/mysql/innodb_file/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 /REP_MYSQL/mysql/innodb_file/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
060925 13:50:11  InnoDB: Unable to open the first data file
InnoDB: Error in opening /REP_MYSQL/mysql/innodb_file/ibdata1
060925 13:50:11  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
060925 13:50:11 [Note] /logiciel/mysql/5.0.22/libexec/mysqld: ready for connections.
Version: '5.0.22-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
060925 15:14:57 [Note] /logiciel/mysql/5.0.22/libexec/mysqld: Normal shutdown

060925 15:14:57 [Note] /logiciel/mysql/5.0.22/libexec/mysqld: Shutdown complete

060925 15:14:57  mysqld ended
>>>>>>>>>>>>>>

How to repeat:

See before.

Suggested fix:

/REP_MYSQL/mysql/... : is on NFS file system !?
No problem when "/REP_MYSQL/mysql/..." is on local disk.
[25 Sep 2006 15:14] Jean-François BEAUD
My MySQL config file :

>>>>>>>>>>>>>>>>>>>
# Example MySQL config file for large systems.
#
# This is for a large system with memory = 512M where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# 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]
user            = root
password        = xxxxxxx
port		= 3306
socket		= /tmp/mysql.sock

# SET PASSWORD FOR root@localhost = Password('m_sql');
# SET PASSWORD FOR root@"host" = Password('m_sql');
# SELECT u.user, u.password, u.host FROM user u;
# DELETE FROM user WHERE user='';
# DELETE FROM db d WHERE d.user='';
# FLUSH PRIVILEGES;

# db MySQL dediee ...
[mysql]
database        = mysql

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port		= 3306
socket		= /tmp/mysql.sock
skip-locking
key_buffer = 256M
max_allowed_packet = 1M
table_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

# 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=/TRIDEM/mysql/JournalDesMisesAJour/mysql-bin

# 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

# Point the following paths to different dedicated disks
#tmpdir		= /tmp/		
#log-update 	= /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 64M
#bdb_max_lock = 100000

#Uncomment the following if you are using InnoDB tables
#Repertoire ou sont stockes les fichiers InnoDB
innodb_data_home_dir = /TRIDEM/mysql/innodb_file
#Parametre a ne positionner que si innodb_file_per_table = 0 !
#innodb_data_file_path = ibdata1:10M:autoextend
#Repertoire des journaux de transactions...
innodb_log_group_home_dir = /TRIDEM/mysql/innodb_log
#Nombre de fichiers journaux de transactions
innodb_log_files_in_group = 3
# Taille de chaque fichier du journal des transactions
innodb_log_file_size = 10M
#innodb_log_arch_dir = /usr/local/mysql/data/
#You can set .._buffer_pool_size up to 50 - 80 %
#of RAM but beware of setting memory usage too high
#Cache des donnees et index
innodb_buffer_pool_size = 64M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 64M
#innodb_log_buffer_size = 8M
# Indique que le buffer du journal doit etre descendu sur le disque au moment d'un commit
innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
# Une table <=> Un fichier
innodb_file_per_table = 1

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
<<<<<<<<<<<<<<<<<<<
[27 Sep 2006 7:54] Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

See also bug #14281