From owner-freebsd-current Fri Dec 6 10:27:15 2002 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 7C47737B401 for ; Fri, 6 Dec 2002 10:27:14 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 43CBD43E4A for ; Fri, 6 Dec 2002 10:27:10 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 15920 invoked by uid 1000); 6 Dec 2002 18:27:10 -0000 Date: Fri, 6 Dec 2002 10:27:10 -0800 (PST) From: Nate Lawson To: Kirk McKusick Cc: Archie Cobbs , freebsd-current@FreeBSD.org Subject: Re: backgroud fsck is still locking up system (fwd) In-Reply-To: <200212060101.gB611u59092060@beastie.mckusick.com> Message-ID: 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 Thu, 5 Dec 2002, Kirk McKusick wrote: > Does the background fsck process continue to run, or does the whole > system come to a halt? If the fsck process continues to run, what > happens when it eventually finishes? Is the system still dead, or > does it come back to life? If the system does not come back to life > can you get me the output of `ps axl'? If not, can you break into > the debugger and get a ps output? (You will need to have the DDB > option specified in your config file). Sorry for butting in. I think Archie is referring to bg fsck gaining an unfair share of cpu due to it running due to IO completions. Last I heard, we were waiting until after 5.0 to experiment with scheduler changes to make it more fair. I have not seen any hard locks or other problems with bg fsck after your commit. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message