Bug #73077 | truncate table might cause .ibd file lost if disk full | ||
---|---|---|---|
Submitted: | 23 Jun 2014 8:20 | Modified: | 8 Jul 2014 3:20 |
Reporter: | liu hickey (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.6.16+ | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | disk full, ibd lost, truncate table |
[23 Jun 2014 8:20]
liu hickey
[24 Jun 2014 8:06]
liu hickey
Ops, it's fixed in 5.7.2, seen from WL6501 http://dev.mysql.com/worklog/task/?id=6501 and ReleaseNote http://mysqlserverteam.com/the-mysql-5-7-2-milestone-release/ Major changes $ bzr diff -c6092 > wl6501.diff And related with bugfix $ bzr log | grep 6501 --color -C5
[27 Jun 2014 10:23]
MySQL Verification Team
Thank you for the report. Yes, this issue most likely fixed in 5.7.2 Please reopen the bug if you hit this issue in >5.7.2. Thanks, Umesh
[2 Jul 2014 2:55]
liu hickey
In theory, 5.7.2 fixed this issue, and you can close it now. For the 5.6 users, they can try this patch if needed.
[2 Jul 2014 2:55]
liu hickey
quick fix for bug73077 in 5.6
Attachment: bug73077.diff (application/octet-stream, text), 9.84 KiB.
[8 Jul 2014 3:20]
liu hickey
Close it as 5.7 has already fixed with more complex solution.