Re: Persistent Corruption [UPDATE]
thanks for everyone help/suggestions -- I wound up swapping the media, and what was corrupt prior, seems to be all nice and happy now -- so - as suggested, looks to be that the drive was starting to fault On 7/31/05, Chris McKeever <[EMAIL PROTECTED]> wrote: > Thanks for all the help - I tried the dump as suggested, and it still > corrupted...waiting on the new drive to come and then I will try > replacing that .. I hope that I dont have to move to a new kernel!! > > > > On 7/29/05, Terence <[EMAIL PROTECTED]> wrote: > > Also check your kernel version. We had the same problems running on the > > old RH 7.3 kernel (2.4.17 was it?) After upgrading to RH9 it was fine. > > > > Chris McKeever wrote: > > > MySQL 4.0.16 > > > > > > I am having this annoying persistent corruption issue, and am > > > wondering if anyone has any suggestions. I have two tables that > > > refuse to stay clean. After a myisamchk (below) they show corruption. > > > I run a myisamchk -r, they get fixed, and the next day, they are once > > > again corrupt. > > > > > > Finally, I did a mysqldump, dropped the tables, imported the data from > > > the dump, and the next day - corrupt. > > > > > > I am at a loss, I thought the brute force method should clean it. > > > > > > I dont think it is the applicaiton itself, since there are an > > > identical 24 tables (alphabet) that do not have this issue. > > > > > > Any help would be appreciated - Chris > > > > > > Checking MyISAM file: EmailMessage_c.MYI > > > Data records: 79196 Deleted blocks: 22 > > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > > - check file-size > > > - check key delete-chain > > > - check record delete-chain > > > - check index reference > > > - check data record references index: 1 > > > - check record links > > > myisamchk: error: Record-count is not ok; is 79197Should be: 79196 > > > myisamchk: warning: Found 457872 deleted space. Should be 459588 > > > myisamchk: warning: Found 79507 partsShould be: > > > 79506 parts > > > MyISAM-table 'EmailMessage_c.MYI' is corrupted > > > Fix it using switch "-r" or "-o" > > > > > > > > > > > > Checking MyISAM file: EmailMessage_j.MYI > > > Data records: 39907 Deleted blocks: 91 > > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > > - check file-size > > > - check key delete-chain > > > - check record delete-chain > > > - check index reference > > > - check data record references index: 1 > > > - check record links > > > myisamchk: error: Record-count is not ok; is 39909Should be: 39907 > > > myisamchk: warning: Found 719032 deleted space. Should be 742328 > > > myisamchk: warning: Found 89 deleted blocks Should be: 91 > > > myisamchk: warning: Found 40195 partsShould be: > > > 40193 parts > > > MyISAM-table 'EmailMessage_j.MYI' is corrupted > > > Fix it using switch "-r" or "-o" > > > > > > > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > > > > > > > -- > -- > please respond to the list .. if you need to contact me direct > cgmckeever is the account > prupref.com is the domain > > http://www.prupref.com";>Simply Chicago Real Estate > -- -- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain http://www.prupref.com";>Simply Chicago Real Estate -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Persistent Corruption
Thanks for all the help - I tried the dump as suggested, and it still corrupted...waiting on the new drive to come and then I will try replacing that .. I hope that I dont have to move to a new kernel!! On 7/29/05, Terence <[EMAIL PROTECTED]> wrote: > Also check your kernel version. We had the same problems running on the > old RH 7.3 kernel (2.4.17 was it?) After upgrading to RH9 it was fine. > > Chris McKeever wrote: > > MySQL 4.0.16 > > > > I am having this annoying persistent corruption issue, and am > > wondering if anyone has any suggestions. I have two tables that > > refuse to stay clean. After a myisamchk (below) they show corruption. > > I run a myisamchk -r, they get fixed, and the next day, they are once > > again corrupt. > > > > Finally, I did a mysqldump, dropped the tables, imported the data from > > the dump, and the next day - corrupt. > > > > I am at a loss, I thought the brute force method should clean it. > > > > I dont think it is the applicaiton itself, since there are an > > identical 24 tables (alphabet) that do not have this issue. > > > > Any help would be appreciated - Chris > > > > Checking MyISAM file: EmailMessage_c.MYI > > Data records: 79196 Deleted blocks: 22 > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > - check file-size > > - check key delete-chain > > - check record delete-chain > > - check index reference > > - check data record references index: 1 > > - check record links > > myisamchk: error: Record-count is not ok; is 79197Should be: 79196 > > myisamchk: warning: Found 457872 deleted space. Should be 459588 > > myisamchk: warning: Found 79507 partsShould be: 79506 > > parts > > MyISAM-table 'EmailMessage_c.MYI' is corrupted > > Fix it using switch "-r" or "-o" > > > > > > > > Checking MyISAM file: EmailMessage_j.MYI > > Data records: 39907 Deleted blocks: 91 > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > - check file-size > > - check key delete-chain > > - check record delete-chain > > - check index reference > > - check data record references index: 1 > > - check record links > > myisamchk: error: Record-count is not ok; is 39909Should be: 39907 > > myisamchk: warning: Found 719032 deleted space. Should be 742328 > > myisamchk: warning: Found 89 deleted blocks Should be: 91 > > myisamchk: warning: Found 40195 partsShould be: 40193 > > parts > > MyISAM-table 'EmailMessage_j.MYI' is corrupted > > Fix it using switch "-r" or "-o" > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > > -- -- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain http://www.prupref.com";>Simply Chicago Real Estate -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Persistent Corruption
Also check your kernel version. We had the same problems running on the old RH 7.3 kernel (2.4.17 was it?) After upgrading to RH9 it was fine. Chris McKeever wrote: MySQL 4.0.16 I am having this annoying persistent corruption issue, and am wondering if anyone has any suggestions. I have two tables that refuse to stay clean. After a myisamchk (below) they show corruption. I run a myisamchk -r, they get fixed, and the next day, they are once again corrupt. Finally, I did a mysqldump, dropped the tables, imported the data from the dump, and the next day - corrupt. I am at a loss, I thought the brute force method should clean it. I dont think it is the applicaiton itself, since there are an identical 24 tables (alphabet) that do not have this issue. Any help would be appreciated - Chris Checking MyISAM file: EmailMessage_c.MYI Data records: 79196 Deleted blocks: 22 myisamchk: warning: 1 clients is using or hasn't closed the table properly - check file-size - check key delete-chain - check record delete-chain - check index reference - check data record references index: 1 - check record links myisamchk: error: Record-count is not ok; is 79197Should be: 79196 myisamchk: warning: Found 457872 deleted space. Should be 459588 myisamchk: warning: Found 79507 partsShould be: 79506 parts MyISAM-table 'EmailMessage_c.MYI' is corrupted Fix it using switch "-r" or "-o" Checking MyISAM file: EmailMessage_j.MYI Data records: 39907 Deleted blocks: 91 myisamchk: warning: 1 clients is using or hasn't closed the table properly - check file-size - check key delete-chain - check record delete-chain - check index reference - check data record references index: 1 - check record links myisamchk: error: Record-count is not ok; is 39909Should be: 39907 myisamchk: warning: Found 719032 deleted space. Should be 742328 myisamchk: warning: Found 89 deleted blocks Should be: 91 myisamchk: warning: Found 40195 partsShould be: 40193 parts MyISAM-table 'EmailMessage_j.MYI' is corrupted Fix it using switch "-r" or "-o" -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Persistent Corruption
Hello. > MySQL 4.0.16 You run an old MySQL. Upgrade to the latest release sometimes solves such issues. Check if the problem remains with MySQL 4.1.13 (or 4.0.25). Chris McKeever <[EMAIL PROTECTED]> wrote: > MySQL 4.0.16 > > I am having this annoying persistent corruption issue, and am > wondering if anyone has any suggestions. I have two tables that > refuse to stay clean. After a myisamchk (below) they show corruption. > I run a myisamchk -r, they get fixed, and the next day, they are once > again corrupt. > > Finally, I did a mysqldump, dropped the tables, imported the data from > the dump, and the next day - corrupt. > > I am at a loss, I thought the brute force method should clean it. > > I dont think it is the applicaiton itself, since there are an > identical 24 tables (alphabet) that do not have this issue. > > Any help would be appreciated - Chris > > Checking MyISAM file: EmailMessage_c.MYI > Data records: 79196 Deleted blocks: 22 > myisamchk: warning: 1 clients is using or hasn't closed the table properly > - check file-size > - check key delete-chain > - check record delete-chain > - check index reference > - check data record references index: 1 > - check record links > myisamchk: error: Record-count is not ok; is 79197Should be: 79196 > myisamchk: warning: Found 457872 deleted space. Should be 459588 > myisamchk: warning: Found 79507 partsShould be: 79506 = > parts > MyISAM-table 'EmailMessage_c.MYI' is corrupted > Fix it using switch "-r" or "-o" > > > =20 > Checking MyISAM file: EmailMessage_j.MYI > Data records: 39907 Deleted blocks: 91 > myisamchk: warning: 1 clients is using or hasn't closed the table properly > - check file-size > - check key delete-chain > - check record delete-chain > - check index reference > - check data record references index: 1 > - check record links > myisamchk: error: Record-count is not ok; is 39909Should be: 39907 > myisamchk: warning: Found 719032 deleted space. Should be 742328 > myisamchk: warning: Found 89 deleted blocks Should be: 91 > myisamchk: warning: Found 40195 partsShould be: 40193 = > parts > MyISAM-table 'EmailMessage_j.MYI' is corrupted > Fix it using switch "-r" or "-o" > > > --=20 > -- > please respond to the list .. if you need to contact me direct > cgmckeever is the account > prupref.com is the domain > > http://www.prupref.com";>Simply Chicago Real Estate > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Persistent Corruption
On 7/28/05, Dan Tappin <[EMAIL PROTECTED]> wrote: > I was running into this all the time. > > I actually had myisamchk running on a regular basis (live) via cron > which I think was actually causing the corruption. > > By chance are you running myisamchk on the live tables?? I was - but not after all this crap started, but I still get those errors even after a rebuild I ran the > REPAIR TABLE... on each table, shut down mysql THEN ran myisamchk > again and my 127 errors seem o be gone (so far). > I think I am going to put in a new harddrive and hope for tbe best > What OS are you running BTW? > RedHat 7.3 > Dan T > > On Jul 28, 2005, at 8:45 AM, Chris McKeever wrote: > > > MySQL 4.0.16 > > > > I am having this annoying persistent corruption issue, and am > > wondering if anyone has any suggestions. I have two tables that > > refuse to stay clean. After a myisamchk (below) they show corruption. > > I run a myisamchk -r, they get fixed, and the next day, they are once > > again corrupt. > > > > Finally, I did a mysqldump, dropped the tables, imported the data from > > the dump, and the next day - corrupt. > > > > I am at a loss, I thought the brute force method should clean it. > > > > I dont think it is the applicaiton itself, since there are an > > identical 24 tables (alphabet) that do not have this issue. > > > > Any help would be appreciated - Chris > > > > Checking MyISAM file: EmailMessage_c.MYI > > Data records: 79196 Deleted blocks: 22 > > myisamchk: warning: 1 clients is using or hasn't closed the table > > properly > > - check file-size > > - check key delete-chain > > - check record delete-chain > > - check index reference > > - check data record references index: 1 > > - check record links > > myisamchk: error: Record-count is not ok; is 79197Should > > be: 79196 > > myisamchk: warning: Found 457872 deleted space. Should be 459588 > > myisamchk: warning: Found 79507 partsShould > > be: 79506 parts > > MyISAM-table 'EmailMessage_c.MYI' is corrupted > > Fix it using switch "-r" or "-o" > > > > > > > > Checking MyISAM file: EmailMessage_j.MYI > > Data records: 39907 Deleted blocks: 91 > > myisamchk: warning: 1 clients is using or hasn't closed the table > > properly > > - check file-size > > - check key delete-chain > > - check record delete-chain > > - check index reference > > - check data record references index: 1 > > - check record links > > myisamchk: error: Record-count is not ok; is 39909Should > > be: 39907 > > myisamchk: warning: Found 719032 deleted space. Should be 742328 > > myisamchk: warning: Found 89 deleted blocks Should > > be: 91 > > myisamchk: warning: Found 40195 partsShould > > be: 40193 parts > > MyISAM-table 'EmailMessage_j.MYI' is corrupted > > Fix it using switch "-r" or "-o" > > > > > > -- > > -- > > please respond to the list .. if you need to contact me direct > > cgmckeever is the account > > prupref.com is the domain > > > > http://www.prupref.com";>Simply Chicago Real Estate > > > > -- > > 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] > > -- -- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain http://www.prupref.com";>Simply Chicago Real Estate -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Persistent Corruption
I was running into this all the time. I actually had myisamchk running on a regular basis (live) via cron which I think was actually causing the corruption. By chance are you running myisamchk on the live tables?? I ran the REPAIR TABLE... on each table, shut down mysql THEN ran myisamchk again and my 127 errors seem o be gone (so far). What OS are you running BTW? Dan T On Jul 28, 2005, at 8:45 AM, Chris McKeever wrote: MySQL 4.0.16 I am having this annoying persistent corruption issue, and am wondering if anyone has any suggestions. I have two tables that refuse to stay clean. After a myisamchk (below) they show corruption. I run a myisamchk -r, they get fixed, and the next day, they are once again corrupt. Finally, I did a mysqldump, dropped the tables, imported the data from the dump, and the next day - corrupt. I am at a loss, I thought the brute force method should clean it. I dont think it is the applicaiton itself, since there are an identical 24 tables (alphabet) that do not have this issue. Any help would be appreciated - Chris Checking MyISAM file: EmailMessage_c.MYI Data records: 79196 Deleted blocks: 22 myisamchk: warning: 1 clients is using or hasn't closed the table properly - check file-size - check key delete-chain - check record delete-chain - check index reference - check data record references index: 1 - check record links myisamchk: error: Record-count is not ok; is 79197Should be: 79196 myisamchk: warning: Found 457872 deleted space. Should be 459588 myisamchk: warning: Found 79507 partsShould be: 79506 parts MyISAM-table 'EmailMessage_c.MYI' is corrupted Fix it using switch "-r" or "-o" Checking MyISAM file: EmailMessage_j.MYI Data records: 39907 Deleted blocks: 91 myisamchk: warning: 1 clients is using or hasn't closed the table properly - check file-size - check key delete-chain - check record delete-chain - check index reference - check data record references index: 1 - check record links myisamchk: error: Record-count is not ok; is 39909Should be: 39907 myisamchk: warning: Found 719032 deleted space. Should be 742328 myisamchk: warning: Found 89 deleted blocks Should be: 91 myisamchk: warning: Found 40195 partsShould be: 40193 parts MyISAM-table 'EmailMessage_j.MYI' is corrupted Fix it using switch "-r" or "-o" -- -- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain http://www.prupref.com";>Simply Chicago Real Estate -- 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]
Re: Persistent Corruption
On 7/28/05, Dobromir Velev <[EMAIL PROTECTED]> wrote: > Hi, > Isn't there some information in the MySQL error log about what might have > caused the corruption. Normally this would happen when disk or memory problem > occurs. > thanks for the reply - from the .err file: 050722 5:20:24 read_next: Got error 127 when reading table ./atmail/EmailDatabase_c 050722 5:23:28 read_next: Got error 127 when reading table ./atmail/EmailDatabase_c 050722 5:23:29 read_next: Got error 127 when reading table ./atmail/EmailDatabase_c however, that was days ago, and since i ran the repairs, as well as the dump -> reinsert > > On Thursday 28 July 2005 17:45, Chris McKeever wrote: > > MySQL 4.0.16 > > > > I am having this annoying persistent corruption issue, and am > > wondering if anyone has any suggestions. I have two tables that > > refuse to stay clean. After a myisamchk (below) they show corruption. > > I run a myisamchk -r, they get fixed, and the next day, they are once > > again corrupt. > > > > Finally, I did a mysqldump, dropped the tables, imported the data from > > the dump, and the next day - corrupt. > > > > I am at a loss, I thought the brute force method should clean it. > > > > I dont think it is the applicaiton itself, since there are an > > identical 24 tables (alphabet) that do not have this issue. > > > > Any help would be appreciated - Chris > > > > Checking MyISAM file: EmailMessage_c.MYI > > Data records: 79196 Deleted blocks: 22 > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > - check file-size > > - check key delete-chain > > - check record delete-chain > > - check index reference > > - check data record references index: 1 > > - check record links > > myisamchk: error: Record-count is not ok; is 79197Should be: 79196 > > myisamchk: warning: Found 457872 deleted space. Should be 459588 > > myisamchk: warning: Found 79507 partsShould be: 79506 > > parts MyISAM-table 'EmailMessage_c.MYI' is corrupted > > Fix it using switch "-r" or "-o" > > > > > > > > Checking MyISAM file: EmailMessage_j.MYI > > Data records: 39907 Deleted blocks: 91 > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > - check file-size > > - check key delete-chain > > - check record delete-chain > > - check index reference > > - check data record references index: 1 > > - check record links > > myisamchk: error: Record-count is not ok; is 39909Should be: 39907 > > myisamchk: warning: Found 719032 deleted space. Should be 742328 > > myisamchk: warning: Found 89 deleted blocks Should be: 91 > > myisamchk: warning: Found 40195 partsShould be: 40193 > > parts MyISAM-table 'EmailMessage_j.MYI' is corrupted > > Fix it using switch "-r" or "-o" > > > > > > -- > > -- > > please respond to the list .. if you need to contact me direct > > cgmckeever is the account > > prupref.com is the domain > > > > http://www.prupref.com";>Simply Chicago Real Estate > > -- > Dobromir Velev > [EMAIL PROTECTED] > http://www.websitepulse.com/ > -- -- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain http://www.prupref.com";>Simply Chicago Real Estate -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Persistent Corruption
Hi, Isn't there some information in the MySQL error log about what might have caused the corruption. Normally this would happen when disk or memory problem occurs. On Thursday 28 July 2005 17:45, Chris McKeever wrote: > MySQL 4.0.16 > > I am having this annoying persistent corruption issue, and am > wondering if anyone has any suggestions. I have two tables that > refuse to stay clean. After a myisamchk (below) they show corruption. > I run a myisamchk -r, they get fixed, and the next day, they are once > again corrupt. > > Finally, I did a mysqldump, dropped the tables, imported the data from > the dump, and the next day - corrupt. > > I am at a loss, I thought the brute force method should clean it. > > I dont think it is the applicaiton itself, since there are an > identical 24 tables (alphabet) that do not have this issue. > > Any help would be appreciated - Chris > > Checking MyISAM file: EmailMessage_c.MYI > Data records: 79196 Deleted blocks: 22 > myisamchk: warning: 1 clients is using or hasn't closed the table properly > - check file-size > - check key delete-chain > - check record delete-chain > - check index reference > - check data record references index: 1 > - check record links > myisamchk: error: Record-count is not ok; is 79197Should be: 79196 > myisamchk: warning: Found 457872 deleted space. Should be 459588 > myisamchk: warning: Found 79507 partsShould be: 79506 > parts MyISAM-table 'EmailMessage_c.MYI' is corrupted > Fix it using switch "-r" or "-o" > > > > Checking MyISAM file: EmailMessage_j.MYI > Data records: 39907 Deleted blocks: 91 > myisamchk: warning: 1 clients is using or hasn't closed the table properly > - check file-size > - check key delete-chain > - check record delete-chain > - check index reference > - check data record references index: 1 > - check record links > myisamchk: error: Record-count is not ok; is 39909Should be: 39907 > myisamchk: warning: Found 719032 deleted space. Should be 742328 > myisamchk: warning: Found 89 deleted blocks Should be: 91 > myisamchk: warning: Found 40195 partsShould be: 40193 > parts MyISAM-table 'EmailMessage_j.MYI' is corrupted > Fix it using switch "-r" or "-o" > > > -- > -- > please respond to the list .. if you need to contact me direct > cgmckeever is the account > prupref.com is the domain > > http://www.prupref.com";>Simply Chicago Real Estate -- Dobromir Velev [EMAIL PROTECTED] http://www.websitepulse.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
