[MDEV-28488] InnoDB (compressed table) exported tablespace results in corrupted indexes Created: 2022-05-06 Updated: 2023-11-28 |
|
| Status: | Confirmed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.7.3, 10.6 |
| Fix Version/s: | 10.4, 10.5, 10.6 |
| Type: | Bug | Priority: | Minor |
| Reporter: | sjon | Assignee: | Thirunarayanan Balathandayuthapani |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | TABLESPACES, compression, import, innodb | ||
| Environment: |
linux |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
I have table that passes mysqlcheck just fine. After exporting the tablespace, and importing it in another database, the table becomes corrupted.
After recreating a fresh table this doesn't occur so the ibd might very well be corrupt - but that would indicate another issue as the server does not seem hindered by this corruption while operating normally. I've attached the exported tablespace with the cfg; the structure of this table is:
|
| Comments |
| Comment by Marko Mäkelä [ 2022-05-06 ] | ||||||
|
I tried importing the tableset.ibd from tableset.tar.gz
I got the following response to the client:
and the following to the error log:
If I copy also the .cfg file to the data directory, the import will succeed. It looks like the check that was implemented in | ||||||
| Comment by sjon [ 2022-05-06 ] | ||||||
|
Thanks Marko, can you confirm that the imported table is corrupt after importing it with the cfg file? Mysqlcheck throws a very weird error (for each index) |