From owner-freebsd-current Tue Jan 28 10: 1:18 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 4720637B405 for ; Tue, 28 Jan 2003 10:01:15 -0800 (PST) Received: from mgate.uni-hannover.de (mgate.uni-hannover.de [130.75.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CC1943F43 for ; Tue, 28 Jan 2003 10:01:13 -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 16:55:12 +0100 Received: by www.pmp.uni-hannover.de (Postfix, from userid 846) id CB0D9123; Tue, 28 Jan 2003 16:55:01 +0100 (CET) Date: Tue, 28 Jan 2003 16:55:01 +0100 From: Gerrit =?iso-8859-1?Q?K=FChn?= To: Attila Nagy Cc: current@freebsd.org Subject: Re: Does bg fsck have problems with large filesystems? Message-ID: <20030128155501.GD78630@pmp.uni-hannover.de> References: <20030127174127.GD71664@pmp.uni-hannover.de> <20030128110125.GB78630@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 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, Jan 28, 2003 at 04:23:08PM +0100, Attila Nagy wrote: > > 47105 seems to be slightly different from what I saw, because my machine > > never paniced; the fsck just hung forever. > It depends. My machine hangs, there's no panic. Yes, I overlooked that in the PR when I read it first. Mine was still usable: I could switch VTs and even log in, but I couldn't do anything about the hanging fsck processes. > > > I've already written to Kirk McKusick, but it seems that he has a lot > > > of work, because I didn't get answer. > > Ok, then things are already on their way, I guess. > Don't know, but I hope :) That makes two of us. :) > > I wonder if it's only the large filesystem that triggers this problem. > > Actually I think that my 50GB are not /that/ large, and someone else > > should have noticed the problem before. > I wonder what's the common in our case, then. I really don't know. I have a SV25 barebone system from Shuttle (VIA Twister Chipset) and an IBM deskstar 80GB IDE HD. Does that sound familiar to you? > > BTW: As mentioned in the PR one workaround is to turn off bg fsck. On > > the other hand bg fsck is working fine on smaller filesystems. Is there > > a way to turn bg fsck off for just one partition? > I don't know any. BTW, the big partitions are those which needs the extra > time, so it is very likely that you won't benefit too much from this... Well, the drive has 80GB, the big partition is 50GB, so I would save something like 3/8 of the time. Not too much, but better than nothing, I thought. ;) cu Gerrit -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message