From owner-freebsd-fs@FreeBSD.ORG Wed Jan 3 16:37:38 2007 Return-Path: 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 597D216A412 for ; Wed, 3 Jan 2007 16:37:38 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: from web58613.mail.re3.yahoo.com (web58613.mail.re3.yahoo.com [68.142.236.211]) by mx1.freebsd.org (Postfix) with SMTP id 0A49A13C44B for ; Wed, 3 Jan 2007 16:37:37 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: (qmail 9551 invoked by uid 60001); 3 Jan 2007 16:10:57 -0000 Message-ID: <20070103161057.9549.qmail@web58613.mail.re3.yahoo.com> DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=uE4WZ05xNPPKhKPVZzxvktIupNHV4DQ9YEZo7WBiRRuNGBs8jkci4tUTZqxQUwGj0ibrT6pBVfFLYcgSOEX4RFLrkClQJubmdQe1y5E7T2LBRozXt+rMkXP4Txw7NsCow7ikcDgznaIU8r6+fhRjvkw4jqYc0kQzt2ji8xeScLI=; X-YMail-OSG: fxQNiEEVM1mBwe2sgM9pWgabC6J2vm9kmblilAPTgryi3sJ2SMLY3kDoMi5nfMooPoeIB2eT9la7c_.7JWxX7dyJrTEkpBITiBIZViL64PiZqHR.ZuPTjDtgPJ67C2snvlMkfW2SePLvE_sjnvPB577C0sD5T3rurNI- Received: from [12.165.108.28] by web58613.mail.re3.yahoo.com via HTTP; Wed, 03 Jan 2007 08:10:57 PST Date: Wed, 3 Jan 2007 08:10:57 -0800 (PST) From: Arone Silimantia To: freebsd-fs@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 03 Jan 2007 17:16:34 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: breaking out of a background fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 16:37:38 -0000 6.1-RELEASE system crashed. System was rebooted before I could get to it, and the background fsck processes started off. So, while they were running, I logged in and issued the 'reboot' command. This command has not completed, and I cannot ctrl-C it. The system is still up and responsive - I can log into it. I have all the time in the world, and uptime is not a problem, so what I want to do is reboot the system with the filesystems commented out in /etc/fstab and just manually fsck them by hand. But now what do I do with this system ? Will it finally reboot when the background fsck is done ? Or are they in a deadlock now (I notice that fsck_ufs, in top, never seems to leave the state SNAPLK). From past experience, I am fairly certain that any attempt to kill the fsck processes will fail. The kill command will return with no errors, but the processes will still be there.... Any ideas ? And in the future, what is the right way to break out of an unintended background fsck ? thanks. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com