mandag den 6. juni 2016

Error 37 and 11 on a MYSQL (CentOS) after we moved data to nfs.

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

Solution: 
1) killed the lingering mysql process
2) mv (move) ibdata1 file to ibdata1.bad
3) cp -a ibdata1.bad ibdata1
4) restart the db server or just type: reboot

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

We faced the “error  InnoDB: Unable to lock ./ibdata1, error: 37 “ while moving my data directory from a SAN to a NFS on a local disk , when we restarted the mysql , the restart failed and we got the error in the error log , all permissions are set properly.

Solution: 
1) Add nolock option into nfs mount entry in /etc/fstab and just type : reboot
-optional-
2) /etc/init.d/portmap restart
3) /etc/init.d/nfslock restart