From owner-freebsd-questions@FreeBSD.ORG Thu Oct 23 02:11:18 2003 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 A0E4616A4B3 for ; Thu, 23 Oct 2003 02:11:18 -0700 (PDT) Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AFBC43FAF for ; Thu, 23 Oct 2003 02:11:17 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta02-svc.ntlworld.comESMTP <20031023091116.SZJ8170.mta02-svc.ntlworld.com@llama.fishballoon.org>; Thu, 23 Oct 2003 10:11:16 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 1ACbUC-000FCO-1P; Thu, 23 Oct 2003 10:10:28 +0100 Date: Thu, 23 Oct 2003 10:10:28 +0100 From: Scott Mitchell To: freebsd@ryansandridge.com Message-ID: <20031023091027.GC57527@llama.fishballoon.org> References: <20031022200054.30862.qmail@web41412.mail.yahoo.com> <7381BDDB-04D6-11D8-AAFC-003065BBC750@ryansandridge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE-p13 i386 Sender: Scott Mitchell cc: freebsd-questions@freebsd.org Subject: Re: strange dump (dark matter?) 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: Thu, 23 Oct 2003 09:11:18 -0000 On Wed, Oct 22, 2003 at 10:01:51PM -0400, Ryan Sandridge wrote: > Well, as a newbie, it only took me about 10 hours to figure out on my > own that I needed to run fsck. It showed me that I had an unreferenced > file hiding on my disk; however fsck never seemed to work as > documented. I couldn't ever run it with 'fsck -p', I always received > (and still do receive): > > /dev/ad0s1g: NO WRITE ACCESS > /dev/ad0s1g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > and when I ran it with just 'fsck', it would always answer "no" to the > prompts to fix the problems without giving me an opportunity to fix it. > No I didn't use the -n flag to force no responses, and I am aware of > the -y flag, but the documentation warns against doing this. Finally I > threw my hands up, and rebooted, which seemed to clear up the > unreferenced file. You should only be running fsck on unmounted filesystems, or those mounted read-only. Looks like you tried to fsck a mounted filesystem? Cheers, Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon