* Wolfram Schlich <[EMAIL PROTECTED]> [2008-02-05 15:50]:
> Hi,
>
> I have a MySQL 5.0.54 instance with a 5.0.22 datadir from a corrupted
> filesystem, backed up what was readable and am now trying to get it
> back to life. Unfortunately, mysqld segfaults on startup:
> [...]
> What should I do nex
Hi,
I have a MySQL 5.0.54 instance with a 5.0.22 datadir from a corrupted
filesystem, backed up what was readable and am now trying to get it
back to life. Unfortunately, mysqld segfaults on startup:
--8<--
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence nu
mike,
Tuesday, October 29, 2002, 4:21:40 AM, you wrote:
maddn> After upgrading mysql to 3.23.53, mysqld would segfault every time
accessing a certain database. After running checks
maddn> on the database and making sure everything was okay, I started mysqld up in
gdb.
maddn> Program re
>Description:
After upgrading mysql to 3.23.53, mysqld would segfault every time accessing a
certain database. After running checks
on the database and making sure everything was okay, I started mysqld up in gdb.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread
