From owner-freebsd-questions@FreeBSD.ORG Wed Nov 10 16:28:02 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 2FE3516A4CE for ; Wed, 10 Nov 2004 16:28:02 +0000 (GMT) Received: from clunix.cl.msu.edu (clunix.cl.msu.edu [35.9.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B668C43D5D for ; Wed, 10 Nov 2004 16:28:01 +0000 (GMT) (envelope-from jerrymc@clunix.cl.msu.edu) Received: (from jerrymc@localhost) by clunix.cl.msu.edu (8.11.7p1+Sun/8.11.7) id iAAGRQE18873; Wed, 10 Nov 2004 11:27:26 -0500 (EST) From: Jerry McAllister Message-Id: <200411101627.iAAGRQE18873@clunix.cl.msu.edu> To: matt@wrongcrowd.com (Matt Staroscik) Date: Wed, 10 Nov 2004 11:27:25 -0500 (EST) In-Reply-To: <6.1.2.0.2.20041109210506.08edc590@mail.speakeasy.net> from "Matt Staroscik" at Nov 09, 2004 09:21:42 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Do you need to dismount /usr to dump it? 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: Wed, 10 Nov 2004 16:28:02 -0000 > > > If I boot to single-user mode (reboot, hit space, do boot -s) and dump /usr > to a file, I get read errors on a couple of blocks. > > Running fsck -y (also in single user of course) did not show a problem, but > it did not clear up the errors when I tried the dump again. > > I thought it was safe to dump /usr in single-user mode. Will I need to boot > off a CD or try another trick to get a clean dump of /usr? Or perhaps I am > not using the right fsck options? > > the dump command I used is: > dump 0af /someotherplace/filename.dump /usr > > This seemed to work fine for / and my other filesystems. Your problem seems to be bad blocks in the /usr file system. That has nothing to do with dump. It is a bad spot on the disk. fsck will not fix that sort of thing. If you can figure out what files sit on the bad spots, you might be able to delete them and then do your dump. Then you should immediately replace the disk. ////jerry > > Thanks! > > - matt s. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Matt Staroscik * KF6IYW * mstar@speakeasy.net * http://wrongcrowd.com > "The combined weight of the horrors I have authored wrought would crush > your carbon hearts into perfect diamonds of terror." > -- Leonid Kasparov Destroyovitch >