From owner-freebsd-current  Tue Jan 28 10: 1:20 2003
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id ECD0D37B407; Tue, 28 Jan 2003 10:01:16 -0800 (PST)
Received: from mgate.uni-hannover.de (mgate.uni-hannover.de [130.75.2.3])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7CA5543F43; Tue, 28 Jan 2003 10:01:15 -0800 (PST)
	(envelope-from gerrit@pmp.uni-hannover.de)
Received: from www.pmp.uni-hannover.de by mgate.uni-hannover.de
          with LocalSMTP (PP) with ESMTP; Tue, 28 Jan 2003 18:52:07 +0100
Received: by www.pmp.uni-hannover.de (Postfix, from userid 846)
	id AF697123; Tue, 28 Jan 2003 18:51:57 +0100 (CET)
Date: Tue, 28 Jan 2003 18:51:57 +0100
From: Gerrit =?iso-8859-1?Q?K=FChn?= <gerrit@pmp.uni-hannover.de>
To: Robert Watson <rwatson@FreeBSD.ORG>
Cc: Andre Guibert de Bruet <andy@siliconlandmark.com>,
	Vallo Kallaste <kalts@estpak.ee>, Attila Nagy <bra@fsn.hu>,
	current@FreeBSD.ORG
Subject: Re: Does bg fsck have problems with large filesystems?
Message-ID: <20030128175157.GG78630@pmp.uni-hannover.de>
References: <20030128110546.L66869@alpha.siliconlandmark.com> <Pine.NEB.3.96L.1030128123140.87213H-100000@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.NEB.3.96L.1030128123140.87213H-100000@fledge.watson.org>
User-Agent: Mutt/1.4i
X-Operating-System: FreeBSD
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Tue, Jan 28, 2003 at 12:34:25PM -0500, Robert Watson wrote:


> Following reports of problems with bgfsck during the 5.0-RC series, and
> prior to the release, I spent some time adding hard disks to machines,
> resetting without clean shutdowns, and then interrupting background fscks,
> piles of builds going, etc. When I started, it was fairly problematic, but
> after Kirk's last batch of buffer fixes, etc, it was pretty much 100%
> reliable on the boxes I was testing on.  

Have these fixes been applied to 5.0-rel, too? If not, I'm considering
updating to -current.


cu
  Gerrit
-- 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message