MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Sp.Raja Date:July 26 2004 2:14pm
Subject:Re: Innodb assertion failure after binary backup-restore
View as plain text  
Hi List,

I figured out the fix for it. I need to do a "sync" and wait for the sync to get over and
take a backup.

Thanks,
Sp.Raja

> ------------Original Message------------
> From: "Sp.Raja" <spraja@stripped>
> To: mysql@stripped
> Date: Fri, Jul-23-2004 8:03 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
> 
> In some cases mysql crashes while restore is trying to destroy 
> persistent databases and mysql.err says
> 
> 000121 21:02:23  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 867418
> InnoDB: Doing recovery: scanned up to log sequence number 0 867418
> InnoDB: Page directory corruption: supremum not pointed to
> 000121 21:02:23  InnoDB: Page dump in ascii and hex (16384 bytes):
>  len 16384; hex.... (all zeros and dots in ascii)
> ....;InnoDB: End of page dump
> 000121 21:02:23  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form 
> checksum 1371122432
> InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
> InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
> InnoDB: Page directory corruption: supremum not pointed to
> 000121 21:02:23  InnoDB: Page dump in ascii and hex (16384 bytes):
>  len 16384; hex ...(all zeros and dots in ascii)
> ....;InnoDB: End of page dump
> 000121 21:02:23  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form 
> checksum 1371122432
> InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
> InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
> InnoDB: Error: trying to access a stray pointer a1027ff8
> InnoDB: buf pool start is at 20840000, number of pages 512
> 000121 21:02:23  InnoDB: Assertion failure in thread 43 in file 
> include/buf0buf.ic line 284
> InnoDB: Failing assertion: 0
> InnoDB: We intentionally generate a memory trap.
> InnoDB: Send a detailed bug report to mysql@stripped
> mysqld got signal 11;
> This could be because you hit a bug. It is also possible that this 
> binary
> or one of the libraries it was linked against is corrupt, improperly 
> built,
> or misconfigured. This error can also be caused by malfunctioning 
> hardware.
> We will try our best to scrape up some info that will hopefully help 
> diagnose
> the problem, but since we have already crashed, something is definitely 
> wrong
> and this may fail.
> 
> key_buffer_size=16777216
> read_buffer_size=131072
> max_used_connections=0
> max_connections=20
> threads_connected=0
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections 
> = 29183 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
> 
> Writing a core file
> 000121 21:02:24  mysqld ended
> 
> Thanks,
> Sp.Raja
> 
> > ------------Original Message------------
> > From: "Sp.Raja" <spraja@stripped>
> > To: "'mysql@stripped '" <mysql@stripped>
> > Date: Fri, Jul-23-2004 7:13 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 
> > employ 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 
> > needs 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 
> > immediately after table creation and population.
> > When we start the mysql after restore of this backup. It comes up, 
> but 
> > mysql 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 
> > database persistent1|
> > | 4  | root | localhost |    | Query   | 0    |                 | 
> show 
> > processlist         |
> > 
>
> +----+------+-----------+----+---------+------+-----------------+--------------------------+
> > 
> > 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  
> | 
> > select * 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 line 2950
> > InnoDB: We intentionally generate a memory trap.
> > InnoDB: Send a detailed bug report to mysql@stripped
> > 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 
> > proceed.
> > 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/mysql?unsub=1
> > 
> 



Thread
Innodb assertion failure after binary backup-restoreSp.Raja23 Jul
  • Re: Innodb assertion failure after binary backup-restoreSp.Raja23 Jul
    • Re: Innodb assertion failure after binary backup-restoreSp.Raja26 Jul
Re: Innodb assertion failure after binary backup-restoreHeikki Tuuri27 Jul
  • Re: Innodb assertion failure after binary backup-restoreSp.Raja27 Jul
Re: Innodb assertion failure after binary backup-restoreHeikki Tuuri27 Jul
  • Re: Innodb assertion failure after binary backup-restoreSp.Raja27 Jul
    • RE: Innodb assertion failure after binary backup-restoreMark Steele28 Jul
Re: Innodb assertion failure after binary backup-restoreHarald Fuchs27 Jul
Re: Innodb assertion failure after binary backup-restoreHeikki Tuuri29 Jul