From owner-freebsd-current@FreeBSD.ORG Wed Jun 10 11:47:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCAB31065694; Wed, 10 Jun 2009 11:47:05 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id DD8BD8FC21; Wed, 10 Jun 2009 11:47:04 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n5ABl0p5016350; Wed, 10 Jun 2009 13:47:00 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n5ABkxul016347; Wed, 10 Jun 2009 13:46:59 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Wed, 10 Jun 2009 13:46:59 +0200 (CEST) From: Wojciech Puchar To: Dmitry Morozovsky In-Reply-To: Message-ID: References: <20090609172142.GA92146@ebi.local> <20090609.195750.41709103.sthaug@nethelp.no> <86hbyowgj6.fsf@ds4.des.no> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Wed, 10 Jun 2009 11:57:15 +0000 Cc: freebsd-hackers@freebsd.org, dan.naumov@gmail.com, freebsd-current@freebsd.org, sthaug@nethelp.no, snb@freebsd.org, =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: sysinstall, GJOURNAL and ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2009 11:47:06 -0000 > to be more precise): inappropriate time of file system lock on snapshot > creation. On not-too-big 300G ufs2 not-too-heavy loaded snapshot creation time > is 20+ minutes, and 5+ from that file system blocked even on reads. This looks > unacceptable for me for any real use. that's why i disable it. If you sum up time of total blocked and time of almost-blocked you will end with much more than fsck normally use with foreground check.