Hello, Sorry if this has been covered, but I've searched the archives with no results.
I have 2 identical servers running mysql 3.23.54a on RedHat linux 7.2 (custom kernel 2.4.17). One is running as master, one slave using mysql internal replication. The primary server has a database where one or more tables get corrupted almost daily. I don't think it's an extremely busy server, although it reports an average of ~17 queries per second, 70% of those being selects, the rest being inserts, and very few updates and deletes. One occassion it reported error 127 (corrupted table), other times it just reports that the index is off and needs repaired. The slave server seems to get corruption also, but it always seems to differ from master server's corruption (both row position and number of errors). Should the slave have the master errors or be error free in this case? REPAIR TABLE has always worked, but I'm afraid that it won't someday. There is no signs of harddrive failure (software raid1) but my best guess at this point is hardware. What should I look at replacing first? Or is there a better way to debug this? The master server needs 24/7 access, so I'd rather not try anything that would cause too much downtime. Any pointers and/or suggestions are appriciated. TIA, Dale __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.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 <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
