MySQL Bugs: #7937: ndb_restore crashes with core-dump

Bug #7937	ndb_restore crashes with core-dump
Submitted:	16 Jan 2005 11:20	Modified:	17 Jan 2005 13:18
Reporter:	Andreas Dolleschal	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1.9	OS:	HP/UX (hpux 11.23 (64bit))
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
if one tries to restore a previous created backup-file with ndb_restore, the restore process creates a coredump.

How to repeat:
.) start ndb_mgmd
.) start ndbd with parameter --initial twice
.) start mysqld
.) create db
.) load data-file into created db
.) submit command "start backup" with ndb_mgm

.) shutdown complete node with command "shutdown" from ndb_mgm
.) start ndb_mgmd
.) start ndbd with parameter --initial twice
.) change to BACKUP directory
.) submit command "ndb_restore -b 1 -r -m -n 1" to restore the previous created backup-file

unable to reproduce on a:

> uname -a
HP-UX hpita2 B.11.23 U ia64 0369260763 unlimited-user license

- Can you give some more info about your platform? E.g. processor.
- Can you please provide the data-file you used, or some other dataset that reproduces the error?

I will try again as soon as I get this info.

Below is the mysqldump of the simple test we did.  Please try if you can have a database with only this, backup and restore it.

-- MySQL dump 10.9
--
-- Host: localhost    Database: test
-- ------------------------------------------------------
-- Server version       4.1.9-pro-log

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE="NO_AUTO_VALUE_ON_ZERO" */;

--
-- Table structure for table `t1`
--

DROP TABLE IF EXISTS `t1`;
CREATE TABLE `t1` (
  `a` int(11) NOT NULL default '0',
  `b` int(11) default NULL,
  PRIMARY KEY  (`a`)
) ENGINE=ndbcluster DEFAULT CHARSET=latin1;

--
-- Dumping data for table `t1`
--

/*!40000 ALTER TABLE `t1` DISABLE KEYS */;
LOCK TABLES `t1` WRITE;
INSERT INTO `t1` VALUES (1,1),(45,2),(3,1),(7,1),(5,1),(6,1),(2,1),(8,1),(10,1),(9,1);
UNLOCK TABLES;
/*!40000 ALTER TABLE `t1` ENABLE KEYS */;

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

ndb_restore with bug fix for Bug#7937

Attachment: ndb_pid27439_error.log (application/octet-stream, text), 468 bytes.

you can download a replacement ndb_restore with bug fixed at:

ftp://ftp.mysql.com/pub/mysql/download/ndb_restore-4.1.9-hp-hpux11.23-ia64-64bit.tar.gz