Percona Server moved to https://jira.percona.com/projects/PS

  1. Bug #1246916
  2. Comment #5

Comment 5 for bug 1246916

Revision history for this message
Przemek (pmalkowski) wrote :

I have seen very similar crash in a case where MySQL data directory was located on a NFS share. After the MySQL server host was rebooted (not clean reboot), MySQL could not gain write permissions (error 11) to some files despite the fact that from OS level all seemed right. Only copying each file out and back in resolved the access/locking problem.
This is example crash:

InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Unable to lock ./db/table#P#p1#SP#p1sp0.ibd, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
140110 13:22:45 InnoDB: Assertion failure in thread 140545018697664 in file fil0fil.c line 844
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.

Happened on Percona Server 5.5.34-32.0-log