[MDEV-792] LP:588849 - Innodb doesn't load if you change innodb_log_file_size Created: 2010-06-02  Updated: 2013-04-05  Resolved: 2013-04-05

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

Type: Task Priority: Minor
Reporter: mgrennan (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug588849.xml    

 Description   

InnoDB fails to load when I set innodb_log_file_size = 10M in my.cnf.

I don't find any errors in the logs. For a time I thought InnoDB was not included in distribution 5.1.44b-MariaDB-mariadb78-log.
After I removed this like from my.cnf it show in the show engine command and my databases returned.

I have learned setting it to the default 'innodb_log_file_size = 5242880' works fine.



 Comments   
Comment by Kristian Nielsen [ 2010-06-07 ]

Re: Innodb doesn't load if you change innodb_log_file_size
This is not a bug. A quick web search will tell how to change innodb_log_file_size, eg.

http://forums.mysql.com/read.php?22,23678,23775#msg-23775

I am guessing that the reporter is using Debian/Ubuntu, where the error message can be found in /var/log/daemon.log

Comment by mgrennan (Inactive) [ 2010-06-07 ]

Re: [Bug 588849] Re: Innodb doesn't load if you change innodb_log_file_size
Hi,

After I send the report I did the search and found this. I agree technically it is not a bug. Can we pass this over to a needed update?

Personally I consider it a bug if a programs leaves the user clueless. It doesn't start InnoDB or report an error while everything else is working fine?!

Mark Grennan
mark@grennan.com
+ 1 405 343-9332
aol: grennancom
twitter: mgrennan
http://www.mysqlfanboy.com

----- Original Message -----
From: "Kristian Nielsen" <knielsen@knielsen-hq.org>
To: mark@grennan.com
Sent: Monday, June 7, 2010 5:20:18 AM GMT -06:00 US/Canada Central
Subject: [Bug 588849] Re: Innodb doesn't load if you change innodb_log_file_size

This is not a bug. A quick web search will tell how to change
innodb_log_file_size, eg.

http://forums.mysql.com/read.php?22,23678,23775#msg-23775

I am guessing that the reporter is using Debian/Ubuntu, where the error
message can be found in /var/log/daemon.log

    • Changed in: maria
      Status: New => Invalid


Innodb doesn't load if you change innodb_log_file_size
https://bugs.launchpad.net/bugs/588849
You received this bug notification because you are a direct subscriber
of the bug.

Status in Maria: Invalid

Bug description:
InnoDB fails to load when I set innodb_log_file_size = 10M in my.cnf.

I don't find any errors in the logs. For a time I thought InnoDB was not included in distribution 5.1.44b-MariaDB-mariadb78-log.
After I removed this like from my.cnf it show in the show engine command and my databases returned.

I have learned setting it to the default 'innodb_log_file_size = 5242880' works fine.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/maria/+bug/588849/+subscribe

Comment by Kristian Nielsen [ 2010-06-08 ]

Re: Innodb doesn't load if you change innodb_log_file_size
See also MySQL Bug#19027:

http://bugs.mysql.com/bug.php?id=19027

This is essentially the same bug I think. The fix for Bug#19027 is to
implement an option --enable-plugin_innodb=FORCE; this will cause server to
fail to start if InnoDB/XtraDB does not initialise properly. (This fix is
also in MariaDB).

Apparently the default is --enable-plugin_innodb=ON, which allows the server
to start with XtraDB disabled.

So solution to the reporters original problem is to add
enable-plugin_innodb=FORCE in my.cnf.

I am changing this to two feature requests:

1. Make the default be --enable-plugin_innodb=FORCE for MariaDB.

2. Make XtraDB able to automatically change its log files when the
configuration is changed and the server is restarted, so the user does not
have to do that manually.

Comment by mgrennan (Inactive) [ 2010-06-08 ]

Re: [Bug 588849] Re: Innodb doesn't load if you change innodb_log_file_size
I agree. Thanks

Mark Grennan
mark@grennan.com
+ 1 405 343-9332
aol: grennancom
twitter: mgrennan
http://www.mysqlfanboy.com

----- Original Message -----
From: "Kristian Nielsen" <knielsen@knielsen-hq.org>
To: mark@grennan.com
Sent: Tuesday, June 8, 2010 2:06:29 AM GMT -06:00 US/Canada Central
Subject: [Bug 588849] Re: Innodb doesn't load if you change innodb_log_file_size

See also MySQL Bug#19027:

http://bugs.mysql.com/bug.php?id=19027

This is essentially the same bug I think. The fix for Bug#19027 is to
implement an option --enable-plugin_innodb=FORCE; this will cause server to
fail to start if InnoDB/XtraDB does not initialise properly. (This fix is
also in MariaDB).

Apparently the default is --enable-plugin_innodb=ON, which allows the server
to start with XtraDB disabled.

So solution to the reporters original problem is to add
enable-plugin_innodb=FORCE in my.cnf.

I am changing this to two feature requests:

1. Make the default be --enable-plugin_innodb=FORCE for MariaDB.

2. Make XtraDB able to automatically change its log files when the
configuration is changed and the server is restarted, so the user does not
have to do that manually.


Innodb doesn't load if you change innodb_log_file_size
https://bugs.launchpad.net/bugs/588849
You received this bug notification because you are a direct subscriber
of the bug.

Status in Maria: Confirmed
Status in Percona XtraDB Storage Engine for MySQL: New

Bug description:
InnoDB fails to load when I set innodb_log_file_size = 10M in my.cnf.

I don't find any errors in the logs. For a time I thought InnoDB was not included in distribution 5.1.44b-MariaDB-mariadb78-log.
After I removed this like from my.cnf it show in the show engine command and my databases returned.

I have learned setting it to the default 'innodb_log_file_size = 5242880' works fine.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/maria/+bug/588849/+subscribe

Comment by Rasmus Johansson (Inactive) [ 2011-06-07 ]

Launchpad bug id: 588849

Comment by Stewart Smith [ 2011-06-07 ]

Re: Innodb doesn't load if you change innodb_log_file_size
All development of XtraDB has moved under the Percona Server project - https://launchpad.net/percona-server - If this bug can be reproduced against current Percona Server, please file this bug against percona-server (you can simply do so by using the "Also affects project" link above).

Thanks,
Stewart Smith
Director of Server Development
Percona.

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