From owner-freebsd-questions@FreeBSD.ORG Mon Oct 30 19:11:37 2006 Return-Path: X-Original-To: freebsd-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 B9B7716A4C8 for ; Mon, 30 Oct 2006 19:11:37 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5225343D45 for ; Mon, 30 Oct 2006 19:11:37 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 30165 invoked from network); 30 Oct 2006 19:11:36 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Oct 2006 19:11:36 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 26D6128432; Mon, 30 Oct 2006 14:11:36 -0500 (EST) To: John References: <20061030185251.GL60126@reiteration.net> From: Lowell Gilbert Date: Mon, 30 Oct 2006 14:11:35 -0500 In-Reply-To: <20061030185251.GL60126@reiteration.net> (John's message of "Mon, 30 Oct 2006 18:52:51 +0000") Message-ID: <44lkmxr53s.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: fsck with freebsd-6.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 19:11:37 -0000 John writes: > Looking at the man page for fsck, I couldn't find an option to > tell fsck when it finds an unreadable sector, to mark it as bad so > it doesn't get written to another time. If fsck can't do it, is there a > program in the system or in ports that can? There are still some utilities in the system for that sort of thing, but they are pretty much historical oddities for most people; modern drives do remapping automatically, (generally) invisible to the user.