myisamchk fails to recover a corrupted table

Hi,

I've just encountered a problem with myisamchk on a corrupted table.

How-to-repeat :

anedroide:/var/lib/mysql/var# myisamchk -o cookie.MYI
- recovering (with keycache) MyISAM-table 'cookie.MYI'
Data records: 70572
Found block with too small length at 21127024; Skipped
Duplicate key 1 for record at 21513280 against new record at 20111600
myisamchk: Error writing file 'UNOPENED' (Errcode: 9)
MyISAM-table 'cookie.MYI' is not fixed because of errors
Try fixing it by using the --safe-recover (-o) or the --force (-f) option

(I already tried to regenerate the .MYI et .frm files, but it doesn't change
anything, so it seems to be the data file which is corrupted)

I uploaded the table on
ftp://support.mysql.com/pub/mysql/secret/cookie.tar.gz

(I'm using latest mysql-4.0.4 available version)

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

Re: myisamchk fails to recover a corrupted table

Jocelyn Fournier writes:
> Hi,
>
> I've just encountered a problem with myisamchk on a corrupted table.
>
> How-to-repeat :
>
> anedroide:/var/lib/mysql/var# myisamchk -o cookie.MYI
> - recovering (with keycache) MyISAM-table 'cookie.MYI'
> Data records: 70572
> Found block with too small length at 21127024; Skipped
> Duplicate key 1 for record at 21513280 against new record at 20111600
> myisamchk: Error writing file 'UNOPENED' (Errcode: 9)
> MyISAM-table 'cookie.MYI' is not fixed because of errors
> Try fixing it by using the --safe-recover (-o) or the --force (-f) option
>
> (I already tried to regenerate the .MYI et .frm files, but it doesn't change
> anything, so it seems to be the data file which is corrupted)
>
> I uploaded the table on
> ftp://support.mysql.com/pub/mysql/secret/cookie.tar.gz
>
> (I'm using latest mysql-4.0.4 available version)
>
> Regards,
> Jocelyn
>

HI!

Your table is truly terribly crashed.

I tried all tricks and none helped.

Can you check whether your file system and / or disk are OK ??

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


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

Re: myisamchk fails to recover a corrupted table

Hi,

In fact, it seems those particular table doesn't support the backup done by
mysqldump.
I've just taken a look at the MySQL error file and I can see :

020830 17:48:40 mysqld started
/usr/local/mysql/libexec/mysqld: ready for connections
020901 2:30:36 Warning: Retrying repair of: './forum/cookie' with keycache
020901 2:36:01 /usr/local/mysql/libexec/mysqld: Normal shutdown

020901 2:36:03 /usr/local/mysql/libexec/mysqld: Shutdown Complete

020901 02:36:03 mysqld ended

020901 02:36:07 mysqld started
/usr/local/mysql/libexec/mysqld: ready for connections
020901 2:36:24 Warning: Retrying repair of: './forum/cookie' with keycache
020901 2:40:56 Warning: Retrying repair of: './forum/cookie' with keycache
020901 2:42:53 /usr/local/mysql/libexec/mysqld: Normal shutdown

020901 2:42:53 /usr/local/mysql/libexec/mysqld: Shutdown Complete

020901 02:42:53 mysqld ended

020901 02:45:54 mysqld started
/usr/local/mysql/libexec/mysqld: ready for connections
020901 2:47:03 Warning: Retrying repair of: './forum/cookie' with keycache
020901 2:48:30 /usr/local/mysql/libexec/mysqld: Normal shutdown

020901 2:48:31 /usr/local/mysql/libexec/mysqld: Shutdown Complete

020901 02:48:31 mysqld ended

020901 02:48:36 mysqld started
/usr/local/mysql/libexec/mysqld: ready for connections
020901 2:57:29 /usr/local/mysql/libexec/mysqld: Normal shutdown

020901 2:57:30 /usr/local/mysql/libexec/mysqld: Shutdown Complete

020901 02:57:30 mysqld ended

020901 02:57:48 mysqld started
/usr/local/mysql/libexec/mysqld: ready for connections
020901 3:48:17 /usr/local/mysql/libexec/mysqld: Normal shutdown

020901 3:48:18 /usr/local/mysql/libexec/mysqld: Shutdown Complete

020901 03:48:18 mysqld ended

020901 03:48:21 mysqld started
/usr/local/mysql/libexec/mysqld: ready for connections
020901 3:55:00 /usr/local/mysql/libexec/mysqld: Normal shutdown

020901 3:55:00 /usr/local/mysql/libexec/mysqld: Shutdown Complete

020901 03:55:00 mysqld ended

020901 03:55:46 mysqld started
/usr/local/mysql/libexec/mysqld: ready for connections
020901 3:57:11 Warning: Retrying repair of: './forum/cookie' with keycache

note that each mysqld ended / started correspond to a backup
(mysqldump --add-drop-table --compress --extended-insert --all-databases --c
omplete-insert > /home/tmp/bases-presencepc-"$DATETGZ".sql ).
In this log, cookie is a new freshly created table.

(BTW mysqldump seems to automatically shutdown mysqld ?)

Regards,
Jocelyn

----- Original Message -----
From: "Sinisa Milivojevic"
To:
Cc:
Sent: Monday, September 02, 2002 3:31 PM
Subject: Re: myisamchk fails to recover a corrupted table


> Jocelyn Fournier writes:
> > Hi,
> >
> > I've just encountered a problem with myisamchk on a corrupted table.
> >
> > How-to-repeat :
> >
> > anedroide:/var/lib/mysql/var# myisamchk -o cookie.MYI
> > - recovering (with keycache) MyISAM-table 'cookie.MYI'
> > Data records: 70572
> > Found block with too small length at 21127024; Skipped
> > Duplicate key 1 for record at 21513280 against new record at
20111600
> > myisamchk: Error writing file 'UNOPENED' (Errcode: 9)
> > MyISAM-table 'cookie.MYI' is not fixed because of errors
> > Try fixing it by using the --safe-recover (-o) or the --force (-f)
option
> >
> > (I already tried to regenerate the .MYI et .frm files, but it doesn't
change
> > anything, so it seems to be the data file which is corrupted)
> >
> > I uploaded the table on
> > ftp://support.mysql.com/pub/mysql/secret/cookie.tar.gz
> >
> > (I'm using latest mysql-4.0.4 available version)
> >
> > Regards,
> > Jocelyn
> >
>
> HI!
>
> Your table is truly terribly crashed.
>
> I tried all tricks and none helped.
>
> Can you check whether your file system and / or disk are OK ??
>
> --
> Regards,
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> <___/ www.mysql.com
>
>
> ------------------------------------------------------------ ---------
> 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-thread12463@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-thread12466@lists.mysql.com
To unsubscribe, e-mail

Re: myisamchk fails to recover a corrupted table

Jocelyn Fournier writes:
> Hi,
>
> In fact, it seems those particular table doesn't support the backup done by
> mysqldump.
> I've just taken a look at the MySQL error file and I can see :
>
> 020830 17:48:40 mysqld started
> /usr/local/mysql/libexec/mysqld: ready for connections
> 020901 2:30:36 Warning: Retrying repair of: './forum/cookie' with keycache
> 020901 2:36:01 /usr/local/mysql/libexec/mysqld: Normal shutdown
>
> 020901 2:36:03 /usr/local/mysql/libexec/mysqld: Shutdown Complete
>
> 020901 02:36:03 mysqld ended
>

[skip]

>
> note that each mysqld ended / started correspond to a backup
> (mysqldump --add-drop-table --compress --extended-insert --all-databases --c
> omplete-insert > /home/tmp/bases-presencepc-"$DATETGZ".sql ).
> In this log, cookie is a new freshly created table.
>
> (BTW mysqldump seems to automatically shutdown mysqld ?)
>
> Regards,
> Jocelyn
>

No, mysqldump should not shutdown a server.

Have you checked file system / disk ??

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


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

Re: myisamchk fails to recover a corrupted table

Hi,

Yes FS is ok (ReiserFS/Kernel 2.4.19 + RAID 5 on mylex acceleraid170, and no
failure are reported :

anedroide:/proc/rd/c0# cat current_status
***** DAC960 RAID Driver Version 2.4.11 of 11 October 2001 *****
Copyright 1998-2001 by Leonard N. Zubkoff
Configuring Mylex AcceleRAID 170 PCI RAID Controller
Firmware Version: 6.00-07, Channels: 1, Memory Size: 64MB
PCI Bus: 1, Device: 2, Function: 1, I/O Address: Unassigned
PCI Address: 0xFC0FE000 mapped at 0xF8800000, IRQ Channel: 27
Controller Queue Depth: 512, Maximum Blocks per Command: 2048
Driver Queue Depth: 511, Scatter/Gather Limit: 128 of 257 Segments
Physical Devices:
0:1 Vendor: FUJITSU Model: MAJ3091MC Revision: 0115
Wide Synchronous at 160 MB/sec
Serial Number: 50030509
Disk Status: Online, 17813504 blocks
0:3 Vendor: FUJITSU Model: MAJ3091MC Revision: 0115
Wide Synchronous at 160 MB/sec
Serial Number: 50030443
Disk Status: Online, 17813504 blocks
Errors - Parity: 0, Soft: 0, Hard: 0, Misc: 0
Timeouts: 0, Retries: 0, Aborts: 1, Predicted: 0
0:6 Vendor: FUJITSU Model: MAJ3091MC Revision: 0115
Wide Synchronous at 160 MB/sec
Serial Number: 50030456
Disk Status: Online, 17813504 blocks
Errors - Parity: 0, Soft: 0, Hard: 0, Misc: 0
Timeouts: 0, Retries: 0, Aborts: 1, Predicted: 0
0:7 Vendor: MYLEX Model: AcceleRAID 170 Revision: 0600
Wide Synchronous at 160 MB/sec
Serial Number:
0:11 Vendor: FUJITSU Model: MAJ3091MC Revision: 0115
Wide Synchronous at 160 MB/sec
Serial Number: 50030475
Disk Status: Online, 17813504 blocks
Errors - Parity: 0, Soft: 0, Hard: 0, Misc: 0
Timeouts: 0, Retries: 0, Aborts: 1, Predicted: 0
Logical Drives:
/dev/rd/c0d0: RAID-5, Online, 35618816 blocks
Logical Device Initialized, BIOS Geometry: 255/63
Stripe Size: 64KB, Segment Size: 8KB
Read Cache Disabled, Write Cache Enabled
/dev/rd/c0d1: RAID-7, Online, 17809408 blocks
Logical Device Initialized, BIOS Geometry: 255/63
Stripe Size: 64KB, Segment Size: 8KB
Read Cache Disabled, Write Cache Disabled
No Rebuild or Consistency Check in Progress)

Moreover, I have more than 3000 tables and it's the only table which is
affected by the problem (lots of insert / update / select)

Regards,
Jocelyn

----- Original Message -----
From: "Sinisa Milivojevic"
To:
Cc:
Sent: Monday, September 02, 2002 8:15 PM
Subject: Re: myisamchk fails to recover a corrupted table


> Jocelyn Fournier writes:
> > Hi,
> >
> > In fact, it seems those particular table doesn't support the backup done
by
> > mysqldump.
> > I've just taken a look at the MySQL error file and I can see :
> >
> > 020830 17:48:40 mysqld started
> > /usr/local/mysql/libexec/mysqld: ready for connections
> > 020901 2:30:36 Warning: Retrying repair of: './forum/cookie' with
keycache
> > 020901 2:36:01 /usr/local/mysql/libexec/mysqld: Normal shutdown
> >
> > 020901 2:36:03 /usr/local/mysql/libexec/mysqld: Shutdown Complete
> >
> > 020901 02:36:03 mysqld ended
> >
>
> [skip]
>
> >
> > note that each mysqld ended / started correspond to a backup
> >
(mysqldump --add-drop-table --compress --extended-insert --all-databases --c
> > omplete-insert > /home/tmp/bases-presencepc-"$DATETGZ".sql ).
> > In this log, cookie is a new freshly created table.
> >
> > (BTW mysqldump seems to automatically shutdown mysqld ?)
> >
> > Regards,
> > Jocelyn
> >
>
> No, mysqldump should not shutdown a server.
>
> Have you checked file system / disk ??
>
> --
> Regards,
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> <___/ www.mysql.com
>
>
>
>


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

Re: myisamchk fails to recover a corrupted table

Hi,

Finally it's not linked to mysqldump at all.
In fact the problem seems to have occured after a server crash.
The error log displays :


020824 17:12:16 read_next: Got error 127 when reading table ./forum/cookie
020825 11:46:50 read_next: Got error 127 when reading table ./forum/cookie

and then the errors disappears (the table ought to be still broken, but
usable).
It's only since yesterday the table completely and definitively crashed.

Regards,
Jocelyn

----- Original Message -----
From: "Sinisa Milivojevic"
To:
Cc:
Sent: Monday, September 02, 2002 8:15 PM
Subject: Re: myisamchk fails to recover a corrupted table


> Jocelyn Fournier writes:
> > Hi,
> >
> > In fact, it seems those particular table doesn't support the backup done
by
> > mysqldump.
> > I've just taken a look at the MySQL error file and I can see :
> >
> > 020830 17:48:40 mysqld started
> > /usr/local/mysql/libexec/mysqld: ready for connections
> > 020901 2:30:36 Warning: Retrying repair of: './forum/cookie' with
keycache
> > 020901 2:36:01 /usr/local/mysql/libexec/mysqld: Normal shutdown
> >
> > 020901 2:36:03 /usr/local/mysql/libexec/mysqld: Shutdown Complete
> >
> > 020901 02:36:03 mysqld ended
> >
>
> [skip]
>
> >
> > note that each mysqld ended / started correspond to a backup
> >
(mysqldump --add-drop-table --compress --extended-insert --all-databases --c
> > omplete-insert > /home/tmp/bases-presencepc-"$DATETGZ".sql ).
> > In this log, cookie is a new freshly created table.
> >
> > (BTW mysqldump seems to automatically shutdown mysqld ?)
> >
> > Regards,
> > Jocelyn
> >
>
> No, mysqldump should not shutdown a server.
>
> Have you checked file system / disk ??
>
> --
> Regards,
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
> /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
> <___/ www.mysql.com
>
>
>
>


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

Re: myisamchk fails to recover a corrupted table

Jocelyn Fournier writes:
> Hi,
>
> Finally it's not linked to mysqldump at all.
> In fact the problem seems to have occured after a server crash.
> The error log displays :
>
>
> 020824 17:12:16 read_next: Got error 127 when reading table ./forum/cookie
> 020825 11:46:50 read_next: Got error 127 when reading table ./forum/cookie
>
> and then the errors disappears (the table ought to be still broken, but
> usable).
> It's only since yesterday the table completely and definitively crashed.
>
> Regards,
> Jocelyn

We can take one more look at the table, but we can not promise much.

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


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

Re: myisamchk fails to recover a corrupted table

Jocelyn Fournier writes:
> Hi,
>
> Finally it's not linked to mysqldump at all.
> In fact the problem seems to have occured after a server crash.
> The error log displays :
>
>
> 020824 17:12:16 read_next: Got error 127 when reading table ./forum/cookie
> 020825 11:46:50 read_next: Got error 127 when reading table ./forum/cookie
>
> and then the errors disappears (the table ought to be still broken, but
> usable).
> It's only since yesterday the table completely and definitively crashed.
>
> Regards,
> Jocelyn

Can you find out from your update or binary log, which command has
crashed a table ??

--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


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