Package: mysql-server-5.0
Version: 5.0.18-7
Severity: normal

Note: this may be a duplicate of #343639, but too many people have tried
to take over bugs that I've seen, so I won't comment while the moreinfo
bit is on there.  Plus there is more than one bug "reported in the last
couple of months", which is what [testing] is for anyhow...

I am running testing (primarily) and caught the mysql upgrade last
Friday.

Today I saw the following messages in my syslog:

mysqld[15682]: 060224 10:56:38 [ERROR] /usr/sbin/mysqld: Incorrect key
file for table './wikidb/searchindex.MYI'; try to repair it
mysqld[15682]: 060224 10:56:38 [ERROR] /usr/sbin/mysqld: Incorrect key
file for table './wikidb/searchindex.MYI'; try to repair it

running mysqlchk:

wikidb.archive                                     OK
wikidb.blobs                                       OK
wikidb.brokenlinks                                 OK
wikidb.categorylinks                               OK
wikidb.cur                                         OK
wikidb.hitcounter
note     : The storage engine for the table doesn't support check
wikidb.image                                       OK
wikidb.imagelinks                                  OK
wikidb.interwiki                                   OK
wikidb.ipblocks                                    OK
wikidb.links                                       OK
wikidb.linkscc                                     OK
wikidb.math                                        OK
wikidb.objectcache                                 OK
wikidb.old                                         OK
wikidb.oldimage                                    OK
wikidb.querycache                                  OK
wikidb.recentchanges                               OK
wikidb.searchindex
error    : Key in wrong position at page 4096
error    : Corrupt
wikidb.site_stats                                  OK
wikidb.user                                        OK
wikidb.user_newtalk                                OK
wikidb.watchlist                                   OK

from mysql:

mysql> use wikidb;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> check table searchindex extended;
+--------------------+-------+----------+--------------------------------------------------------------------------+
| Table              | Op    | Msg_type | Msg_text
|
+--------------------+-------+----------+--------------------------------------------------------------------------+
| wikidb.searchindex | check | error    | Table './wikidb/searchindex'
is marked as crashed and should be repaired |
+--------------------+-------+----------+--------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> repair table searchindex extended;
+--------------------+--------+----------+----------+
| Table              | Op     | Msg_type | Msg_text |
+--------------------+--------+----------+----------+
| wikidb.searchindex | repair | status   | OK       |
+--------------------+--------+----------+----------+
1 row in set (0.12 sec)

mysql> check table searchindex extended;
+--------------------+-------+----------+------------------------------------+
| Table              | Op    | Msg_type | Msg_text
|
+--------------------+-------+----------+------------------------------------+
| wikidb.searchindex | check | error    | Key in wrong position at page
4096 |
| wikidb.searchindex | check | error    | Corrupt
|
+--------------------+-------+----------+------------------------------------+
2 rows in set (0.00 sec)

>From Google, I hear very few reasons why a repaired table would
immediately corrupt, one of the possible reasons is that a column name
in the table has just been declared a keyword.  Are any of the column
names here MySQL keywords?

mysql> describe searchindex;
+----------+-----------------+------+-----+---------+-------+
| Field    | Type            | Null | Key | Default | Extra |
+----------+-----------------+------+-----+---------+-------+
| si_page  | int(8) unsigned | NO   | PRI | 0       |       |
| si_title | varchar(255)    | NO   | MUL |         |       |
| si_text  | mediumtext      | NO   | MUL |         |       |
+----------+-----------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

At the moment the table appears to be usable, at least until a CHECK
operation comes and re-corrupts the table.  This smells like something
upstream though, either CHECK needs to properly identify (un)recoverable errors 
or REPAIR needs to successfully correct them...

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mysql-server-5.0 depends on:
ii  adduser                       3.80       Add and remove users and groups
ii  debconf [debconf-2.0]         1.4.70     Debian configuration management sy
ii  libc6                         2.3.5-13   GNU C Library: Shared libraries an
ii  libdbi-perl                   1.50-2     Perl5 database interface by Tim Bu
ii  libgcc1                       1:4.0.2-9  GCC support library
ii  libmysqlclient15              5.0.18-7   mysql database client library
ii  libncurses5                   5.5-1      Shared libraries for terminal hand
ii  libreadline5                  5.1-6      GNU readline and history libraries
ii  libstdc++6                    4.0.2-9    The GNU Standard C++ Library v3
ii  libwrap0                      7.6.dbs-8  Wietse Venema's TCP wrappers libra
ii  mysql-client-5.0              5.0.18-7   mysql database client binaries
ii  mysql-common                  5.0.18-7   mysql database common files (e.g. 
ii  passwd                        1:4.0.14-4 change and administer password and
ii  perl                          5.8.7-10   Larry Wall's Practical Extraction 
ii  psmisc                        22.1-1     Utilities that use the proc filesy
ii  zlib1g                        1:1.2.3-9  compression library - runtime

Versions of packages mysql-server-5.0 recommends:
ii  mailx            1:8.1.2-0.20050715cvs-1 A simple mail user agent

-- debconf information:
  mysql-server-5.0/really_downgrade: false
  mysql-server-5.0/start_on_boot: true
  mysql-server-5.0/mysql_update_hints1:
  mysql-server-5.0/nis_warning:
  mysql-server-5.0/postrm_remove_databases: false
  mysql-server-5.0/no_upgrade_with_isam_tables:
* mysql-server-5.0/mysql_install_db_notes:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to