From owner-freebsd-questions@FreeBSD.ORG Mon Dec 12 19:48:57 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D75DF16A45A for ; Mon, 12 Dec 2005 19:48:56 +0000 (GMT) (envelope-from danstemporaryaccount@yahoo.ca) Received: from kenyan.nodes.net.ad-flow.com (KENYAN.NODES.NET.AD-FLOW.COM [66.117.33.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93ECA43D64 for ; Mon, 12 Dec 2005 19:48:50 +0000 (GMT) (envelope-from danstemporaryaccount@yahoo.ca) Received: from [66.38.196.186] (helo=dquinn.cubearmy.com) by kenyan.nodes.net.ad-flow.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50) id 1EltfD-0008fP-43 for freebsd-questions@freebsd.org; Mon, 12 Dec 2005 19:48:47 +0000 From: daniel To: freebsd-questions@freebsd.org Date: Mon, 12 Dec 2005 14:48:45 -0500 User-Agent: KMail/1.9 References: <200512081051.38306.danstemporaryaccount@yahoo.ca> <70e8236f0512081529p71063331ua3b6297fbd007c3d@mail.gmail.com> In-Reply-To: <70e8236f0512081529p71063331ua3b6297fbd007c3d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512121448.45716.danstemporaryaccount@yahoo.ca> Subject: Re: MySQL "forgot" some of my data! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 19:48:57 -0000 On Thursday 08 December 2005 18:29, Joao Barros wrote: > On 12/8/05, daniel wrote: > > Our company has a few very large databases (>9gb) which required a shut > > down, > > > > mysql> SELECT * FROM campaigns LIMIT 0; > > ERROR 1017 at line 1: Can't find file: 'campaigns.MYI' (errno: 2) > > Was that using MyISAM or InnoDB ? Both tables lost were MyISAM, but ther were also a number of other MyISAM tables that remained seemingly untouched. > > So my questions to you, deal list are: > > > > 1. Should mysqladmin shutdown take this long? > > a. Is this normal even with a load of 0.00? > > I'd say no.... on a Power5 with 8ish cpus and a load of 15 on a 34GB > database I could stop it almost instantly using normal shutdown > procedure. Good to know, but what then is the best idea when a shutdown _is_ taking so long? > > 2. Is this the best way to shut down a database of this size? > > Is there a different way per size? Guess not ;) > > > 3. What is most likely to be the cause of the data loss? > > Were you using MyISAM of InnoDB? I had this issue after a restart with > the only table using MyISAM. My chief concern is that this should never happen again and at this stage I'm still not sure how to prevent it. Are you saying InnoDB is a more stable format and recommending that we should switch everything to this format? Right now we're using MySQL 4.0.x but we're in the process of migrating to 4.1 for the next version of the project. Would 5.0 be a better choice considering that this is a near rewrite? Thanks for all the advice and sorry for the late reply. Christmas time has been a stressful one for me ;-) -- we do not see things as they are. we see them as we are - anais nin