Bug #42886 ndb_restore output should be clearer when backup file was not found

• Submitted: 16 Feb 2009 15:19
• Modified: 12 Apr 2015 11:57
• Reporter: Geert Vanderkelen
• Status: Verified
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S4 (Feature request)
• Version: mysql-5.1-telco-6.3
• OS: Any
• CPU Architecture: Any
• Tags: mysql-5.1.31-telco-6.3.22, ndb, restore

[16 Feb 2009 15:19] Geert Vanderkelen

Description:
(spin off for bug #42880)
Currently, when a backup file is not found a system error 9 "Bad File Descriptor" is returned. Although correct, it's quite cryptic for the user.

How to repeat:
shell> ndb_restore -n 4 -b 1 -m -r
backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/
Nodeid = 4
Backup Id = 1
backup path = backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/
Opening file
'backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/BACKUP-1.4.ctl'
Progress reporting degraded output since fstat failed,errno: 9
Failed to read
backup_path=/data2/users/geert/cluster/master/BACKUP/BACKUP-1/BACKUP-1.4.ctl

Suggested fix:
Limit the output, verify first, and give an error. Maybe add a more stuff using --verbose ?

shell> ndb_restore -n 4 -b 1 -m -r /path/to/something/odd/
File not found: /path/to/something/odd/BACKUP-1.4.ctl