From owner-freebsd-current Tue Jan 28 9:22:27 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 DC59D37B405 for ; Tue, 28 Jan 2003 09:22:25 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2C9F43F43 for ; Tue, 28 Jan 2003 09:22:24 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) by alpha.siliconlandmark.com (8.12.6/8.12.6) with ESMTP id h0SHMFPT019319; Tue, 28 Jan 2003 12:22:15 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost) by alpha.siliconlandmark.com (8.12.6/8.12.6/Submit) with ESMTP id h0SHMAU9019316; Tue, 28 Jan 2003 12:22:10 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 28 Jan 2003 12:22:10 -0500 (EST) From: Andre Guibert de Bruet To: Vallo Kallaste Cc: Attila Nagy , =?iso-8859-1?Q?Gerrit_K=C3=BChn?= , current@FreeBSD.ORG Subject: Re: Does bg fsck have problems with large filesystems? In-Reply-To: <20030128125432.GB4813@tiiu.internal> Message-ID: <20030128110546.L66869@alpha.siliconlandmark.com> References: <20030127174127.GD71664@pmp.uni-hannover.de> <20030128125432.GB4813@tiiu.internal> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 28 Jan 2003, Vallo Kallaste wrote: > On Tue, Jan 28, 2003 at 11:44:03AM +0100, Attila Nagy wrote: > > > > I've just installed my first 5.0-rel system and did some > > > "torture-testing". When resetting the machine to test the backgrounded > > > fsck I experienced the following problem: All filesystems came back > > > quickly and bg fsck worked fine, except for one. I had created a large > > > (>50GB) /export filesystem on with fsck reproducively hang. > > See PR kern/47105. > > Although it speaks of much larger filesystems, than your, the problem is > > there. > > > > I've already written to Kirk McKusick, but it seems that he has a lot of > > work, because I didn't get answer. > > I don't see it listed in 5.0-RELEASE ERRATA. Several people have now > reported problems with background fsck and in the case Kirk as > original author is loaded with other work I see no justification to > not mention the brokenness of bgfsck. I've been trying to reproduce this bug on my desktop. This machine has 2 80gb disks, one of which is dedicated with one slice. So far, after 8 hard resets, I haven't had any problem with either the machine or bgfsck hanging. Here's what df's output looks like: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 128990 83408 35264 70% / devfs 1 1 0 100% /dev /dev/ad0s1f 257998 404 236956 0% /tmp /dev/ad0s1g 74757832 5774972 63002234 8% /usr /dev/ad0s1e 257998 21122 216238 9% /var procfs 4 4 0 100% /proc /dev/ad1s1e 76955976 49105248 21694250 69% /export Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message