From owner-freebsd-questions@FreeBSD.ORG Mon Oct 30 19:09:49 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 6B70216A536 for ; Mon, 30 Oct 2006 19:09:49 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EA2C43F52 for ; Mon, 30 Oct 2006 19:04:01 +0000 (GMT) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id k9UJ3NiS012877; Mon, 30 Oct 2006 14:03:23 -0500 (EST) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id k9UJ3NvQ012876; Mon, 30 Oct 2006 14:03:23 -0500 (EST) (envelope-from jerrymc) Date: Mon, 30 Oct 2006 14:03:23 -0500 From: Jerry McAllister To: John Message-ID: <20061030190323.GA12835@gizmo.acns.msu.edu> References: <20061030185251.GL60126@reiteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061030185251.GL60126@reiteration.net> User-Agent: Mutt/1.4.2.2i 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 List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 19:09:49 -0000 > Hello list > > 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? That generally gets handled nowdays by the disk controller. It remaps blocks to reserved spare blocks. When you begin to see bad blocks mentioned by the OS, it generally means that the disk has run out of its spare blocks and is beginning to die and it is time to replace it - not just mark a block as bad. I don't think fsck deals with things at that level. It is more interested in making sure the structure of the file system is intact and that is a higher level than bad blocks. So, I could be wrong on that part, but I don't think fsck has a option for marking bad blocks. I don't know about a utililty to do it. ////jerry > > cheers > -- > John - lists@reiteration.net > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"