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

innodb.innodb_bug14147491 fails in buildbot on some debug builds

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/4143/steps/test_6/logs/stdio

      innodb.innodb_bug14147491 'innodb_plugin' w2 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2015-08-21 18:56:50
      line
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: Database page corruption on disk or a failed
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: Space 4 file test/t1 read of page 6.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: You may have to recover from a backup.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: It is also possible that your operatingsystem has corrupted its own file cache.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: and rebooting your computer removes the error.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: If the corrupt page is an index page you can also try to
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: fix the corruption by dumping, dropping, and reimporting
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: the corrupt table. You can use CHECK
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: TABLE to scan your table for corruption.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html about forcing recovery.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: Database page corruption on disk or a failed
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: Space 4 file test/t1 read of page 6.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: You may have to recover from a backup.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: It is also possible that your operatingsystem has corrupted its own file cache.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: and rebooting your computer removes the error.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: If the corrupt page is an index page you can also try to
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: fix the corruption by dumping, dropping, and reimporting
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: the corrupt table. You can use CHECK
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: TABLE to scan your table for corruption.
      2015-08-21 18:56:47 2913430336 [ERROR] InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html about forcing recovery.
      ^ Found warnings in /mnt/buildbot/build/mariadb-10.1.6/mysql-test/var/2/log/mysqld.1.err
      ok

      According to cross-reference report, it started happening around this push:
      http://buildbot.askmonty.org/buildbot/builders/p8-rhel6-bintar-debug/builds/759

      Changed by	Jan Lindström <jan.lindstrom@mariadb.com>
      Changed at	Fri 14 Aug 2015 15:49:56
      Repository	https://github.com/MariaDB/server
      Branch	10.1
      Revision	a80753594a37538a35df7c02ae80da624578dec4
      Comments
       
      MDEV-8591: Database page corruption on disk or a failed space, Assertion failure in file buf0buf.cc line 2856 on querying a table using wrong default encryption key
       
      Improved error messaging to show based on original page before
      encryption is page maybe encrypted or just corrupted.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jplindst Jan Lindström
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: