Comment 3 for bug 1434940

Thanks for referring to http://bugs.mysql.com/bug.php?id=65199. It is similar with differences, 1) the original case didn't involve server crash, 2)the last two cases that involves server crashed were caused by 'DROP TABLE'. In this case, the customer was accessing table sesame_db/ledger_versioned while the server complained about missing temp/ledger_versioned, and crashed.

The step that lead to the crash is: accessing sesame_db/ledger_versioned.

The import is mentioned as related information.

"ls -l in the database dir at each step etc": That data is not available. temp/ledger_versioned.frm is still there, per customer.

The error log can be considered full since import till the crash, the part skipped is just duplicated sections.

What do we know from the stack trace?

p.s. If the customer would agree to take this server out of production and try the drop table, we might get a core dump.