From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 10 10:31:31 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C308106573D; Wed, 10 Jun 2009 10:31:31 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id B7DE58FC13; Wed, 10 Jun 2009 10:31:30 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.3/8.14.3) with ESMTP id n5AAVSqQ006442; Wed, 10 Jun 2009 14:31:28 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Wed, 10 Jun 2009 14:31:28 +0400 (MSD) From: Dmitry Morozovsky To: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: <86hbyowgj6.fsf@ds4.des.no> 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) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (woozle.rinet.ru [0.0.0.0]); Wed, 10 Jun 2009 14:31:29 +0400 (MSD) Cc: snb@freebsd.org, freebsd-current@freebsd.org, dan.naumov@gmail.com, sthaug@nethelp.no, freebsd-hackers@freebsd.org Subject: Re: sysinstall, GJOURNAL and ZFS X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2009 10:31:33 -0000 On Wed, 10 Jun 2009, Dag-Erling Sm?rgrav wrote: DS> sthaug@nethelp.no writes: DS> > I've had several cases that needed manual fsck. After I turned off DS> > background fsck, the problems stopped. These days background_fsck="NO" DS> > is a standard part of my rc.conf. DS> DS> Hear, hear. Well, I can see at least one rather big problem with bgfsck (or with snapshots 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. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------