MySQL doesn't start. Here the logs:
071004 10:33:05 mysqld started
071004 10:33:05 [Warning] Asked for 196608 thread stack, but got 126976
InnoDB: Unable to lock /data/mysql/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Error in opening /data/mysql/ibdata1
071004 10:33:05 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: 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!
071004 10:33:05 [ERROR] Can't init databases
071004 10:33:05 [ERROR] Aborting
071004 10:33:05 [Note] /usr/sbin/mysqld: Shutdown complete
071004 10:33:05 mysqld ended
We've found any information about this issue. The warning above suggests to delete the new ibdata files, but our files have a huge size (4Go) and we would like not to delete our precious data...
-rw-rw---- 1 mysql mysql 3.9G Oct 3 15:30 /data/mysql/ibdata1
-rw-rw---- 1 mysql mysql 3.9G Oct 3 14:42 /data/mysql/ibdata2
-rw-rw---- 1 mysql mysql 3.9G Oct 3 14:42 /data/mysql/ibdata3
-rw-rw---- 1 mysql mysql 3.9G Oct 3 14:42 /data/mysql/ibdata4
-rw-rw---- 1 mysql mysql 3.9G Oct 3 14:42 /data/mysql/ibdata5
-rw-rw---- 1 mysql mysql 10M Oct 2 13:12 /data/mysql/ibdata6
-rw-rw---- 1 mysql mysql 100M Oct 3 15:30 /data/mysql/ib_logfile0
-rw-rw---- 1 mysql mysql 100M Oct 3 15:35 /data/mysql/ib_logfile1
Maybe a clue, remaining space disk on MySQL data partition becomes short:
Filesystem Size Used Avail Use% Mounted on
/dev/sdc2 42G 34G 5.9G 86% /data
We are aware of this lack of space, and we'll solve it sooner as possible; can it be directly the cause of the innodb issue?
Thanks for your help!