Hi! sync will not help.
You can run SHOW INNODB STATUS\G to monitor when InnoDB has flushed its buffer pool. Best regards, Heikki Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL support from http://www.mysql.com/support/index.html ----- AlkuperÃinen viesti ----- LÃhettÃjÃ: "Sp.Raja" <[EMAIL PROTECTED]> Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]> Kopio: <[EMAIL PROTECTED]> LÃhetetty: Tuesday, July 27, 2004 3:42 PM Aihe: Re: Innodb assertion failure after binary backup-restore Hi, I was able to solve this by calling sync command, as my previous mail say. Do you mean to say this will not work regardless of the whether we sync or not?? which implies binary backup/restore for innodb is impossible?? We actually started with mysqldump for backup, but that was slow when we had huge amount of data, so we decided to switch in to binary mode. If innodb takes long time to flush contents to files, are there any command available to make this happen which would block until things are flushed ?? Thanks for your reply. Thanks, Sp.Raja > ------------Original Message------------ > From: "Heikki Tuuri" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Tue, Jul-27-2004 1:05 PM > Subject: Re: Innodb assertion failure after binary backup-restore > > Hi! > > That method will not work. InnoDB must be quiet long enough so that it > has > time to flush all the contents of the buffer pool to the data files. > > Best regards, > > Heikki Tuuri > Innobase Oy > Foreign keys, transactions, and row level locking for MySQL > InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up > MyISAM > tables > http://www.innodb.com/order.php > > Order MySQL technical support from https://order.mysql.com/ > > > ----- Original Message ----- > From: ""Sp.Raja"" <[EMAIL PROTECTED]> > Newsgroups: mailing.database.myodbc > Sent: Friday, July 23, 2004 4:43 PM > Subject: Innodb assertion failure after binary backup-restore > > > > Hi List, > > > > We are using 4.0.15a MySQL. We need to backup database at times and > we > empl= > > oy the following method > > > > FLUSH TABLES WITH READ LOCK > > tar -zcf backup.tar.gz ibdata1 ib_logfile0 ib_logfile1 > > UNLOCK TABLES > > > > and restore is reverse. We cannot overwrite all databases, some of > them > nee= > > ds to be unchanged across backup and restores called persistent > databases > (= > > just 1% of full data) so we employ the following > > > > mysqldump on persistent databases > > stop mysql > > cd /usr/local/mysql/data > > tar -zxf backup.tar.gz > > start mysql > > destroy persistent databases > > run mysqldump sql files to get database back to shape > > > > This method works fine expect for the case where backup is taken > immediatel= > > y after table creation and population. > > When we start the mysql after restore of this backup. It comes up, > but > mysq= > > l connections to it asking for persistent database destroy hangs. > When I > do= > > a processlist I get > > > +----+------+-----------+----+---------+------+-----------------+----------= > > ----------------+ > > | Id | User | Host | db | Command | Time | State | > Info > = > > | > > > +----+------+-----------+----+---------+------+-----------------+----------= > > ----------------+ > > | 1 | root | localhost | | Query | 55 | Waiting on cond | > drop > data= > > base persistent1| > > | 4 | root | localhost | | Query | 0 | | > show > proc= > > esslist | > > > +----+------+-----------+----+---------+------+-----------------+----------= > > ----------------+ > > > > When I open up another mysql client and query some of the tables, > they > also= > > hang and processlist at that time shows > > > +----+------+-----------+---------+---------+------+-----------------+-----= > > ------------------------+ > > | Id | User | Host | db | Command | Time | State > | > Info= > > | > > > +----+------+-----------+---------+---------+------+-----------------+-----= > > ------------------------+ > > | 1 | root | localhost | | Query | 171 | Waiting on cond > | > drop= > > database persistent1 | > > | 6 | root | localhost | data | Query | 59 | Opening tables > | > sele= > > ct * from my_data | > > | 11 | root | localhost | | Query | 0 | > | > show= > > processlist | > > > +----+------+-----------+---------+---------+------+-----------------+-----= > > ------------------------+ > > > > After some time mysql.err reports > > 040721 14:43:49 InnoDB: Assertion failure in thread 88 in file > fsp0fsp.c > l= > > ine 2950 > > InnoDB: We intentionally generate a memory trap. > > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > > InnoDB: Thread 88 stopped in file fsp0fsp.c line 2950 > > InnoDB: Thread 30 stopped in file os0sync.c line 509 > > InnoDB: Thread 96 stopped in file sync0sync.ic line 109 > > InnoDB: Thread 29 stopped in file sync0arr.c line 126 > > > > Please help me in resolving the issue by giving directions on how to > procee= > > d. > > your help is much appreciated. > > > > Thanks for your time, > > Sp.Raja > > > > > > > > > > -- > > 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] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
