From owner-freebsd-questions@FreeBSD.ORG Thu Aug 17 17:09:26 2006 Return-Path: X-Original-To: questions@FreeBSD.org 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 403D316A4DF for ; Thu, 17 Aug 2006 17:09:26 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6023D43DDE for ; Thu, 17 Aug 2006 17:08:49 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout13/MantshX 4.0) with ESMTP id k7HH8h7N011781; Thu, 17 Aug 2006 10:08:43 -0700 (PDT) Received: from [17.214.14.142] (a17-214-14-142.apple.com [17.214.14.142]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id k7HH8cic028468; Thu, 17 Aug 2006 10:08:42 -0700 (PDT) In-Reply-To: <20060817165508.GH89500@submonkey.net> References: <20060817165508.GH89500@submonkey.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Thu, 17 Aug 2006 10:08:37 -0700 To: Ceri Davies X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAQAAA+k= X-Language-Identified: TRUE Cc: questions@FreeBSD.org Subject: Re: Wilfully dirtying a filesystem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Aug 2006 17:09:26 -0000 On Aug 17, 2006, at 9:55 AM, Ceri Davies wrote: > I cannot easily get to single-user on this machine, so is there a good > way for me to dirty the filesystem just enough to force "fsck -p" to > fail (yanking power also difficult)? "umount -f /usr; reboot" doesn't > seem to work... Edit a file on /usr and leave the editor session going to make sure you've got an open file on that filesystem, then do a "reboot -nq" instead... -- -Chuck