Osvaneo,
you probably forgot to move also ib_logfiles.
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 7 1021600303
InnoDB: Doing recovery: scanned up to log sequence number 7 1021600256
It cannot scan the current ib_logfiles at all!
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 InnoDB which also backs up MyISAM
tables
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: Osvaneo Ap. Ferreira [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, December 12, 2003 2:53 AM
Subject: [ MySQL: Problems with Innodb ]
--=_NextPart_000_000C_01C3BFEE.891285C0
Content-Type: multipart/alternative;
boundary==_NextPart_001_000D_01C3BFEE.891719A0
--=_NextPart_001_000D_01C3BFEE.891719A0
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi,
I have a problem and would like a help.
I copied a mysql datadir to another place (backup of datadir), but when =
start up mysql server with datadir it's crash.
See below, trace of logfile:
031211 13:28:01 mysqld started
031211 13:28:01 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 7 1021600303
InnoDB: Doing recovery: scanned up to log sequence number 7 1021600256
InnoDB: Error: trying to access a stray pointer c0b7bff8
InnoDB: buf pool start is at 40388000, number of pages 512
031211 13:28:01 InnoDB: Assertion failure in thread 16384 in file =
../../innobase/include/buf0buf.ic line 284
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
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=3D8388600
read_buffer_size=3D131072
sort_buffer_size=3D137
max_used_connections=3D0
max_connections=3D100
threads_connected=3D0
It is possible that mysqld could use up to=20
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
=3D 21005 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=3D0x83322c0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Bogus stack limit or frame pointer, fp=3D0xbfffd368, =
stack_bottom=3D0x706f6e6d, thread_stack=3D196608, aborting backtra
ce.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd-query at 0x6c6b6a69 is invalid pointer
thd-thread_id=3D0
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 0 did to cause the crash. In some cases of =
really
bad corruption, the values shown above may be invalid.
The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash.
031211 13:28:01 mysqld ended
Server Installed: mysql-4.0.12
Help me !!!.
Osv=E2neo Ap. Ferreira
http://www.ig.com.br
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
