We have tried doing that. We did
# sudo stop mysql
I make sure that mysql is no longer running
# ps -ef | grep mysql
and then we rename the old log files. We then start up using
# sudo start mysql
and the above errors start. It is creating the new log files but it just
seems that they do not tie up with what is in the innodb tables.
- Should we be able to change the size of the log file even if we already
have data?
- Had a look at the innodb_fast_shutdown (which is currently the default
1). Should we set it to 0 to force a full purge?
Thanks for getting back to me.
Regards,
On Tue, Sep 28, 2010 at 10:09 AM, Prabhat Kumar <aim.prabhat@stripped>wrote:
> it seems that mysql is not shutdown properly which caused error.
> now , you can try to start MySQL with, backed log files (ib_logfile0 and
> ib_logfile1) with old value in cnf. (as you said renamed those log files )
>
> Then do proper MySQL shutdown , edit the cnf.... again move log files some
> safe place ... and start with new value in cnf.
>
>
>
>
>
> On Tue, Sep 28, 2010 at 12:47 PM, brett skinner <tatty.dishcloth@stripped
> > wrote:
>
>> Hi
>>
>> Yesterday we had an issue with one our servers. It seemed to be performing
>> quite poorly. At some point we noticed that it was running with the stock
>> standard innodb settings although the my.cnf file had been changed. We
>> probably forgot to restart mysql after the changes. It has been this way
>> for
>> a couple of months. We have a couple of very large tables. We have 3
>> tables
>> that can hold up to 6 millions rows. We attempted to clean some of these
>> tables to get better performance. After the deletes had finished (It took
>> about 2 hours to delete 6 Million rows in one table) we restarted mysql.
>>
>> The innodb engine failed to start. We investigated the error.log file and
>> saw that there was a difference between the configured size and the actual
>> (this is what lead us to believe that the configuration changes had been
>> made but not restarted). So we shut down mysql and renamed the log files.
>> We
>> then restarted mysql and the new innodb log files were created. However we
>> are now getting these errors:
>>
>> 100927 20:52:52 InnoDB: Log file ./ib_logfile1 did not exist: new to be
>> created
>> InnoDB: Setting log file ./ib_logfile1 size to 256 MB
>> InnoDB: Database physically writes the file full: wait...
>> InnoDB: Progress in MB: 100 200
>> InnoDB: The log sequence number in ibdata files does not match
>> InnoDB: the log sequence number in the ib_logfiles!
>> 100927 20:52: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...
>> 100927 20:52:58 InnoDB: Error: page 7 log sequence number 14 3682128430
>> InnoDB: is in the future! Current system log sequence number 0 1526796.
>> InnoDB: Your database may be corrupt or you may have copied the InnoDB
>> InnoDB: tablespace but not the InnoDB log files. See
>> InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
>> InnoDB: for more information.
>> 100927 20:52:58 InnoDB: Error: page 1 log sequence number 15 2402422243
>> InnoDB: is in the future! Current system log sequence number 0 1526796.
>> InnoDB: Your database may be corrupt or you may have copied the InnoDB
>> InnoDB: tablespace but not the InnoDB log files. See
>> InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
>> InnoDB: for more information.
>>
>> And it goes on and on...
>>
>> We eventually managed to get the innodb engine started again by shutting
>> down and renaming the old log files back and restarting. After everything
>> had started and we had run a CHECK TABLE on the tables then we tried
>> again. So we shut down again and the followed the instructions at
>> http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.htmlexplicitly.
>>
>> We have done this a couple of times but the innodb engine never seems to
>> come back and we see the above errors.
>>
>> How do we proceed?
>>
>> Regards,
>>
>
>
>
> --
> Best Regards,
>
> Prabhat Kumar
> MySQL DBA
>
> My Blog: http://adminlinux.blogspot.com
> My LinkedIn: http://www.linkedin.com/in/profileprabhat
>
