MySQL Forums
Forum List  »  Performance

InnoDB: Database was not shut down normally after changing innod_db_log_file_size
Posted by: Area sistemi Ripartizione Informatica
Date: October 04, 2013 02:36AM

I followed Mysql documentation about changing innodb_log_file_size (I tested this procedure also with innodb_fast_shutdown set to 0) and when I start db all seems to be ok but from logs I can see:

131002 08:04:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131002 8:04:58 InnoDB: Initializing buffer pool, size = 8.0M
131002 8:04:58 InnoDB: Completed initialization of buffer pool
131002 8:04:58 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
131002 8:04:58 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
131002 8:04:58 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
131002 8:05:05 InnoDB: Started; log sequence number 3 1342899212


The question is: it is an exptected behavior the fact that db starts anyway in crash recovery?

Thanks

Options: ReplyQuote


Subject
Views
Written By
Posted
InnoDB: Database was not shut down normally after changing innod_db_log_file_size
1447
October 04, 2013 02:36AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.