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

InnoDB: Assertion failure in file fil0pagecompress.cc line 532

        Details

          Description

          Database corruption when using compression+encryption on FusionIO hw.

          InnoDB: Corruption: Page is marked as compressed but decompression read only 3002783 bytes size 6611 len 16384 err=424967292.

            Gliffy Diagrams

              Attachments

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                jplindst Jan Lindström added a comment -

                How to repeat:

                Create database for LinkBench using page compression and e.g. example_key_management. Start load phase by using trim and atomic writes.

                Show
                jplindst Jan Lindström added a comment - How to repeat: Create database for LinkBench using page compression and e.g. example_key_management. Start load phase by using trim and atomic writes.
                Hide
                Permalink
                jplindst Jan Lindström added a comment -

                commit 70b82efd20ec6682a6ede8552b1109d04d372e0c
                Author: Jan Lindström <jan.lindstrom@mariadb.com>
                Date: Mon Jun 8 19:36:35 2015 +0300

                MDEV-8273: InnoDB: Assertion failure in file fil0pagecompress.cc line 532

                Analysis: Problem was that actual payload size (page size) after compression
                was handled incorrectly on encryption. Additionally, some of the variables
                were not initialized.

                Fixed by encrypting/decrypting only the actual compressed page size.

                Show
                jplindst Jan Lindström added a comment - commit 70b82efd20ec6682a6ede8552b1109d04d372e0c Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Mon Jun 8 19:36:35 2015 +0300 MDEV-8273 : InnoDB: Assertion failure in file fil0pagecompress.cc line 532 Analysis: Problem was that actual payload size (page size) after compression was handled incorrectly on encryption. Additionally, some of the variables were not initialized. Fixed by encrypting/decrypting only the actual compressed page size.

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: