when removed the ibdata1 it worked, and I cant understand how it happened. I checked with ps and there was no mysql process. also permissions were ok. Is there a way to check the integrity of this file?
Asked
Active
Viewed 1.6k times
0
-
This really belongs on serverfault.com, but normally this means you still have a (possibly corrupt) mysql process running. Check `ps` & possibly kill those processes. Although usually a graceful stop (`/etc/init.d/mysql stop`) would be prefered. – Wrikken Aug 05 '10 at 13:52
4 Answers
1
this is one of the issue using NFS for MySQL , one quick solution can be found on
http://onaxer.com/blog/blog/2010/06/01/innodb-unable-to-lock-ibdata1-error-37/
Pankaj Joshi
- 42
- 2
0
Did you restart mysql with the wrong user at some point? What were the permissions on the file and the directory it was in?
Paul Tomblin
- 179,021
- 58
- 319
- 408
0
I guess some other process is talking to this resource/file you don't have the right permissions on that file.
You could restart the computer as an easy solution.
If that does not help, you need to find out out who else is using that file.
But first, check permissions.
Itay Moav -Malimovka
- 52,579
- 61
- 190
- 278