From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hamish Moffatt Subject: Re: linux-ax25.org website issues Date: Sat, 13 Oct 2007 11:06:17 +1000 Message-ID: <20071013010617.GA26467@cloud.net.au> References: <470F751D.9000303@w1nr.net> <20071012171601.GA10256@linux-mips.org> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20071012171601.GA10256@linux-mips.org> Sender: linux-hams-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hams@vger.kernel.org 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. Hamish -- Hamish Moffatt VK3SB