On Sat, Oct 13, 2007 at 11:06:17AM +1000, Hamish Moffatt wrote: > On Fri, Oct 12, 2007 at 06:16:01PM +0100, Ralf Baechle DL5RB wrote: > > 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? > > It's happening to me all the time (with my MythTV installation). It > started when I migrated from 32-bit to dual-core 64-bit. MySQL is > running at all times but corrupts its own tables. > > On their forums, lots of people have reported similar problems in the > past which have supposedly been fixed. I have the latest version and it > still occurs. I have not had a response to my post on the forum yet.
Oh well, time for the good old UNIX glue - cronjobs ... Even though as a software developer that solution gives me the creeps ;) 73 de DL5RB op Ralf -- Loc. JN47BS / CQ 14 / ITU 28 / DOK A21 Packet: [EMAIL PROTECTED] - 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
