InnoDB: Unable to lock ./ibdata1, error: 11
We have a few systems that use NFS one of which is installed on a NetAPP appliance. When MySQL shuts down the ibdata files remain locked so when it start up again the files are already locked and the database is locked. We do a work around which is moving ibdata1 and ibdata2 and copying them back. It looks like the unlocking on shutdown doesn't occur because of the order of PID's conflicting with file locks. Are there innodb variables that can get set to fall within the timing paremeters to allow for latencies from NFS?
Subject
Views
Written By
Posted
InnoDB: Unable to lock ./ibdata1, error: 11
11622
December 09, 2008 02:25PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.