MySQL Bugs: #40089: ndbd fails to start after hard kill due to corrupt Dbdict.

Bug #40089	ndbd fails to start after hard kill due to corrupt Dbdict.
Submitted:	16 Oct 2008 20:19	Modified:	4 Oct 2009 12:58
Reporter:	Matthew Montgomery	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-7.0	OS:	Linux
Assigned to:	Assigned Account	CPU Architecture:	Any

File:	Maximum allowed size is 3MB.
Description:
Privacy:

If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-40089.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
Log in with your newly created Oracle Web account (email address) and password.
Upload the archive to /support/incoming.
Once you have uploaded the file, add a comment to this bug to notify us about it.

Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

Trace log file

Attachment: 40089_traces.tgz (application/x-compressed-tar, text), 104.22 KiB.

my traces

Attachment: 40089_traces_theodor_reppe.tar.gz (application/x-gzip, text), 125.75 KiB.