On 10/12/07, Ralf Baechle DL5RB <[EMAIL PROTECTED]> wrote: > On Fri, Oct 12, 2007 at 09:22:37AM -0400, Mike McCarthy, W1NR wrote: > > > There seems to be a database problem at the www.linux-ax25.org website. > > Does anyone have the contact info for the webmaster to let them know > > there is a problem? > > You might try [EMAIL PROTECTED] ;-)
That'd be too logical for a ham radio operator to figure out (tounge in cheek) > > What happened is that mysql once more shot itself into the foot: > > [EMAIL PROTECTED] wikidb_ham]# myisamchk text.MYI > Checking MyISAM file: text.MYI > Data records: 2253 Deleted blocks: 10 > myisamchk: warning: Table is marked as crashed > - check file-size > - check record delete-chain > - check key delete-chain > - check index reference > - check data record references index: 1 > myisamchk: error: Found 2252 keys of 2253 > - check record links > myisamchk: error: Keypointers and record positions doesn't match > MyISAM-table 'text.MYI' is corrupted > Fix it using switch "-r" or "-o" > [EMAIL PROTECTED] wikidb_ham]# > > MySQL marking one of its tables as crashed without crashing itself has > unfortunately become a somewhat regular event. I think it may have > started around the time when the system got migrated from a dual P3 to a > Xeon P4 running all 64-bit software so already quite a while ago. Maybe > somebody here has seen the same sort of issue? I see this fairly often on the mysql servers at work - but usually as a result of a hardware crash. We use a shell script that will run a "CHECK TABLE" command on all tables, then follow it with a script that looks at the output to find corrupt tables, and does a "REPAIR TABLE" on them. The normal operation of MySQL is to lock the table when it detects corruption - that way it can continue to serve other requests that it can complete. Jeremy, NW7JU - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
