Segfault during repair after a MySQL server crash and bug with myisam-recover

Hi,

How-to-repeat :

Download ftp://support.mysql.com/pub/mysql/secret/configcrash.tar.gz and try
to repair the table : it always crashes (even myisamchk -o segfault)

(the corruption happens after testing tests/client_test script in the test
directory :
[MySQL-4.1.0-alpha][2013] Lost connection to MySQL server during query
client_test: client_test.c:2696: bind_fetch: Assertion `rc == 0' failed.
total parameters in stmt: 7 (expected: 7)Aborted
)

BTW I just see another bug using myisam-recover=BACKUP,FORCE,QUICK.
A show processlist, during the repair of some tables, showed :

| 10 | mysql | localhost | Hardwarefr | Query | 649 | Repair by sorting
| SELECT COUNT(*) FROM threadhardwarefr1

or even

| 2052 | DELAYED | localhost | Hardwarefr | Delayed_insert | 44 | Checking
table |

=> It seems the status messages are sometimes written in the wrong place
during the auto-repair process.

Regards,
Jocelyn


------------------------------------------------------------ ---------
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 bugs-thread13598@lists.mysql.com
To unsubscribe, e-mail

Re: Segfault during repair after a MySQL server crash

Hi!

On Jan 26, Jocelyn Fournier wrote:
> Hi,
>
> How-to-repeat :
>
> Download ftp://support.mysql.com/pub/mysql/secret/configcrash.tar.gz and try
> to repair the table : it always crashes (even myisamchk -o segfault)

Fixed, thanks.
Though, I can hardly imagine how you managed to create such a file,
without manually editing MYI header :)
Now, it's:

% myisamchk -r config
myisamchk: error: 'config' doesn't have a correct index definition. You need to recreate it before you can do a repair
%

Of course, REPAIR TABLE ... USE_FRM repairs this table perfectly.

Regards,
Sergei

--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/

------------------------------------------------------------ ---------
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 bugs-thread13602@lists.mysql.com
To unsubscribe, e-mail

Re: Segfault during repair after a MySQL server crash

Hi sergei,

I reproduced exactely the same problem after a crash in 4.1.
It seems the myisam-recover=BACKUP,FORCE,QUICK option corrupt the file when
it try to repair it with keycache :

030204 13:19:06 Warning: Recovering table: './Hardwarefr/config'
030204 13:19:08 Warning: Checking table:
'./forum_hardwarefr/searchmainhardwarefr13'
030204 13:19:08 1 clients is using or hasn't closed the table properly
030204 13:19:08 Warning: Retrying repair of: './Hardwarefr/config' with
keycache
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=536870912
read_buffer_size=1044480
sort_buffer_size=2097144
max_used_connections=38
max_connections=320
threads_connected=32
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
1506045 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x5aaec6e0
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...
Cannot determine thread, fp=0xbb5fd0a8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80d6ffb
0x40034f54
0x832cb40
0x832cc2f
0x832cc76
0x832d03b
0x83271ca
0x8326b16
0x812be42
0x812bab0
0x812c486
0x80f4d9f
0x80f4152
0x80f4e93
0x80f5148
0x80e134f
0x80e4de5
0x80e043b
0x80dfe6d
0x80df69e
0x400320ba
0x40180d6a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x890ef78 = SELECT
email,password,nbrpost_forum,image_forum,signature_forum,icq ,IP,homepage,dat
einscr,hobby,occupation,status,image,mailv,validation,citati on,ville,smilies
,config.config,js,zlib,online,topicpp,lastpost,birthday, oldquote,modomp
FROM Hardwarefr.inscrit LEFT JOIN Hardwarefr.config USING (pseudo) WHERE
inscrit.pseudo='Muse'
thd->thread_id=186

(the signal 11 occurs because I'm now using official 4.0.9 binaries and you
fix is not present)
Any idea of what could cause this kind of bad corruption in the keycache
recovery process ?

Thanks and regards,
Jocelyn

----- Original Message -----
From: "Sergei Golubchik"
To: "Jocelyn Fournier"
Cc:
Sent: Monday, January 27, 2003 4:38 PM
Subject: Re: Segfault during repair after a MySQL server crash


> Hi!
>
> On Jan 26, Jocelyn Fournier wrote:
> > Hi,
> >
> > How-to-repeat :
> >
> > Download ftp://support.mysql.com/pub/mysql/secret/configcrash.tar.gz and
try
> > to repair the table : it always crashes (even myisamchk -o segfault)
>
> Fixed, thanks.
> Though, I can hardly imagine how you managed to create such a file,
> without manually editing MYI header :)
> Now, it's:
>
> % myisamchk -r config
> myisamchk: error: 'config' doesn't have a correct index definition. You
need to recreate it before you can do a repair
> %
>
> Of course, REPAIR TABLE ... USE_FRM repairs this table perfectly.
>
> Regards,
> Sergei
>
> --
> MySQL Development Team
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Sergei Golubchik
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
> /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
> <___/
>
> ------------------------------------------------------------ ---------
> 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 bugs-thread13602@lists.mysql.com
> To unsubscribe, e-mail
>
>


------------------------------------------------------------ ---------
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 bugs-thread13665@lists.mysql.com
To unsubscribe, e-mail

Re: Segfault during repair after a MySQL server crash

Hi,

Any news about this bug ? :) (and the status messages written in the wrong
place in show processlist during auto-repair process)

Thanks !
Jocelyn
----- Original Message -----
From: "Jocelyn Fournier"
To: "Sergei Golubchik"
Cc:
Sent: Tuesday, February 04, 2003 1:30 PM
Subject: Re: Segfault during repair after a MySQL server crash


> Hi sergei,
>
> I reproduced exactely the same problem after a crash in 4.1.
> It seems the myisam-recover=BACKUP,FORCE,QUICK option corrupt the file
when
> it try to repair it with keycache :
>
> 030204 13:19:06 Warning: Recovering table: './Hardwarefr/config'
> 030204 13:19:08 Warning: Checking table:
> './forum_hardwarefr/searchmainhardwarefr13'
> 030204 13:19:08 1 clients is using or hasn't closed the table properly
> 030204 13:19:08 Warning: Retrying repair of: './Hardwarefr/config' with
> keycache
> 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=536870912
> read_buffer_size=1044480
> sort_buffer_size=2097144
> max_used_connections=38
> max_connections=320
> threads_connected=32
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
> 1506045 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>
> thd=0x5aaec6e0
> 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...
> Cannot determine thread, fp=0xbb5fd0a8, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x80d6ffb
> 0x40034f54
> 0x832cb40
> 0x832cc2f
> 0x832cc76
> 0x832d03b
> 0x83271ca
> 0x8326b16
> 0x812be42
> 0x812bab0
> 0x812c486
> 0x80f4d9f
> 0x80f4152
> 0x80f4e93
> 0x80f5148
> 0x80e134f
> 0x80e4de5
> 0x80e043b
> 0x80dfe6d
> 0x80df69e
> 0x400320ba
> 0x40180d6a
> New value of fp=(nil) failed sanity check, terminating stack trace!
> Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow
> instructions on how to resolve the stack trace. Resolved
> stack trace is much more helpful in diagnosing the problem, so please do
> resolve it
> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort...
> thd->query at 0x890ef78 = SELECT
>
email,password,nbrpost_forum,image_forum,signature_forum,icq ,IP,homepage,dat
>
einscr,hobby,occupation,status,image,mailv,validation,citati on,ville,smilies
> ,config.config,js,zlib,online,topicpp,lastpost,birthday, oldquote,modomp
> FROM Hardwarefr.inscrit LEFT JOIN Hardwarefr.config USING (pseudo) WHERE
> inscrit.pseudo='Muse'
> thd->thread_id=186
>
> (the signal 11 occurs because I'm now using official 4.0.9 binaries and
you
> fix is not present)
> Any idea of what could cause this kind of bad corruption in the keycache
> recovery process ?
>
> Thanks and regards,
> Jocelyn
>
> ----- Original Message -----
> From: "Sergei Golubchik"
> To: "Jocelyn Fournier"
> Cc:
> Sent: Monday, January 27, 2003 4:38 PM
> Subject: Re: Segfault during repair after a MySQL server crash
>
>
> > Hi!
> >
> > On Jan 26, Jocelyn Fournier wrote:
> > > Hi,
> > >
> > > How-to-repeat :
> > >
> > > Download ftp://support.mysql.com/pub/mysql/secret/configcrash.tar.gz
and
> try
> > > to repair the table : it always crashes (even myisamchk -o segfault)
> >
> > Fixed, thanks.
> > Though, I can hardly imagine how you managed to create such a file,
> > without manually editing MYI header :)
> > Now, it's:
> >
> > % myisamchk -r config
> > myisamchk: error: 'config' doesn't have a correct index definition. You
> need to recreate it before you can do a repair
> > %
> >
> > Of course, REPAIR TABLE ... USE_FRM repairs this table perfectly.
> >
> > Regards,
> > Sergei
> >
> > --
> > MySQL Development Team
> > __ ___ ___ ____ __
> > / |/ /_ __/ __/ __ \/ / Sergei Golubchik
> > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
> > /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
> > <___/
> >
> > ------------------------------------------------------------ ---------
> > 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 bugs-thread13602@lists.mysql.com
> > To unsubscribe, e-mail
> >
> >
>


------------------------------------------------------------ ---------
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 bugs-thread13791@lists.mysql.com
To unsubscribe, e-mail

Re: bug with myisam-recover

Hi!

On Jan 26, Jocelyn Fournier wrote:
>
> BTW I just see another bug using myisam-recover=BACKUP,FORCE,QUICK.
> A show processlist, during the repair of some tables, showed :
>
> | 10 | mysql | localhost | Hardwarefr | Query | 649 | Repair by sorting
> | SELECT COUNT(*) FROM threadhardwarefr1
>
> or even
>
> | 2052 | DELAYED | localhost | Hardwarefr | Delayed_insert | 44 | Checking
> table |
>
> => It seems the status messages are sometimes written in the wrong place
> during the auto-repair process.

I wasn't able to reproduce this. :(

Regards,
Sergei

--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/

------------------------------------------------------------ ---------
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 bugs-thread13792@lists.mysql.com
To unsubscribe, e-mail

Re: Segfault during repair after a MySQL server crash

Hi!

On Feb 04, Jocelyn Fournier wrote:
> Hi sergei,
>
> I reproduced exactely the same problem after a crash in 4.1.
> It seems the myisam-recover=BACKUP,FORCE,QUICK option corrupt the file when
> it try to repair it with keycache :

No crash for me on your table :)

Regards,
Sergei

--
MySQL Development Team
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/

------------------------------------------------------------ ---------
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 bugs-thread13793@lists.mysql.com
To unsubscribe, e-mail