24 messages in com.mysql.lists.bugsRe: myisamchk --unpack bug in 3.23.42
FromSent OnAttachments
Martin MOKREJŠ19 Nov 2001 03:13 
Michael Widenius19 Nov 2001 07:15 
Michael Widenius21 Nov 2001 14:48 
Martin MOKREJŠ22 Nov 2001 02:31 
Martin MOKREJŠ22 Nov 2001 04:17 
Michael Widenius22 Nov 2001 05:10 
Michael Widenius22 Nov 2001 10:21 
Martin MOKREJŠ08 Dec 2001 14:40 
Martin MOKREJŠ08 Dec 2001 16:08 
Michael Widenius08 Dec 2001 17:36 
Martin MOKREJŠ08 Dec 2001 18:40 
Michael Widenius09 Dec 2001 04:34 
Michael Widenius09 Dec 2001 05:03 
Michael Widenius09 Dec 2001 05:07 
Martin MOKREJŠ09 Dec 2001 08:31 
Martin MOKREJŠ09 Dec 2001 09:05 
Martin MOKREJŠ09 Dec 2001 09:15 
Michael Widenius10 Dec 2001 07:21 
Michael Widenius10 Dec 2001 07:31 
Martin MOKREJŠ10 Dec 2001 08:03 
Martin MOKREJŠ10 Dec 2001 14:55 
Michael Widenius10 Dec 2001 15:55 
Martin MOKREJŠ11 Dec 2001 02:56 
Michael Widenius11 Dec 2001 04:07 
Subject:Re: myisamchk --unpack bug in 3.23.42
From:Michael Widenius (mon@mysql.com)
Date:12/11/2001 04:07:20 AM
List:com.mysql.lists.bugs

Hi!

"mmokrejs" == mmokrejs <iso-8859-2> writes:

mmokrejs> On Tue, 11 Dec 2001, Michael Widenius wrote: mmokrejs> Hi,

<cut>

When and how did you notice that the table was corrupted.

mmokrejs> I needed uncompressed tables in this database. I've seen error message mmokrejs> from myisamchk --unpack that it could not uncompress the table. mmokrejs> I used flush-tables for sure before that (I already knew that I have
to mmokrejs> use it).

ok, now I finally understand the problem:

- You had a table that was compressed and ok (passed 'check tables' and 'myisamchk'). - When you run 'myisamchk -r --unpack' on it, you got errors.

I have however not got any such table from you. If you have such a table somewhere, I would really like to take a look at this. If not, let's forget this thread for now...

<cut>

mmokrejs> OK, I think this thread was long enough. Thanks a lot and sorry for
stupid mmokrejs> e-mails. ;)

I agree :)

Regards, Monty