Ha-nyung, ----- Original Message ----- From: ""Chung Ha-nyung"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Wednesday, January 22, 2003 6:48 AM Subject: resize InnoDB's log file
> > Currently I have three InnoDB log files, whose size is 256MB and main > memory is 2GB. > Since I use 1GB of InnoDB buffer pool, I think log files'd better get > bigger to some extent; > possibly 1GB. > You know, only changing the value in my.cnf cause mysqld not to start > due to error. > I'm wondering if deleting log files after mysqld is stopped and > starting mysqld is safe. yes. You can read the procedure from the manual from 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 the following IMPORTANT bug fix: http://www.innodb.com/ibman.html#InnoDB_history: " MySQL/InnoDB-3.23.55, January xx, 2003 ... Fixed a bug: if the combined size of InnoDB log files was >= 2 GB in a 32-bit computer, InnoDB would write log in a wrong position. That could make crash recovery and InnoDB Hot Backup to fail in log scan. " This fix is already in 4.0.9. Also note that the recommendation is that the combined log file size should be 50 % of the buffer pool size and always < 4 GB. 3 GB is too much.for a buffer pool of 1 GB. > I tried this and got some look-so-serious error(or warning?) messages > like following: > > 030121 10:18:49 mysqld ended > > 030121 10:27:07 mysqld started > 030121 10:27:11 InnoDB: Log file ./ib_logfile0 did not exist: new to > be created > InnoDB: Setting log file ./ib_logfile0 size to 1024 MB > InnoDB: Database physically writes the file full: wait... > 030121 10:28:05 InnoDB: Log file ./ib_logfile1 did not exist: new to > be created > InnoDB: Setting log file ./ib_logfile1 size to 1024 MB > InnoDB: Database physically writes the file full: wait... > 030121 10:29:02 InnoDB: Log file ./ib_logfile2 did not exist: new to > be created > InnoDB: Setting log file ./ib_logfile2 size to 1024 MB > InnoDB: Database physically writes the file full: wait... > 030121 10:29:58 InnoDB: Database was not shut down normally. > InnoDB: Starting recovery from log files... > InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 0 3205932556 > InnoDB: Doing recovery: scanned up to log sequence number 0 3205932556 > InnoDB: Last MySQL binlog file position 0 13846, file name ./lacrimosa- > bin.003 > 030121 10:29:58 InnoDB: Flushing modified pages from the buffer pool... > 030121 10:29:59 InnoDB: Started > /austin/local/mysql/bin/mysqld: ready for connections These are the normal messages when you resize the log files. InnoDB always does a 'crash recovery' at a startup. In a regular startup these messages are suppresses and you do not see them. > query. sql > > -- > Chung Ha-nyung <alita@[neowiz.com|kldp.org]> > Sayclub <http://www.sayclub.com> > NeoWiz <http://www.neowiz.com> Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
