From owner-freebsd-questions@FreeBSD.ORG Fri Feb 25 14:00:16 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94B5816A4CE for ; Fri, 25 Feb 2005 14:00:16 +0000 (GMT) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BCC643D1F for ; Fri, 25 Feb 2005 14:00:15 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 31835 invoked from network); 25 Feb 2005 14:00:14 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 25 Feb 2005 14:00:14 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 9B2AF82; Fri, 25 Feb 2005 09:00:12 -0500 (EST) Sender: lowell@be-well.ilk.org To: "T.F. Cheng" , FreeBSD , Piter References: <20050225032032.GE60363@dan.emsphone.com> <20050225032917.26920.qmail@web51010.mail.yahoo.com> <20050225135021.GB18789@alzatex.com> From: Lowell Gilbert Date: 25 Feb 2005 09:00:12 -0500 In-Reply-To: <20050225135021.GB18789@alzatex.com> Message-ID: <44mztsvixf.fsf@be-well.ilk.org> Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Directory not empty X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 14:00:16 -0000 "Loren M. Lang" writes: > On Fri, Feb 25, 2005 at 11:29:17AM +0800, T.F. Cheng wrote: > > man, you are right, I now recall there was a crash > > during the last portupgrade. And there is " > > /dev/ad0s1f: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN > > fsck MANUALLY." in my /var/log. > > Guess the mystery is solved. > > Then why do I have to reboot first then run bgfsck? > > Can I run this myself without rebooting? > > kill -TERM 1 will send your system into single user mode without > rebooting. Assuming you haven't done system like increase the > securelevel, you should be able to fsck the drive from here. The disk will still be mounted read-write. It would be good to umount(8) it before using fsck(8) on it. Then, mounting it again before returning to multi-user mode will be necessary.