Bug #36571 | Restore hangs for database size of 33K and more | ||
---|---|---|---|
Submitted: | 7 May 2008 16:38 | Modified: | 9 Jun 2008 12:20 |
Reporter: | Hema Sridharan | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
Version: | mysql-6.0-backup | OS: | Linux (SUSE 64-bit) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[7 May 2008 16:38]
Hema Sridharan
[12 May 2008 20:48]
Sveta Smirnova
Thank you for the report. I can not repeat described behavior with test data. Could you please provide dump of problem database?
[12 May 2008 21:30]
Hema Sridharan
I created the script that is attached to generate bigger database. Need to change the relevant socket path in $sock_path and can also change the values of $bid and $i as required to create huge database. Once the test is run, perform Restore manually in mysql prompt like Restore from '/tmp/b2';
[13 May 2008 5:41]
Rafal Somla
I'm reasonably sure that this problem is caused by issues reported in BUG#36624 and BUG#36586. In that case it is a duplicate of BUG#34701.
[14 May 2008 4:35]
Hema Sridharan
I don't think its duplicate of the bug mentioned.
[15 May 2008 19:01]
Sveta Smirnova
Thank you for the feedback. Verified as described. Bug is only repeatable on 64-bit machine.
[6 Jun 2008 9:55]
Øystein Grøvlen
If I apply the fix outlined in BUG#36586, I no longer get a hang. Instead, I get:ERROR 1698 (HY000): Error when reading summary section of backup image.
[9 Jun 2008 12:20]
Øystein Grøvlen
I have verified that the proposed fix for bug#36624 fixes fixes this.