From owner-freebsd-stable@FreeBSD.ORG Thu Jun 29 17:59:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44E6716A403 for ; Thu, 29 Jun 2006 17:59:30 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8DF443D6B for ; Thu, 29 Jun 2006 17:59:29 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 125A6B896; Thu, 29 Jun 2006 13:59:29 -0400 (EDT) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id B6C61B893; Thu, 29 Jun 2006 13:59:28 -0400 (EDT) References: <20060607222351.GA66870@math.jussieu.fr> <20060628081752.GA24060@rink.nu> <20060628092825.GB24060@rink.nu> <20060628110237.GS79678@deviant.kiev.zoral.com.ua> <20060629174428.GA1258@deviant.kiev.zoral.com.ua> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Kostik Belousov Date: Thu, 29 Jun 2006 13:59:28 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: 6.1-R ? 6-Stable ? 5.5-R ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2006 17:59:30 -0000 Kostik Belousov writes: > This seems to be a different issue. BTW, I have already heard complaints > about deadlocks caused by combination of nfsd and snapshots. I think you can add: nfsd + background fsck too. > Probably, I will look into this, but cannot give you estimations when. Thank!! > For now, you could turn off background fsck. We did.. and it was horrible.. It seems mysql was crashing the machine so we had 4 reboots in about 5 days. Since we had to give up on background fsck, that meant 2 hours every time the machine rebooted (the machine in question has 10+ million files in the volume which takes the 2 hours to fsck).