INNODB Table corruptions

@futureweb wrote:

Hello,
on our Piwik installation we got massive Problems with INNODB Table corruptions.
Every few Days an old piwik_archive_blob_xx_xx Table gets corrupted. Already got an open Case with MariaDB on that (https://jira.mariadb.org/browse/MDEV-12434) - but I noticed that those corruptions always happen between 03:00 - 04:00.
May I ask if there are automated Tastks on the Archive Blob Tables running then? (File-Change Date on the Archive Blob Tables is always between 3-4)
If there are operations running on them - what's doing it? And why still touching such old Tables? (Or is it something from MariaDB touching those Tables?)

Piwik: 3.0.4
[root@piwikdb mariadb]# cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
[root@piwikdb mariadb]# mysql -V
mysql Ver 15.1 Distrib 10.1.24-MariaDB, for Linux (x86_64) using readline 5.1
[root@piwikdb mariadb]# php -v
PHP 7.0.19 (cli) (built: May 11 2017 10:39:08) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.0.19, Copyright (c) 1999-2017, by Zend Technologies

MariaDB Error:

2017-06-26  3:32:08 140133463947008 [ERROR] InnoDB: Space id and page n:o stored in the page read in are 1358817207:3293897363, should be 62801:13951!
2017-06-26  3:32:08 140133463947008 [Note] InnoDB: Log sequence number at the start 2841626724 and the end 2277888994 do not match.
2017-06-26  3:32:08 140133463947008 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace piwik/piwik_archive_blob_2016_03 page  [page id: space=62801, page number=13951]. You may have to recover from a backup.
2017-06-26 03:32:08 7f735d56f700 InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex e4d4c698c454e29399cb79a5fc8ff2d4563ebcdaa95fc8641c091ca8d3fe5723f53c50fde7b7ebfbbb89987838e9124e241a7efdf13c6d813c7900c8b5bf18050b8122000005295a56697369746f72496e7465726573745f6461797353696e63654c61737456697369740000462645bddc00002664137a0$
InnoDB: End of page dump
2017-06-26 03:32:09 7f735d56f700 InnoDB: uncompressed page, stored checksum in field1 3839149720, calculated checksums for field1: crc32 1464224319, innodb 1101069064, none 3735928559, stored checksum in field2 1288165860, calculated checksums for field2:$
InnoDB: page type 7177 meaning PAGE TYPE CORRUPTED

Thank you for any information which could lead me in the right direction on stopping those corruptions ...
Andreas Schnederle-Wagner

Posts: 3

Participants: 2

Read full topic