MySQL Bugs: #29972: The mysqlhotcopy script fails to copy tables or databases

Bug #29972	The mysqlhotcopy script fails to copy tables or databases
Submitted:	23 Jul 2007 8:31	Modified:	23 Jul 2007 11:41
Reporter:	Euan Hogg	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Backup	Severity:	S3 (Non-critical)
Version:	Ver 14.12 Distrib 5.0.41, for pc-linux-g	OS:	Linux (RHES4 Update 5)
Assigned to:		CPU Architecture:	Any

Description:
As per bug report http://bugs.mysql.com/bug.php?id=812

When mysqlhotcopy is run it reports it succeeds in creating the target ( database  or table ) then reports as having copied the source database to the target but the target database or directory is empty.

How to repeat:
./mysqlhotcopy m1 m2

or

./mysqlhotcopy m1 /scratch/m2

Locked 185 tables in 0 seconds.
Flushed tables (`m1`.`adodb_logsql`, `m1`.`m1assignment`, `m1`.`m1assignment_submissions`, `m1`.`m1backup_config`, `m1`.`m1backup_courses`, `m1`.`m1backup_files`, `m1`.`m1backup_ids`, `m1`.`m1backup_log`, `m1`.`m1block`, `m1`.`m1block_instance`,

cut for brevity

`m1`.`m1workshop_submissions`) in 0 seconds.
Copying 556 files...
Copying indices for 0 files...
Unlocked tables.
mysqlhotcopy copied 185 tables (556 files) in 0 seconds (1 seconds overall).
 
[root@moorh4 m1]# ls -l /scratch/m2/m1/
total 0

mysql> use m1
Database changed
mysql> show tables;
+--------------------------------+
| Tables_in_m1                   |
+--------------------------------+
| adodb_logsql                   | 
| m1assignment                   | 
| m1assignment_submissions       | 
| m1backup_config                | 
| m1backup_courses               | 

cut for brevity

| m1workshop_stockcomments       | 
| m1workshop_submissions         | 
+--------------------------------+
185 rows in set (0.01 sec)

mysql> use m2;
Database changed
mysql> show tables;
Empty set (0.00 sec)

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of Bug #28460