From owner-freebsd-current Sat Feb 26 10: 5:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id A5AA437BB7F for ; Sat, 26 Feb 2000 10:05:38 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from gateway.posi.net (root@alc-180.alcnet.com [63.69.28.180]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id NAA80717; Sat, 26 Feb 2000 13:05:27 -0500 (EST) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id NAA43831; Sat, 26 Feb 2000 13:07:05 -0500 (EST) (envelope-from kbyanc@posi.net) Date: Sat, 26 Feb 2000 13:07:03 -0500 (EST) From: Kelly Yancey To: kibbet Cc: freebsd-current@FreeBSD.ORG Subject: Re: bad blocks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Feb 2000, kibbet wrote: > Hi all, > > Quick question, how does the new ata driver handle bad blocks? > I've been tracking -current since around Nov 99 but haven't > seen this come up. As I recall, it doesn't. The reasoning is that modern IDE drives perform bad block reassignment so if you are seeing bad block errors, then the entire reserve of blocks available for reassignment has been exhausted. In which case, things are Very Bad and you should start backing up your data ASAP. In you scenario of upgrading from the old wd driver in -stable to the new ad driver in -current, the only advisable action is to just not do a bad block scan under -stable before upgrading. The should stop the complaints from the ad driver about the old-style bad block table. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message