Kevin,

...
/************************************************************
Empties the hash table when it has been fully processed. */
static
void
recv_sys_empty_hash(void)
/*=====================*/
{
        ut_ad(mutex_own(&(recv_sys->mutex)));
        ut_a(recv_sys->n_addrs == 0);
...

looks like the hash table of log records had a wrong count of page numbers
which caused the assertion.

recv_sys->n_addrs means for how many database pages we have log records.

I have not seen this bug report before. If you can send me ibbackup_logfile
from your backup directory, I can parse it here and look what is wrong. Also
send me the printout of

ls -l

in /usr/local/mysql/var

so that I see the exact size of ibdata1.

Regards,

Heikki

sql query

........

Subject: bug report
From: Kevin Carrigan
Date: 01 Nov 2002 06:59:42 -0800

----------------------------------------------------------------------------
----

Not sure if this is a bug or not, I just read the output after restore
failed....

ibbackup --restore /etc/my.cnf
InnoDB Hot Backup version 1.03b; Copyright 2002 Innobase Oy
License serial n:o A320
(--restore works in any computer regardless of the hostname)
Licensed for use in a computer whose hostname is 'eve'
Expires 2003-12-1 (year-month-day) at 00:00
See http://www.innodb.com for further information
Type ibbackup --license for detailed license terms, --help for help

Contents of /etc/my.cnf:
innodb_data_home_dir got value /usr/local/mysql/var/
innodb_data_file_path got value ibdata1:10M:autoextend
innodb_log_group_home_dir got value /usr/local/mysql/var/
innodb_log_files_in_group got value 4
innodb_log_file_size got value 5242880

021101  6:51:50  ibbackup: ibbackup_logfile's creation parameters:
ibbackup: start lsn 0 4268909056, end lsn 0 4268995937,
ibbackup: start checkpoint 0 4268909336
InnoDB: Doing recovery: scanned up to log sequence number 0 4268995937
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 3
4 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 7
5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98
99 InnoDB: Assertion failure in thread 8192 in file
log0recv.c line 144
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
Segmentation fault



--
Kevin Carrigan <[EMAIL PROTECTED]>





---------------------------------------------------------------------
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

Reply via email to