From owner-freebsd-current Tue Jan 28 4:52:11 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 2CF8437B401 for ; Tue, 28 Jan 2003 04:52:10 -0800 (PST) Received: from mgate.uni-hannover.de (mgate.uni-hannover.de [130.75.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id B03B643F85 for ; Tue, 28 Jan 2003 04:52:08 -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 12:01:35 +0100 Received: by www.pmp.uni-hannover.de (Postfix, from userid 846) id 77FA5123; Tue, 28 Jan 2003 12:01:25 +0100 (CET) Date: Tue, 28 Jan 2003 12:01:25 +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: <20030128110125.GB78630@pmp.uni-hannover.de> References: <20030127174127.GD71664@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 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. 47105 seems to be slightly different from what I saw, because my machine never paniced; the fsck just hung forever. > 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. > If anybody wants to look into this problem, I can give access to the > machine (even serial console)... 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. 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? cu Gerrit -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message