MySQL - InnoDB: Error number 37 means 'No locks available'

Ошибка вида:

InnoDB: Unable to lock ./admin_forum1/blog_blogs.ibd, error: 37
160519  6:44:58  InnoDB: Error creating file './admin_forum1/blog_blogs.ibd'. 
160519  6:44:58  InnoDB: Operating system error number 37 in a file operation.
InnoDB: Error number 37 means 'No locks available'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
160519  6:44:58  InnoDB: Error creating file './admin_forum1/blog_blogs.ibd'.
160519  6:44:58  InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file './admin_forum1/blog_blogs.ibd'
InnoDB: under the 'datadir' of MySQL. 
160519  6:44:58  InnoDB: Error creating file './admin_forum1/blog_blogs.ibd'.
160519  6:44:58  InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: The file already exists though the corresponding table did not

Решение - убрать опцию innodb_file_per_table из my.cnf и перезапустить mysql сервер.

Также такая ошибка может возникнуть из-за неправильного выделения памяти на VPS сервере с OpenVZ виртуализацией, поэтому обратитесь к Вашему хостинг провайдеру.