[MDEV-583] LP:884728 - [ERROR] mysqld: Aria engine: log initialization failed Created: 2011-11-01 Updated: 2021-04-26 Resolved: 2020-10-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Aria |
| Affects Version/s: | 10.0.0, 5.5.28, 5.3.9, 5.5, 10.0, 10.1 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Dreas van Donselaar (Inactive) | Assignee: | Michael Widenius |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | Aria, Launchpad | ||
| Attachments: |
|
| Description |
|
MariaDB failed to start on one of our systems:
Removing /var/lib/mysql/aria* allowed MariaDB to start again. I'll upload the corrupt Aria files to FTP (we verified on another system that it indeed fails to start with those files). |
| Comments |
| Comment by Dreas van Donselaar (Inactive) [ 2011-11-11 ] | |||||||||||||||||
|
Re: [ERROR] mysqld: Aria engine: log initialization failed | |||||||||||||||||
| Comment by Rasmus Johansson (Inactive) [ 2011-12-01 ] | |||||||||||||||||
|
Launchpad bug id: 884728 | |||||||||||||||||
| Comment by Elena Stepanova [ 2012-11-04 ] | |||||||||||||||||
|
The problem can still be seen while trying to read logs:
However, there is no indication of how the corrupted logs were produced. Knowing the history, chances are that it happened due to a power failure or a hardware failure. I suppose if we want to do anything at all about the bug, it's to check that the failure is really caused by the log being corrupted and not by the contents. | |||||||||||||||||
| Comment by Elena Stepanova [ 2017-08-30 ] | |||||||||||||||||
|
The problem with a mysteriously corrupt | |||||||||||||||||
| Comment by Michael Widenius [ 2018-05-21 ] | |||||||||||||||||
|
Tried to reproduce this with the given logs, but worked in 10.1 for me. Without an log that allows me to reproduce this or access to a machine | |||||||||||||||||
| Comment by Claudio Nanni [ 2018-06-06 ] | |||||||||||||||||
|
Seen again in 10.1.33 | |||||||||||||||||
| Comment by Elena Stepanova [ 2018-06-08 ] | |||||||||||||||||
|
I'm not sure why it wasn't reproducible for monty, I'm still getting the same assertion on the same data with the current 10.1:
However, now non-debug version produces an additional more descriptive error message:
| |||||||||||||||||
| Comment by Michael Widenius [ 2020-10-15 ] | |||||||||||||||||
|
Probably problem with the operating system. Issue disappeared after OS update |