Crash with REPAIR TABLE and MySQL-4.0.2

Hi,

I've just hit a bug in latest mysql-4.0.2 source.

How-to-repeat :

CREATE TABLE `posts1` (
`post_id` mediumint(8) unsigned NOT NULL auto_increment,
`topic_id` mediumint(8) unsigned NOT NULL default '0',
`post_time` datetime NOT NULL default '0000-00-00 00:00:00',
`post_text` text NOT NULL,
`icon_url` varchar(10) NOT NULL default '',
`sign` tinyint(1) unsigned NOT NULL default '0',
`post_edit` varchar(150) NOT NULL default '',
`poster_login` varchar(35) NOT NULL default '',
`ip` varchar(15) NOT NULL default '',
PRIMARY KEY (`post_id`),
KEY `post_time` (`post_time`),
KEY `ip` (`ip`),
KEY `poster_login` (`poster_login`),
KEY `topic_id` (`topic_id`),
FULLTEXT KEY `post_text` (`post_text`)
) TYPE=MyISAM;

INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
INSERT INTO posts1 (post_text) VALUES ('ceci est un test');

REPAIR TABLE posts1;


mysql> CREATE TABLE `posts1` (
-> `post_id` mediumint(8) unsigned NOT NULL auto_increment,
-> `topic_id` mediumint(8) unsigned NOT NULL default '0',
-> `post_time` datetime NOT NULL default '0000-00-00 00:00:00',
-> `post_text` text NOT NULL,
-> `icon_url` varchar(10) NOT NULL default '',
-> `sign` tinyint(1) unsigned NOT NULL default '0',
-> `post_edit` varchar(150) NOT NULL default '',
-> `poster_login` varchar(35) NOT NULL default '',
-> `ip` varchar(15) NOT NULL default '',
-> PRIMARY KEY (`post_id`),
-> KEY `post_time` (`post_time`),
-> KEY `ip` (`ip`),
-> KEY `poster_login` (`poster_login`),
-> KEY `topic_id` (`topic_id`),
-> FULLTEXT KEY `post_text` (`post_text`)
-> ) TYPE=MyISAM;
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Query OK, 1 row affected (0.00 sec)

mysql> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Query OK, 1 row affected (0.00 sec)

mysql> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Query OK, 1 row affected (0.00 sec)

mysql> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Query OK, 1 row affected (0.00 sec)

mysql> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Query OK, 1 row affected (0.00 sec)

mysql> REPAIR TABLE posts1;
ERROR 2013: Lost connection to MySQL server during query


Regards,
Jocelyn Fournier




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

Crash with REPAIR TABLE and MySQL-4.0.2

Hi!

>>>>> "Jocelyn" == Jocelyn Fournier writes:

Jocelyn> Hi,
Jocelyn> I've just hit a bug in latest mysql-4.0.2 source.

Jocelyn> How-to-repeat :

Jocelyn> CREATE TABLE `posts1` (
Jocelyn> `post_id` mediumint(8) unsigned NOT NULL auto_increment,
Jocelyn> `topic_id` mediumint(8) unsigned NOT NULL default '0',
Jocelyn> `post_time` datetime NOT NULL default '0000-00-00 00:00:00',
Jocelyn> `post_text` text NOT NULL,
Jocelyn> `icon_url` varchar(10) NOT NULL default '',
Jocelyn> `sign` tinyint(1) unsigned NOT NULL default '0',
Jocelyn> `post_edit` varchar(150) NOT NULL default '',
Jocelyn> `poster_login` varchar(35) NOT NULL default '',
Jocelyn> `ip` varchar(15) NOT NULL default '',
Jocelyn> PRIMARY KEY (`post_id`),
Jocelyn> KEY `post_time` (`post_time`),
Jocelyn> KEY `ip` (`ip`),
Jocelyn> KEY `poster_login` (`poster_login`),
Jocelyn> KEY `topic_id` (`topic_id`),
Jocelyn> FULLTEXT KEY `post_text` (`post_text`)
Jocelyn> ) TYPE=MyISAM;

Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');

Jocelyn> REPAIR TABLE posts1;

For me this worked :(

I will add this to our test suite and do a new test under purify.

Regards,
Monty

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

Re: Crash with REPAIR TABLE and MySQL-4.0.2

Hi,

Here is the stack trace I obtained :

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=268431360
record_buffer=1044480
sort_buffer=1048540
max_used_connections=0
max_connections=320
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 916208 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x83e6404
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=0xbff5ce68, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8090062 _Z15handle_segfaulti + 482
0x825a752 pthread_sighandler + 162
0x822801b sort_key_cmp + 15
0x823fc32 queue_insert + 82
0x822da60 merge_buffers + 362
0x822dd56 merge_index + 134
0x822c38f _create_index_by_sort + 1191
0x8224d84 mi_repair_by_sort + 2330
0x80f6bd0 _ZN9ha_myisam6repairEP3THDR17st_mi_check_paramb + 720
0x80f67de _ZN9ha_myisam6repairEP3THDP15st_ha_check_opt + 288
0x81038ef
_Z17mysql_admin_tableP3THDP13st_table_listP15st_ha_check_opt PKc13thr_lock_ty
pebjPFiS0_S2_S4_EM7handlerFiS0_S4_E + 2025
0x8103dec _Z18mysql_repair_tableP3THDP13st_table_listP15st_ha_check_op t +
178
0x8099f51 _Z21mysql_execute_commandv + 5913
0x809d322 _Z11mysql_parseP3THDPcj + 212
0x8097ce3 _Z16dispatch_command19enum_server_commandP3THDPcj + 1605
0x8097693 _Z10do_commandP3THD + 341
0x8096ccf _Z21handle_one_connectionPv + 673
0x8257ee8 pthread_start_thread + 200
0x828ff7a thread_start + 4
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 0x83e6d54 = REPAIR TABLE posts1
thd->thread_id=1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 1 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.

Monty, I send you the same mail with the mysqld.trace file corresponding to
this
bug attached.

Regards,
Jocelyn


----- Original Message -----
From: "Michael Widenius"
To: "Jocelyn Fournier"
Cc: "Bugs@Lists.Mysql.Com"
Sent: Friday, June 28, 2002 11:27 AM
Subject: Crash with REPAIR TABLE and MySQL-4.0.2


>
> Hi!
>
> >>>>> "Jocelyn" == Jocelyn Fournier writes:
>
> Jocelyn> Hi,
> Jocelyn> I've just hit a bug in latest mysql-4.0.2 source.
>
> Jocelyn> How-to-repeat :
>
> Jocelyn> CREATE TABLE `posts1` (
> Jocelyn> `post_id` mediumint(8) unsigned NOT NULL auto_increment,
> Jocelyn> `topic_id` mediumint(8) unsigned NOT NULL default '0',
> Jocelyn> `post_time` datetime NOT NULL default '0000-00-00 00:00:00',
> Jocelyn> `post_text` text NOT NULL,
> Jocelyn> `icon_url` varchar(10) NOT NULL default '',
> Jocelyn> `sign` tinyint(1) unsigned NOT NULL default '0',
> Jocelyn> `post_edit` varchar(150) NOT NULL default '',
> Jocelyn> `poster_login` varchar(35) NOT NULL default '',
> Jocelyn> `ip` varchar(15) NOT NULL default '',
> Jocelyn> PRIMARY KEY (`post_id`),
> Jocelyn> KEY `post_time` (`post_time`),
> Jocelyn> KEY `ip` (`ip`),
> Jocelyn> KEY `poster_login` (`poster_login`),
> Jocelyn> KEY `topic_id` (`topic_id`),
> Jocelyn> FULLTEXT KEY `post_text` (`post_text`)
> Jocelyn> ) TYPE=MyISAM;
>
> Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
> Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
> Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
> Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
> Jocelyn> INSERT INTO posts1 (post_text) VALUES ('ceci est un test');
>
> Jocelyn> REPAIR TABLE posts1;
>
> For me this worked :(
>
> I will add this to our test suite and do a new test under purify.
>
> Regards,
> Monty
>
> ------------------------------------------------------------ ---------
> 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-thread12149@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-thread12150@lists.mysql.com
To unsubscribe, e-mail

Crash with REPAIR TABLE and MySQL-4.0.2

Hi!

>>>>> "Jocelyn" == Jocelyn Fournier writes:

Jocelyn> Hi,
Jocelyn> I've just hit a bug in latest mysql-4.0.2 source.

Jocelyn> How-to-repeat :



Jocelyn> REPAIR TABLE posts1;

Sorry, when I tested this, I didn't use the lastest source.
I have now found and fixed this bug in the main source repository.

Regards,
Monty


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