InnoDB: Unable to lock ./ibdata1, error: 37

June 1st, 2010 by Pankaj Joshi Leave a reply »

InnoDB: Unable to lock ./ibdata1, error: 37

I recently faced the “error  InnoDB: Unable to lock ./ibdata1, error: 37 “ while moving my data directory to NFS from local disk , when I restarted the mysql , the restart failed and I got the error in the error log , all permissions were set properly so I was not sure whats going wrong , I was sure that there is some problem with the OS not able to lock the file and it was related to NFS so I

1) /etc/init.d/portmap restart
2) /etc/init.d/nfslock restart

Restarted the mysql and it worked .

Posted in CentOS, Linux, Mysql, NFS

Tags:

You can follow any responses to this entry through the RSS 2.0 Feed. You can leave a response , or trackback from your own site.

Advertisement
  • Prashant

    Thanks Pankaj. This tip saved my day once again!

  • http://onaxer.com pankaj

    good to see that its helpfull :)

  • http://www.continuent.com Edward

    Thanks, Pankaj, saved the day.

  • http://onaxer.com/blog/blog/2011/02/23/innodb-unable-to-lock-ib_logfile0-error-11/ InnoDB: Unable to lock ./ib_logfile0, error: 11 | Nix World

    [...] (SSH2)” PHP ExtensionAntonio on Installing “Secure Shell2 (SSH2)” PHP ExtensionEdward on InnoDB: Unable to lock ./ibdata1, error: 37ery on Oracle 10g R2 installtion on CentOS 5.5/RHELTag Cloudadd mail aliases Apache apache + WebDav [...]

blog comments powered by Disqus