Asif, now take the old log files from the safe place and put them back! That will save your data.
The instructions about changing the size of the log files are the following: http://www.innodb.com/ibman.html#Adding_and_removing " If you want to change the number or the size of your InnoDB log files, you have to shut down MySQL and make sure that it shuts down without errors. Then copy the old log files into a safe place just in case something went wrong in the shutdown and you will need them to recover the database. Delete then the old log files from the log file directory, edit my.cnf, and start MySQL again. InnoDB will tell you at the startup that it is creating new log files. " Note above that you must make sure mysqld shuts down without errors. Only then you can change the size of the log files. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: "Asif Iqbal" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Tuesday, August 26, 2003 9:03 PM Subject: Re: InnoDB Error ib_logfile0 of different size > On Tue, 26 Aug 2003, Victoria Reznichenko wrote: > > > Asif Iqbal <[EMAIL PROTECTED]> wrote: > > > I already have mysql 4.0.13 running with all InnoDB tables. I am trying to use > > > my-huge.cnf since I have 4 gig RAM with 4 x 450 Mhz processes > > > > > > In my MySQL data directory I have two ib_logfile files > > > > > > -rw-rw---- 1 mysql mysql 5242880 Aug 26 01:55 ib_logfile0 > > > -rw-rw---- 1 mysql mysql 5242880 Aug 25 19:03 ib_logfile1 > > > > > > Now if I add this line in my cnf file (as recommended by my-huge.cnf) > > > > > > innodb_log_file_size = 100M > > > > > > I get the following error > > > > > > InnoDB: Error: log file /usr/local/mysql/data/ib_logfile0 is of different size 0 > > > 5242880 bytes > > > InnoDB: than specified in the .cnf file 0 104857600 bytes! > > > 030826 1:42:15 Can't init databases > > > 030826 1:42:15 Aborting > > > > > > So as a workaround I commented the innodb_log_file_size. But I really don't like > > > this solution. Is there a better solution ? > > > > Move old log files to the safe place. > > Edit my.cnf and then start MySQL server. > > > > If I move the old log in a safe place and use innodb_log_file_size = 100M, this > is what I get > > 030826 01:40:38 mysqld started > 030826 1:40:39 InnoDB: Log file /usr/local/mysql/data/ib_logfile0 did not > exist: new to be created > InnoDB: Setting log file /usr/local/mysql/data/ib_logfile0 size to 100 MB > InnoDB: Database physically writes the file full: wait... > InnoDB: Progress in MB: 100 > 030826 1:40:47 InnoDB: Log file /usr/local/mysql/data/ib_logfile1 did not > exist: new to be created > InnoDB: Setting log file /usr/local/mysql/data/ib_logfile1 size to 100 MB > InnoDB: Database physically writes the file full: wait... > InnoDB: Progress in MB: 100 > InnoDB: Cannot initialize created log files because > InnoDB: data files were not in sync with each other > InnoDB: or the data files are corrupt. > 030826 1:40:54 Can't init databases > 030826 1:40:54 Aborting > > > > > > > > -- > Asif Iqbal > http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08 > There's no place like 127.0.0.1 > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
