Bug #54650 ndbd --initial failed because copyfrag failed
Submitted: 21 Jun 2010 3:25 Modified: 25 May 2012 10:32
Reporter: 小华 谭 Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:mysql-cluster-com-7.0.7-linux-x86_64-gli OS:Linux (SLES 10 SP2)
Assigned to: CPU Architecture:Any
Tags: ndbd copyfrag failed

[21 Jun 2010 3:25] 小华 谭
#cat ndb_3_error.log 
Current byte-offset of file-pointer is: 568                       

Time: Friday 18 June 2010 - 08:31:08
Status: Temporary error, restart node
Message: System error, node killed during node restart by other node (Internal error, programming error or missing error message, please report a bug)
Error: 2303

Error data: Killed by node 3 as copyfrag failed, error: 744
Error object: NDBCNTR (Line: 263) 0x0000000e
Program: ndbd
Pid: 10707
Trace: /DD3/ndb_3_trace.log.1
Version: mysql-5.1.35 ndb-7.0.7

How to repeat:
ndbd --initial 
can repeat this bug
[21 Jun 2010 3:30] 小华 谭
version: mysql-cluster-com-7.0.7-linux-x86_64-glibc23
         total 2 data nodes
[21 Jun 2010 8:34] Sveta Smirnova
Thank you for the report.

I can not repeat described behavior. Do you run ndbd --initial on empty dir? Please provide your configuration files also.
[21 Jul 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[25 May 2012 10:32] Gustaf Thorslund
Logs would have been useful, but from what I can see this looks like a duplicate of bug 40312: