Bug#327264: mysql-server-4.1: InnoDB crash recovery fails after power failure

2005-09-15 Thread Ian Kilgore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Hammers wrote: | If you need the data, contact MySQL support for a quick answer. I'm right back | from holidays and currently have not too much time :) But will try to | reproduce it. The data is not important, it's a copy of our database

Bug#327264: mysql-server-4.1: InnoDB crash recovery fails after power failure

2005-09-22 Thread Christian Hammers
tags 327264 + upstream moreinfo unreproducible thanks Hello > And so on. The database is ~19GB of text files, ~42 when its all stored > in the InnoDB tablespace. Uh, then I guess the problem has something to do with the size :) Anyway, can't do anything about it, please report the bug at http://

Bug#327264: mysql-server-4.1: InnoDB crash recovery fails after power failure

2005-09-08 Thread Ian Kilgore
Package: mysql-server-4.1 Version: 4.1.11a-4 Severity: grave After a power failure, InnoDB's crash recovery consistently fails to get the database is a usable state. mysqld either hangs, or segfaults. This has been tested using reiserfs, ext3, and a raw device for the tablespace. mysql 4.0 works

Bug#327264: mysql-server-4.1: InnoDB crash recovery fails after power failure

2005-09-08 Thread Christian Hammers
severity 327264 important thanks Hello Ian On 2005-09-08 Ian Kilgore wrote: > After a power failure, InnoDB's crash recovery consistently fails to get > the database is a usable state. mysqld either hangs, or segfaults. If you need the data, contact MySQL support for a quick answer. I'm right b