From owner-freebsd-fs@FreeBSD.ORG  Wed Feb 28 13:13:43 2007
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
X-Original-To: freebsd-fs@freebsd.org
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id D72AD16A400
	for <freebsd-fs@freebsd.org>; Wed, 28 Feb 2007 13:13:43 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 7A2EA13C461
	for <freebsd-fs@freebsd.org>; Wed, 28 Feb 2007 13:13:43 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 27CAE47208;
	Wed, 28 Feb 2007 08:13:42 -0500 (EST)
Date: Wed, 28 Feb 2007 13:13:42 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Jason Arnaute <non_secure@yahoo.com>
In-Reply-To: <660490.45660.qm@web51014.mail.yahoo.com>
Message-ID: <20070228131227.K6955@fledge.watson.org>
References: <660490.45660.qm@web51014.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-fs@freebsd.org
Subject: Re: Looking for a graceful way to disable BG fsck ?
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Feb 2007 13:13:43 -0000


On Tue, 27 Feb 2007, Jason Arnaute wrote:

> Because if I miss it, I'm screwed - you can't kill a BG fsck, and you can't 
> reboot the system while a BG fsck is going on.  So then you have to reset it 
> again, which is scary because you've got a dirty filesystem, while being 
> fsck'd, and then you dirty it up some more.

I'm not very informed on the rest of the issues here, but I can say that 
killing bgfsck is entirely possible.  Send the fsck_ufs processes TERM 
signals, and then wait a bit and they will exit.  I believe they finish 
whatever the current task they are working on is, then release the snapshot 
which can take a bit to free.

Robert N M Watson
Computer Laboratory
University of Cambridge