Basic information: MySQL Table crash?
hi, someone else had a similar question, but didn't get any useful reply here on the list - I'll give it another try. :-) I need some basic understanding of MySQL table crashes. Maybe you can help me, I think it's so basic, no one ever wrote about it. (Until now! ;)) The mysql manual just says 'if you have a crashed table you can repair it.' Well... 1. What IS a table crash? What file/relation/... gets corrupted? And how does table recovery basically work? 2. If you had a crashed table: Where would you start looking for the reason? And where would you look next? 3. What precautions can one take to avoid a table crash? Are there any symptoms that show up when a table crash is about to happen? (like: out of swap memory, disk full, too much system load, ...?) Any comments/hints/links appreciated, thanks in advance, regards, Roman -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Basic information: MySQL Table crash?
Roman Eberle wrote: hi, someone else had a similar question, but didn't get any useful reply here on the list - I'll give it another try. :-) I need some basic understanding of MySQL table crashes. Maybe you can help me, I think it's so basic, no one ever wrote about it. (Until now! ;)) The mysql manual just says 'if you have a crashed table you can repair it.' Well... 1. What IS a table crash? What file/relation/... gets corrupted? And how does table recovery basically work? 2. If you had a crashed table: Where would you start looking for the reason? And where would you look next? 3. What precautions can one take to avoid a table crash? Are there any symptoms that show up when a table crash is about to happen? (like: out of swap memory, disk full, too much system load, ...?) Any comments/hints/links appreciated, thanks in advance, regards Roman #1 reason is powering off the computer without a proper shutdown. Get a UPS. -- Gerald L. Clark Sr. V.P. Development Supplier Systems Corporation Unix since 1982 Linux since 1992 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Table crash questions...
I have MySQL 4.1.8 installed on OS X 10.3.8 Server and I was in the process of building a PHP / MySQL website. After numerous connection issues with the MySQL server I decided to take a look at the status of my tables to check for corruption. After running myisamchk I managed to loose all my data records for one table. Not a big deal As I was just in a testing phase an planned to purge the data any way. The problem is now when I run myisamchk on this table I get: Warning: table file /pathtomydatafolder/users.MYI was created in MySQL 4.1+, use REPAIR TABLE ... USE_FRM to recreate it as a valid MySQL 4.0 table - recovering (with keycache) MyISAM-table 'users.MYI' Data records: 0 I tried REPAIR TABLE users USE_FRM with no help in resolving this message. Is this anything to even worry about?? Dan T
Re: Table crash questions...
Dan Tappin wrote: I have MySQL 4.1.8 installed on OS X 10.3.8 Server and I was in the process of building a PHP / MySQL website. After numerous connection issues with the MySQL server I decided to take a look at the status of my tables to check for corruption. After running myisamchk I managed to loose all my data records for one table. Not a big deal As I was just in a testing phase an planned to purge the data any way. The problem is now when I run myisamchk on this table I get: Warning: table file /pathtomydatafolder/users.MYI was created in MySQL 4.1+, use REPAIR TABLE ... USE_FRM to recreate it as a valid MySQL 4.0 table - recovering (with keycache) MyISAM-table 'users.MYI' Data records: 0 You have installed mysql 4.1.8, but this error message appears to come from mysql 4.0.x. Any possibility you started the wrong server? Which leads me to wonder which version of myisamchk you ran. A PATH problem, perhaps? I tried REPAIR TABLE users USE_FRM with no help in resolving this message. Is this anything to even worry about?? Dan T Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Table crash questions...
Good call... I should have figured that out my self. The old version was 2.6: /usr/bin/myisamchk (v2.6) /usr/local/mysql-standard-4.1.8-apple-darwin7.6.0-powerpc/bin/myisamchk (v2.7) This is likely why I lost my data in the first place. Dan T On Feb 16, 2005, at 10:57 AM, Michael Stassen wrote: Dan Tappin wrote: I have MySQL 4.1.8 installed on OS X 10.3.8 Server and I was in the process of building a PHP / MySQL website. After numerous connection issues with the MySQL server I decided to take a look at the status of my tables to check for corruption. After running myisamchk I managed to loose all my data records for one table. Not a big deal As I was just in a testing phase an planned to purge the data any way. The problem is now when I run myisamchk on this table I get: Warning: table file /pathtomydatafolder/users.MYI was created in MySQL 4.1+, use REPAIR TABLE ... USE_FRM to recreate it as a valid MySQL 4.0 table - recovering (with keycache) MyISAM-table 'users.MYI' Data records: 0 You have installed mysql 4.1.8, but this error message appears to come from mysql 4.0.x. Any possibility you started the wrong server? Which leads me to wonder which version of myisamchk you ran. A PATH problem, perhaps? I tried REPAIR TABLE users USE_FRM with no help in resolving this message. Is this anything to even worry about?? Dan T -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
table crash (error127) using v4.0.15 JDBC
Hi I'm working with mysql 4.0.15 for some software of ours and we are experiencing a random table crash. we have 30 MyISAM tables in our database and we're using JDBC to connect to them. Sometimes, very rarely, one of the tables crashes. It has nothing special compared to the other tables (int, varchars, datetimes and a blob), and it's one of the least accessed. We checked all the requests, they all work separately. I may add that 6 processes are accessing the base at the same time but only one of them is accessing the table that crashes, and there are always at least 5 seconds between each request on this table. for the whole base, there are 1 to 5 requests per second. It seems it's a very random bug. Never crashed buring the development, twice during the tests, then not during some time, then once during some tests at the custommers', and until now, never during the production phase, whereas there are far more requests than during the tests... I know how to repair the tables, but our software being realtime, it's a bit annoying to have to stop everything, repair and restart. Even dropping and creating the table again can lead to a further crash. Well so here is my question : i'm wondering whether the crashes could come from our version of the ConnectorJ : mysql-connector-java-2.0.14-bin.jar ?? nota bene : we couldn't use the 3.0.8 version at the moment we began coding because it had an annoying java access-rights bug (that seems corrected on the 3.0.9). Another possibility is some issue with using some toad-like mysql manager at the same time as the 6 processes...could be. If any of you has experienced a compatibility issue related to mysql 4 and connector 2, please be so kind as telling me. Thanks Fabien
RE: table crash (error127) using v4.0.15 JDBC
Are the crashes occurring on the same machines? Or random machines? Can you track the disk activity at the time the table is being marked as corrupt? Are you tracking the database activity? -Original Message- From: fabien marsaud [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 5:52 AM To: [EMAIL PROTECTED] Subject: table crash (error127) using v4.0.15 JDBC Hi I'm working with mysql 4.0.15 for some software of ours and we are experiencing a random table crash. we have 30 MyISAM tables in our database and we're using JDBC to connect to them. Sometimes, very rarely, one of the tables crashes. It has nothing special compared to the other tables (int, varchars, datetimes and a blob), and it's one of the least accessed. We checked all the requests, they all work separately. I may add that 6 processes are accessing the base at the same time but only one of them is accessing the table that crashes, and there are always at least 5 seconds between each request on this table. for the whole base, there are 1 to 5 requests per second. It seems it's a very random bug. Never crashed buring the development, twice during the tests, then not during some time, then once during some tests at the custommers', and until now, never during the production phase, whereas there are far more requests than during the tests... I know how to repair the tables, but our software being realtime, it's a bit annoying to have to stop everything, repair and restart. Even dropping and creating the table again can lead to a further crash. Well so here is my question : i'm wondering whether the crashes could come from our version of the ConnectorJ : mysql-connector-java-2.0.14-bin.jar ?? nota bene : we couldn't use the 3.0.8 version at the moment we began coding because it had an annoying java access-rights bug (that seems corrected on the 3.0.9). Another possibility is some issue with using some toad-like mysql manager at the same time as the 6 processes...could be. If any of you has experienced a compatibility issue related to mysql 4 and connector 2, please be so kind as telling me. Thanks Fabien -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: table crash (error127) using v4.0.15 JDBC
it happened on 3 different machines (2*win2000 1*win2003) we have a big logger running at the same time and it tells nothing partiular about the disk activity. else i have had a mysql 4.0.x + 4.1.0 beta at home taking a lot of requests for a quite a long time now (requests are performed thru php, not java this time), and no crash ever occured. that's why i was asking for a possible ConnectorJ issue. I'm gonna read its changelog, who knows... f. - Original Message - From: Victor Pendleton [EMAIL PROTECTED] To: 'fabien marsaud' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 2:51 PM Subject: RE: table crash (error127) using v4.0.15 JDBC Are the crashes occurring on the same machines? Or random machines? Can you track the disk activity at the time the table is being marked as corrupt? Are you tracking the database activity? -Original Message- From: fabien marsaud [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 5:52 AM To: [EMAIL PROTECTED] Subject: table crash (error127) using v4.0.15 JDBC Hi I'm working with mysql 4.0.15 for some software of ours and we are experiencing a random table crash. we have 30 MyISAM tables in our database and we're using JDBC to connect to them. Sometimes, very rarely, one of the tables crashes. It has nothing special compared to the other tables (int, varchars, datetimes and a blob), and it's one of the least accessed. We checked all the requests, they all work separately. I may add that 6 processes are accessing the base at the same time but only one of them is accessing the table that crashes, and there are always at least 5 seconds between each request on this table. for the whole base, there are 1 to 5 requests per second. It seems it's a very random bug. Never crashed buring the development, twice during the tests, then not during some time, then once during some tests at the custommers', and until now, never during the production phase, whereas there are far more requests than during the tests... I know how to repair the tables, but our software being realtime, it's a bit annoying to have to stop everything, repair and restart. Even dropping and creating the table again can lead to a further crash. Well so here is my question : i'm wondering whether the crashes could come from our version of the ConnectorJ : mysql-connector-java-2.0.14-bin.jar ?? nota bene : we couldn't use the 3.0.8 version at the moment we began coding because it had an annoying java access-rights bug (that seems corrected on the 3.0.9). Another possibility is some issue with using some toad-like mysql manager at the same time as the 6 processes...could be. If any of you has experienced a compatibility issue related to mysql 4 and connector 2, please be so kind as telling me. Thanks Fabien -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
cause of table crash
Hello I get the following errors/warnings on a table: Table is marked as crashed Not used space is supposed to be: 3688 but is: 3624 record delete-link-chain corrupted corrupt What can be the cause of this crash? Med vänlig hälsning/Best Regards Datatal Utveckling AB Jonas Gauffin Tel direct: +46 (0) 498 25 30 16 Tel Support: +46 (0) 498 25 30 30 Fax: +46 (0) 498 25 30 99 http://www.datatal.se I try every day, but sometimes I fail -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: cause of table crash
Hi, What version of MySQL are you using? Maybe it's because of a corruption bug in versions 4.0.3 - 4.0.14. Try upgrading to the latest version. Hope that helps. Matt - Original Message - From: Datatal AB - Gauffin, Jonas Sent: Monday, October 27, 2003 6:40 AM Subject: cause of table crash Hello I get the following errors/warnings on a table: Table is marked as crashed Not used space is supposed to be: 3688 but is: 3624 record delete-link-chain corrupted corrupt What can be the cause of this crash? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
table crash problem
hi listers i've upgraded my mysql env from 3.23.53 to 4.0.13. also, i changed os from m$ to rh 7.3. what did not change was h/ware. since the upgrade, i often get the error message table is marked as crashed and should be repaired. (errno 145). i then run myisamcheck --auto-repair to fix the problem but this is a reactive. what switches can i set on mysqld to trace the cause of this problem? to handle to symptom, i've set myisam_recover_option=backup,force in my.cnf this morning so hopefully the problem does not re-occur, though i'm sure sure if this will work tks _ ___ _ __ /______/ / ___/ / \ // / / / // / / ^ v / / / / /__/ / / / \/ / / /_ / /__ / /_ / /_ / Cell: 083 440 2213 Ph: 021 980 4969
Re: Table crash!
- Original Message - From: Martin Mokrejs [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, April 05, 2002 10:41 PM Subject: Table crash! Don't do this when the table is in the cache! The correct way (open two xterms and do commands in this order): mysql flush tables; mysql lock table repository write; $ myisamchk -f -d -v repository.MYI # this will tell you the status of the table based on the index file I've used myisamchk while mysql server was not running. I've shut it down first and then tryed to fix it with myisamchk. But I will try all those other options you have so kindly mentioned in your reply. THNX! Will tell you about the results. Regards, Ale Perme - 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 [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Table crash!
Description: Hi! My name is Ales Perme. A college of mine Samo Login gave me this adress, which was given to him by Monty, to report MySQL bugs to. Production configurations: 1. Windows NT 4.0, Service pack 6a, MySQL 3.23.36 2. Slackware Linux, kernel version: SMP 2.4.18, MySQL 3.23.42-log The structure of the table we are experianceing problems with is: CREATE TABLE `repository` ( `DIGEST` varchar(32) NOT NULL default '', `CONTENT` longblob NOT NULL, `CONTENT_TYPE` varchar(60) NOT NULL default '', `CONTENT_LENGTH` int(11) NOT NULL default '-1', `CONTENT_LANGUAGE` tinyblob, `LAST_MODIFIED` datetime default NULL, `LAST_ACCESSED` datetime NOT NULL default '-00-00 00:00:00', `CONTENT_TIMESTAMP` datetime NOT NULL default '-00-00 00:00:00', PRIMARY KEY (`DIGEST`), KEY `REPOSITORY_LAST_ACCESSED` (`LAST_ACCESSED`) ) TYPE=MyISAM MAX_ROWS=4 The table has mysql select count(*) from repository; +--+ | count(*) | +--+ | 5673838 | +--+ records inside. 1. I get table a table crashed whenever I try to fix it or check it with MYISAMCHK using -r, -o or -f parameters. And the table is then no longer usable. 2. BACKUP TABLE repository to ... gives a response code OK. Successfull! But when I try to restore it with RESTORE TABLE repository FROM ..., the restore fails and tryes to restore the table without quicksort. MySQL server on Windows NT 4.0, Service Pach 6a crashes with drwatson. 3. If I check the table with SQL statement CHECK TABLE repository then I get an OK! result code. What can I do? What seems to be the problem. If you need any aditional info please contact me. The table itself is 13.1 GB in size and index is 430 MB. With best regards, Ales Perme IT Manager Novifroum Ltd. Stegne 31 Ljubljana S L O V E N I A How-To-Repeat: 1. I get table a table crashed whenever I try to fix it or check it with MYISAMCHK using -r, -o or -f parameters. And the table is then no longer usable. 2. BACKUP TABLE repository to ... gives a response code OK. Successfull! But when I try to restore it with RESTORE TABLE repository FROM ..., the restore fails and tryes to restore the table without quicksort. MySQL server on Windows NT 4.0, Service Pach 6a crashes with drwatson. Fix: None available! Submitter-Id: submitter ID Originator:Ales Perme Organization: Noviforum Ltd. MySQL support: none Synopsis: Table crash! Severity: critical Priority: high Category: mysql Class: sw-bug Release: mysql-3.23.36 (Official MySQL binary) Server:3.23.36 for Windows NT Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 3.23.36-log Environment: System: Windows NT Server v4.0 , Service pack 6a Architecture: i686 - 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 [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Table crash!
The table has mysql select count(*) from repository; +--+ | count(*) | +--+ | 5673838 | +--+ records inside. 1. I get table a table crashed whenever I try to fix it or check it with MYISAMCHK using -r, -o or -f parameters. And the table is then no longer usable. Don't do this when the table is in the cache! The correct way (open two xterms and do commands in this order): mysql flush tables; mysql lock table repository write; $ myisamchk -f -d -v repository.MYI # this will tell you the status of the table based on the index file If the output says the table is broken, then myisamchk -r $table myisamchk -f -d -v $table mysql unlock tables; mysql flush tables; mysql check table $table; If it it looks fine (see the line Status), then mysql unlock tables; mysql flush tables; mysql check table $table; if the check table complains about bad number of rows present versus expect, like below: ++---+--+---+ + | Table | Op| Msg_type | Msg_text | ++---+--+---+ + | $db.$table | check | warning | Size of datafile is: 679740 Should be: 0| | $db.$table | check | error| Record-count is not ok; is 501 Should be: 0 | | $db.$table | check | warning | Found 501 partsShould be: 0 parts | | $db.$table | check | error| Corrupt | ++---+--+---+ + then do mysql flush tables; mysql lock table $table write; $ myisamchk -rq $table.MYI # fix the index while NOT modifying the .MYD file with data $ myisamchk -f -d -v $table # check the result mysql unlock tables; mysql flush tables; mysql check table $table; In any case, you should have working table. I believe this is your current problem. But you should upgrade to 3.23.49a at least as there're some bugfixes in previous versions. There're probably still some (I've reported some ;) ), so you should look for 3.23.51 to get more fixes. I've learned a lot from this thread: http://lists.mysql.com/cgi-ez/ezmlm-cgi?9:msn:11533:nkocbgofapjhfkjheipi To quote the summarized secret from that thread: - You must do FLUSH TABLES before you manipulate the .MYI or .MYD files outside of mysqld. - You can't just replace a .MYD file with another; You have to always use the .MYD and .MYI files together. (Actually, if you want to save backup space, you can go away from this restrictions by just copying the first 8K from the .MYI file; This should contain all the meta-information that myisamchk / REPAIR TABLE needs to reconstruct the rest of this file. Regards, Monty The only way to fix this is to generate a new empty .MYI file with the correct header information (Just run 'truncate table ..' on it) and then copy the old .MYD file over the empty one. Is this nice explanation of truncate table mentioned somewhere in the myisamchk section in manual? I was missing this very serious information - that I cannot re-create .MYI via myisamchk but have to use some `truncate table`, which really doesn't sound to be the command I need when repairing table. ;) [...] If you delete the .MYI table you have to generate it from the .frm file with 'truncate table'. Perfect explanation what to do in such case. I just missed this idea from you example -- me You can't just replace a compressed .MYD file with a not compressed. The .MYI and .MYD files must always be kept together. This is because all meta information (like the record type) is stored in the .MYI file. mmokrejs OK, I thought the index can be re-created safely from .MYD and .frm. mmokrejs With your explanation somewhere below that .MYI I can recreate with mmokrejs `truncate table` explains it well. And them myisamchk can fix the .MYI mmokrejs according the current status of .MYD. I thought that `truncate table` mmokrejs truncates the .MYD file, and this I didn't want to happen intentionally in mmokrejs these experiments. Yes. TRUNCATE TABLE does truncate the .MYD file. If you want to use this to generate an index the way I used it, you must first do a backup of the .MYD file and then copy it back after TRUNCATE TABLE. The only way to fix this is to generate a new empty .MYI file with the correct header information (Just run 'truncate table ..' on it)
MySQL 4.0 table crash when updating record with fulltext index
Description:
When doing the following update I get a table crash.
How-To-Repeat:
CREATE TABLE tester (
id int(11) auto_increment,
title varchar(100) default '',
PRIMARY KEY (id),
#If you comment out the following index, then the table is briefly marked as crashed
# but appears to recover although the update does not succeed
KEY ind5 (title),
#The fulltext index appears to be the root of this prob.
FULLTEXT KEY FT1 (title)
) TYPE=MyISAM;
insert into tester (title) values ('this is a test');
update tester set title='this is A test' where id=1;
check table tester;
Fix:
No known workaround. Please advise if you are aware of one. Thanks.
Submitter-Id: submitter ID
Originator:Mark Maunder
Organization:
SwiftCamel Software LTD
MySQL support: none
Synopsis: Table crash when doing update of record with fulltext index.
Severity: critical
Priority: medium
Category: mysql
Class: sw-bug
Release: mysql-4.0.0-alpha (Source distribution)
Server: /usr/bin/mysqladmin Ver 8.22 Distrib 4.0.0-alpha, for pc-linux-gnu on i686
Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license
Server version 4.0.0-alpha-log
Protocol version10
Connection Localhost via UNIX socket
UNIX socket /tmp/mysql.sock
Uptime: 8 hours 3 min 52 sec
Threads: 32 Questions: 18198 Slow queries: 295 Opens: 33 Flush tables: 1 Open
tables: 12 Queries per second avg: 0.627
Environment:
System: Linux mark.swiftcamel.com 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknown
Architecture: i686
Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-81)
Compilation info: CC='gcc' CFLAGS='' CXX='c++' CXXFLAGS='' LDFLAGS=''
LIBC:
lrwxrwxrwx1 root root 13 Jul 28 17:24 /lib/libc.so.6 - libc-2.2.2.so
-rwxr-xr-x2 root root 1236396 Apr 6 2001 /lib/libc-2.2.2.so
-rw-r--r--1 root root 26350254 Apr 6 2001 /usr/lib/libc.a
-rw-r--r--1 root root 178 Apr 6 2001 /usr/lib/libc.so
lrwxrwxrwx1 root root 10 Jul 28 17:44 /usr/lib/libc-client.a -
c-client.a
Configure command: ./configure --prefix=/usr/local/mysql4
--localstatedir=/usr/local/mysql4/data
-
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 [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Large table crash recovery
Greetings list, I have a semi large table (~10gig) that when I run a select query from the table it gives me an errno 145. So I run myisamchk on the table, as it is a myisam table. However, my problem is, when I run myisamchk it tells me that the table has about 20 million data records, then proceeds to count through them. But when it reaches 20 million it doesn't stop, and just keeps on counting up. The longest one I let run reached 26 million, before it was aborted. I have run the myisamchk with two different options the first: myisamchk --fast -r table the second: myisamchk -q -r table I received no errors from myisamchk on either as it ran through, it just doesn't stop when it reaches the number of data records it says it has. I tried running myisamchk --safe-recover and got the following message: [server /usr/local/var/my_db ]# myisamchk --safe-recover my_table - recovering (with keycache) MyISAM-table 'my_table.MYI' Data records: 19424783 myisamchk: error: Can't create new tempfile: 'my_table.TMD' MyISAM-table 'my_table' is not fixed because of errors Try fixing it by using the --safe-recover (-o) or the --force (-f) option Running it with the -f option yeilds this: [server /usr/local/var/my_db ]# myisamchk -f my_table Checking MyISAM file: my_table Data records: 19424783 Deleted blocks: 0 myisamchk: warning: Table is marked as crashed and last repair failed - check file-size myisamchk: warning: Size of indexfile is: 2917998592 Should be: 1024 - check key delete-chain - check record delete-chain - check index reference - check data record references index: 1 myisamchk: error: Can't read indexpage from filepos: -1 - recovering (with keycache) MyISAM-table 'my_table.MYI' It then starts to count through the records. Since each check takes about 14 hours I do not know if the -f option will stop at 19million or not. Can any of you guru's offer me any advice in where to take it from here? Any other myisamchk command line options that I am not aware of? It just seems to me that if the --safe-recover tells you to use --safe-recover because it didn't work, things aren't good. _Any_ advice is appreciated. - 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 [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
