mysql bug error 138

------=_NextPart_000_0006_01C322D8.95EB1E00
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

After having updated MySQL from rev 4.0.13 to rev 4.0.14, I had several
tables that crashed and that now give me this error back :

e-systemusr/local/mysql/bin# ./myisamchk -a
/usr/local/mysql/var/centralf/postscobe1.MYI

myisamchk: error: 138 when opening MyISAM-table
'/usr/local/mysql/var/centralf/postscobe1.MYI'

e-systemusr/local/mysql/bin#




------=_NextPart_000_0006_01C322D8.95EB1E00--

RE : mysql bug error 138

Oups i forgot this
I try to fix the table whit myisamchk but no result, after i try with
REPAIR TABLE and no result too but the REPAIR TABLE USE_FRM it's ok but
the table is empty.

How can i repair table without lose any data ?

-----Message d'origine-----
De=A0: Gilles [mailto:mysql@centralfr.com]=20
Envoyé : dimanche 25 mai 2003 16:14
À : bugs@lists.mysql.com
Objet=A0: mysql bug error 138

After having updated MySQL from rev 4.0.13 to rev 4.0.14, I had several
tables that crashed and that now give me this error back :

e-systemusr/local/mysql/bin# ./myisamchk -a
/usr/local/mysql/var/centralf/postscobe1.MYI

myisamchk: error: 138 when opening MyISAM-table
'/usr/local/mysql/var/centralf/postscobe1.MYI'

e-systemusr/local/mysql/bin#

=20



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org

Re: RE : mysql bug error 138

On Sun, 2003-05-25 at 18:49, Gilles wrote:
> Oups i forgot this
> I try to fix the table whit myisamchk but no result, after i try with
> REPAIR TABLE and no result too but the REPAIR TABLE USE_FRM it's ok but
> the table is empty.
>
> How can i repair table without lose any data ?

Gilles,

Is not this RAID table ?

pz@abyss:~> perror 138
Error code 138: Unknown error 138
138 = Unsupported extension used for table


Also any idea how this table got corrupted ? Is it just treated as
corrupted after upgrading ?
Does it works fine with MySQL 4.0.12

In any case we hardly can tell you a lot about this problem without the
data.

Please use the smallest table from the ones you've got corrupted and
upload it to:

ftp://support.mysql.com/pub/mysql/secret

and send mail to us with the name of it.

We shall take a look what could be the problem.

>
> -----Message d'origine-----
> De : Gilles [mailto:mysql@centralfr.com]
> Envoyé : dimanche 25 mai 2003 16:14
> À : bugs@lists.mysql.com
> Objet : mysql bug error 138
>
> After having updated MySQL from rev 4.0.13 to rev 4.0.14, I had several
> tables that crashed and that now give me this error back :
>
> e-systemusr/local/mysql/bin# ./myisamchk -a
> /usr/local/mysql/var/centralf/postscobe1.MYI
>
> myisamchk: error: 138 when opening MyISAM-table
> '/usr/local/mysql/var/centralf/postscobe1.MYI'
>
> e-systemusr/local/mysql/bin#
>
>
--
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: RE : mysql bug error 138

On Mon, 2003-05-26 at 14:43, Joce wrote:
> Hi,
>
> Could this table be created with 4.1, and then modified with 4.0 ?
> Has some changes been introduced in latest mysql tree to detect such cases ?
>

Joce,

There are such checks, but they should be in earlier releases as well,
also Data file structure was not affected in 4.1 only index was, so USE
FRM should not result in trashing all the data from table.

If it does it is bug and shall be fixed.


--
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

RE : RE : mysql bug error 138

No I hasn't any idea how this table have been corrupted
And the table work fine with 4.0.12. It's after upgrade that she has
crashed.
I've upload a table in ftp this name is "postscobe3.rar"


Regards,
Gilles.
-----Message d'origine-----
De=A0: Peter Zaitsev [mailto:peter@mysql.com]=20
Envoyé : lundi 26 mai 2003 10:12
À : Gilles
Cc=A0: bugs@lists.mysql.com
Objet=A0: Re: RE : mysql bug error 138

On Sun, 2003-05-25 at 18:49, Gilles wrote:
> Oups i forgot this
> I try to fix the table whit myisamchk but no result, after i try with
> REPAIR TABLE and no result too but the REPAIR TABLE USE_FRM it's ok
but
> the table is empty.
>=20
> How can i repair table without lose any data ?

Gilles,

Is not this RAID table ?=20

pz@abyss:~> perror 138
Error code 138: Unknown error 138
138 =3D Unsupported extension used for table


Also any idea how this table got corrupted ? Is it just treated as=20
corrupted after upgrading ?
Does it works fine with MySQL 4.0.12

In any case we hardly can tell you a lot about this problem without the=20
data.

Please use the smallest table from the ones you've got corrupted and
upload it to:

ftp://support.mysql.com/pub/mysql/secret=20

and send mail to us with the name of it.

We shall take a look what could be the problem.=20

>=20
> -----Message d'origine-----
> De : Gilles [mailto:mysql@centralfr.com]=20
> Envoy=E9 : dimanche 25 mai 2003 16:14
> =C0 : bugs@lists.mysql.com
> Objet : mysql bug error 138
>=20
> After having updated MySQL from rev 4.0.13 to rev 4.0.14, I had
several
> tables that crashed and that now give me this error back :
>=20
> e-systemusr/local/mysql/bin# ./myisamchk -a
> /usr/local/mysql/var/centralf/postscobe1.MYI
>=20
> myisamchk: error: 138 when opening MyISAM-table
> '/usr/local/mysql/var/centralf/postscobe1.MYI'
>=20
> e-systemusr/local/mysql/bin#
>=20
> =20
--=20
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com =20



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org

Re: RE : RE : mysql bug error 138

On Mon, 2003-05-26 at 18:07, Gilles wrote:
> No I hasn't any idea how this table have been corrupted
> And the table work fine with 4.0.12. It's after upgrade that she has
> crashed.
> I've upload a table in ftp this name is "postscobe3.rar"

Dear Giles,

This table was truly corrupted some tricky way, so
MySQL 3.23.57 is able to open it (thus finds corruption),
while MySQL 4.0 fails to do so.

On other hand REPAIR USE_FRM worked fine for me, repairing table.

Have not you been using this table with MySQL 4.1 ?

In MySQL 4.0 we have added more extensive header check which may be the
reason for such behavior.

We'll investigate this issue more internally and will let you know what
was wrong.

I've added it to our bugs database #506


--
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

RE : RE : RE : mysql bug error 138

Yes effectively, I used the tables with MySQL 4.1.=20
The REPAIR use FRM function works properly with MySQL 4.0.14 but
unfortunately, it dumps all the data from the table.=20
So, how can I proceed in order to recover all the data? Should I install
MySQL 3.23.x back to read the tables and make a backup from them? Then
uninstall it and use MySQL 4.0.x as I=92m doing now?

Regards,
Gilles.

-----Message d'origine-----
De=A0: Peter Zaitsev [mailto:peter@mysql.com]=20
Envoyé : lundi 26 mai 2003 17:54
À : Gilles
Cc=A0: bugs@lists.mysql.com
Objet=A0: Re: RE : RE : mysql bug error 138

On Mon, 2003-05-26 at 18:07, Gilles wrote:
> No I hasn't any idea how this table have been corrupted
> And the table work fine with 4.0.12. It's after upgrade that she has
> crashed.
> I've upload a table in ftp this name is "postscobe3.rar"

Dear Giles,

This table was truly corrupted some tricky way, so
MySQL 3.23.57 is able to open it (thus finds corruption),
while MySQL 4.0 fails to do so.

On other hand REPAIR USE_FRM worked fine for me, repairing table.

Have not you been using this table with MySQL 4.1 ?=20

In MySQL 4.0 we have added more extensive header check which may be the
reason for such behavior.

We'll investigate this issue more internally and will let you know what
was wrong.

I've added it to our bugs database #506


--=20
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com =20


--=20
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: =
http://lists.mysql.com/bugs?unsub=3Dmysql@centralfr.com



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org

Re: RE : RE : RE : mysql bug error 138

On Mon, 2003-05-26 at 22:53, Gilles wrote:
> Yes effectively, I used the tables with MySQL 4.1.

OK. This explains the thing.

MySQL 4.1 has modified table structure and so table should not be used
in earlier version of MySQL. MySQL versions previous to 4.0.13 just did
not have enough checks.

> The REPAIR use FRM function works properly with MySQL 4.0.14 but
> unfortunately, it dumps all the data from the table.

Hm. I've just checked with recent source tree and I got 262 rows in the
table. Is this what should be where ?

I'd suggest you to get the fresh pull from BK tree or use 4.0.13 both
shall not have problems with it.

MySQL 4.0.12 had some problem with REPAIR .. USE FRM, are you sure
you're not using this version or pre release of 4.0.13 (from BK tree)


> So, how can I proceed in order to recover all the data? Should I install
> MySQL 3.23.x back to read the tables and make a backup from them? Then
> uninstall it and use MySQL 4.0.x as Im doing now?

If above fails for some reason (no ideas why, it works for me) you might
wish to get myisamchk from earlier MySQL version (4.0.12 , 3.23.56) and
repair the table. There is no need to install whole server for this
purpose.


--
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

RE : RE : RE : RE : mysql bug error 138

Ok I updated the last bk tree and that works fine now with REPAIR TABLE
USE_FRM

Thanks a lot for your help.

Regards,
Gilles.


-----Message d'origine-----
De=A0: Peter Zaitsev [mailto:peter@mysql.com]=20
Envoyé : lundi 26 mai 2003 20:58
À : Gilles
Cc=A0: bugs@lists.mysql.com
Objet=A0: Re: RE : RE : RE : mysql bug error 138

On Mon, 2003-05-26 at 22:53, Gilles wrote:
> Yes effectively, I used the tables with MySQL 4.1.=20

OK. This explains the thing.

MySQL 4.1 has modified table structure and so table should not be used
in earlier version of MySQL. MySQL versions previous to 4.0.13 just did
not have enough checks.

> The REPAIR use FRM function works properly with MySQL 4.0.14 but
> unfortunately, it dumps all the data from the table.=20

Hm. I've just checked with recent source tree and I got 262 rows in the
table. Is this what should be where ?

I'd suggest you to get the fresh pull from BK tree or use 4.0.13 both
shall not have problems with it.

MySQL 4.0.12 had some problem with REPAIR .. USE FRM, are you sure
you're not using this version or pre release of 4.0.13 (from BK tree)


> So, how can I proceed in order to recover all the data? Should I
install
> MySQL 3.23.x back to read the tables and make a backup from them? Then
> uninstall it and use MySQL 4.0.x as Im doing now?

If above fails for some reason (no ideas why, it works for me) you might
wish to get myisamchk from earlier MySQL version (4.0.12 , 3.23.56) and
repair the table. There is no need to install whole server for this
purpose.=20


--=20
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com =20


--=20
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: =
http://lists.mysql.com/bugs?unsub=3Dmysql@centralfr.com



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org