[MDEV-11656] 'Data structure corruption' IMPORT TABLESPACE doesn't work for encrypted InnoDB tables if space_id changed Created: 2016-12-23 Updated: 2017-01-03 Resolved: 2017-01-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.1.19 |
| Fix Version/s: | 10.1.21 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrii Nikitin (Inactive) | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Sprint: | 10.2.4-5 |
| Description |
|
So I do following actions on encrypted InnoDB : root@c480fbb475db:/test# mysql <<EOL If I don't drop the table inbetween - it works. ALTER TABLE t1 IMPORT TABLESPACE; CURRENT_TEST: encryption.innodb-discard-import-adv |
| Comments |
| Comment by Andrii Nikitin (Inactive) [ 2016-12-23 ] |
|
Error log: |
| Comment by Jan Lindström (Inactive) [ 2016-12-27 ] |
|
http://lists.askmonty.org/pipermail/commits/2016-December/010337.html |
| Comment by Marko Mäkelä [ 2016-12-28 ] |
|
I would like some clarification when the copying is actually needed. There seem to be 3 different buffers at play, and some of them are only used when compression or encryption is involved. |