Bug #17999 DD: Restore db to the directory that does not exist fails with unknown error.
Submitted: 6 Mar 2006 22:35 Modified: 24 May 2006 19:52
Reporter: Nikolay Grishakin Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:5.1 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[6 Mar 2006 22:35] Nikolay Grishakin
Description:
Restore database to the directory that does not exist fails with the following error:
"Nodeid = 2
Backup Id = 1
backup path = /space/run
Ndb version in backup files: Version 5.1.8
Connected to ndb!!
Creating logfile group: TPCB_LOG...FAILED701: System busy with other schema operation
Restore: Failed to restore table: sys/def/SYSTAB_0 ... Exiting
NDBT_ProgramExit: 1 - Failed"

ndb_mgm reported the following error:
"ndb_mgm> Node 2: Forced node shutdown completed. Initiated by signal 0. Caused by error 2815: 'File not found(Ndbd file system inconsistency error, please report a bug). Ndbd file system error, restart node initial'."

How to repeat:
1. I used 1 node groups cluster configuration (see 1nd.ini file) and populated
TPCB database using load_tpcb.pl script. To do that log in to ndb 15:
ssh ndb 15
cd /home/ndbdev/ngrishakin
execute: . ./shortcuts.sh
execute: $ndb_mgmd -f 1nd.ini
Start server: $mysql_server start

2. Start ndbd on each machine ndb14 and ndb13: ndbd -c ndb15:14000

3. Run load_tpcb.pl script on ndb15:
[ndbdev@ndb15 ngrishakin]$ perl load_tpcb.pl NDB15 3306 root BLANK ndb_mix

6. After it finishes run BACKUP on ndb15: ndb_mgm ndb15:14000 -e "start backup"

7. Shut down ndb_mgmd and mySQL server on ndb15 and ndbd on all nodes.

8. Copy backup files from ndb13:/space/run/BACKUP/BACKUP-1/* and 
ndb14:/space/run/BACKUP/BACKUP-1/* to ndb15:/space/run/
$rm -rf /space/run/*

9. Restart cluster. Repeat steps 1 and 2.

10. On ndb14 remove /space/run directory.

11. Try to restore: 
[ndbdev@ndb15 ngrishakin]$ ndb_restore -c ndb15:14000 -n 2 -b 1 -m -r /space/run
[24 May 2006 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".