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

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 .
Thanks
Pankaj Joshi

This entry was posted on Tuesday, June 1st, 2010 at 2:26 pm and is filed under CentOS, Linux, Mysql, NFS. 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.

2 Responses to “InnoDB: Unable to lock ./ibdata1, error: 37”

  1. Prashant Says:
    July 28th, 2010 at 10:48 am

    Thanks Pankaj. This tip saved my day once again!

  2. pankaj Says:
    July 28th, 2010 at 5:20 pm

    good to see that its helpfull :)

Leave a Reply