Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-11656

'Data structure corruption' IMPORT TABLESPACE doesn't work for encrypted InnoDB tables if space_id changed

Details

    • 10.2.4-5

    Description

      So I do following actions on encrypted InnoDB :
      [mysqld]
      plugin_load=file_key_management.so
      file_key_management_encryption_algorithm=aes_cbc
      file_key_management_filename=/sec/keys.enc
      file_key_management_filekey=secret
      innodb-buffer-pool-size=128M
      innodb-encrypt-log=ON
      innodb-encryption-rotate-key-age=2
      innodb-encryption-threads=4
      innodb-tablespaces-encryption
      innodb-encrypt-tables=FORCE

      root@c480fbb475db:/test# mysql <<EOL
      create database d1;
      use d1;
      create table t(a varchar(5)) encrypted=yes encryption_key_id=1;
      EOL
      root@c480fbb475db:/test# cp /dt/d1/t.ibd /t.ibd
      root@c480fbb475db:/test# mysql d1 <<EOL
      > drop table t;
      > create table t(a varchar(5)) encrypted=yes encryption_key_id=1;
      > alter table t discard tablespace;
      > EOL
      root@c480fbb475db:/test# cp /t.ibd /dt/d1/
      root@c480fbb475db:/test# mysql -e "alter table d1.t import tablespace;"
      ERROR 1296 (HY000) at line 1: Got error 39 'Data structure corruption' from ./d1/t.ibd

      If I don't drop the table inbetween - it works.
      Attached mtr test case shows the same error:

      ALTER TABLE t1 IMPORT TABLESPACE;
      encryption.innodb-discard-import-adv 'cbc,innodb_plugin' [ fail ]
      Test ended at 2016-12-23 11:46:15

      CURRENT_TEST: encryption.innodb-discard-import-adv
      mysqltest: At line 134: query 'ALTER TABLE t1 IMPORT TABLESPACE' failed: 1296: Got error 39 'Data structure corruption' from ./test/t1.ibd

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          anikitin Andrii Nikitin (Inactive) added a comment -

          Error log:
          2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk
          2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk - done!
          2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Phase I - Update all pages
          2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk
          2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk - done!
          2016-12-23 10:37:37 139667421829888 [ERROR] InnoDB: In file './d1/t.ibd', tablespace id and flags are 4 and 0, but in the InnoDB data dictionary they are 5 and 0. Have you moved InnoDB .ibd files around without using the commands DISCARD TABLESPACE and IMPORT TABLESPACE? Please refer to http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
          2016-12-23 10:37:37 7f06db109b00 InnoDB: Operating system error number 2 in a file operation.
          InnoDB: The error means the system cannot find the path specified.
          2016-12-23 10:37:37 139667421829888 [ERROR] InnoDB: Could not find a valid tablespace file for 'd1/t'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
          2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Discarding tablespace of table "d1"."t": Data structure corruption

          anikitin Andrii Nikitin (Inactive) added a comment - Error log: 2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk 2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk - done! 2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Phase I - Update all pages 2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk 2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Sync to disk - done! 2016-12-23 10:37:37 139667421829888 [ERROR] InnoDB: In file './d1/t.ibd', tablespace id and flags are 4 and 0, but in the InnoDB data dictionary they are 5 and 0. Have you moved InnoDB .ibd files around without using the commands DISCARD TABLESPACE and IMPORT TABLESPACE? Please refer to http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2016-12-23 10:37:37 7f06db109b00 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. 2016-12-23 10:37:37 139667421829888 [ERROR] InnoDB: Could not find a valid tablespace file for 'd1/t'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2016-12-23 10:37:37 139667421829888 [Note] InnoDB: Discarding tablespace of table "d1"."t": Data structure corruption
          jplindst Jan Lindström (Inactive) added a comment -

          http://lists.askmonty.org/pipermail/commits/2016-December/010337.html

          jplindst Jan Lindström (Inactive) added a comment - http://lists.askmonty.org/pipermail/commits/2016-December/010337.html
          marko Marko Mäkelä added a comment -

          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.

          marko Marko Mäkelä added a comment - 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.

          People

            jplindst Jan Lindström (Inactive)
            anikitin Andrii Nikitin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.