[MDEV-2838] LP:1007776 - mysqld crashes with assertion space != 0 when using invalid innodb ibdata1 Created: 2012-06-02  Updated: 2012-10-04  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Kissaki (Inactive) Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug1007776.xml     Text File LPexportBug1007776_crash.log    

 Description   

When using an invalid innodb data file (ibdata1) mysqld crashed for me.

On Windows x64, mariadb-5.5.24-winx64.

This happened on an upgrade from 5.2 to 5.5, where I had a seemingly older ibdata1 file in the data directory, but used a custom innodb_data_home_dir previously.
Upon upgrading, without the old innodb_data_home_dir set correctly, the outdated ibdata1 from the data directory seems to have been read.

When starting mysqld, it crashed with
> 120602 11:21:08 InnoDB: Assertion failure in thread 34164 in file fsp0fsp.c line 2874
> InnoDB: Failing assertion: space != 0

The full log in detail is attached.

What I would expect is not a crash, but a sane error-handling, quitting with an appropriate error being logged/printed out.

 Comments   
Comment by Kissaki (Inactive) [ 2012-06-02 ]

Re: mysqld crashes with assertion space != 0 when using invalid innodb ibdata1

Comment by Kissaki (Inactive) [ 2012-06-02 ]

Full error log from the respective mysqld call.
LPexportBug1007776_crash.log

Comment by Vladislav Vaintroub [ 2012-06-02 ]

Re: mysqld crashes with assertion space != 0 when using invalid innodb ibdata1
I' changing the status to "invalid", since it seems to be a user error rather than Innodb logic. Innodb can't always know what you're doing , and log appropriate error message. You data file can be corupt on different reasons, so crashing like this is not insane, to have some attention from a DBA.

As for the upgrade, I added "General recommendations" section in the KB article about upgrading on Windows :http://kb.askmonty.org/en/upgrading-mariadb-on-windows/ . If one follows the steps, no such errors should happen .

Comment by Rasmus Johansson (Inactive) [ 2012-06-02 ]

Launchpad bug id: 1007776

Generated at Thu Feb 08 06:44:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.