From owner-freebsd-questions@FreeBSD.ORG Thu Sep 23 11:49:21 2004 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 2EEF516A4CE for ; Thu, 23 Sep 2004 11:49:21 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2EA643D1D for ; Thu, 23 Sep 2004 11:49:20 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 194E969A71; Thu, 23 Sep 2004 07:49:20 -0400 (EDT) Date: Thu, 23 Sep 2004 07:49:18 -0400 From: Bill Moran To: Gabriel Ambuehl Message-Id: <20040923074918.7efbcabf.wmoran@potentialtech.com> In-Reply-To: <392342192.20040923104959@buz.ch> References: <392342192.20040923104959@buz.ch> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: questions@freebsd.org cc: gaml@buz.ch Subject: Re: fsck'ing dirty unmounted file system in multi user? 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 Sep 2004 11:49:21 -0000 Gabriel Ambuehl wrote: > Hi, > after a crash of a server (running 4.10) we wanted to bring it > up ASAP and skipped fsck'ing some backup partitions as they weren't > essential for it to work. However, I'd now like to fsck them while the > machine is in multi user but I always end up with. > fsck -fp /dev/ar0s1g > /dev/ar0s1g: NO WRITE ACCESS > /dev/ar0s1g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > > Do I really have to take the machine to single user just to fix a not > currently used FS? You can't/shouldn't fsck them if they're mounted. Make sure they're not mounted first. Additionally, if your securelevel is high, you can't fsck them no matter what, as the securelevel will prevent direct access to raw devices. You'll have to temporarily lower the securelevel in order to fsck them. -- Bill Moran Potential Technologies http://www.potentialtech.com