From owner-freebsd-questions Sun Mar 11 8:54:10 2001 Delivered-To: freebsd-questions@freebsd.org Received: from relay.ioffe.rssi.ru (relay.ioffe.rssi.ru [194.85.224.33]) by hub.freebsd.org (Postfix) with ESMTP id CB9E837B718; Sun, 11 Mar 2001 08:54:02 -0800 (PST) (envelope-from kopts@astro.ioffe.rssi.ru) Received: from astro.ioffe.rssi.ru (astro.ioffe.rssi.ru [194.85.229.130]) by relay.ioffe.rssi.ru (8.9.1/8.9.1) with ESMTP id TAA02570; Sun, 11 Mar 2001 19:53:54 +0300 (MSK) Received: by astro.ioffe.rssi.ru (8.9.3/Clnt-2.14-AS-eef) id TAA13194; Sun, 11 Mar 2001 19:53:49 +0300 (MSK) Date: Sun, 11 Mar 2001 19:53:49 +0300 (MSK) From: Alexey Koptsevich To: Poul-Henning Kamp Cc: questions@freebsd.org Subject: bad144 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Poul-Henning, May I ask what was the reason for removing bad144 from 4.x? It seems to me it was quite useful utility in many cases. E.g., I temporarily move data from failed drive to another one and I want to know immediately are there bad blocks on the replacement drive or not. Why should I rely upon capability of modern drives to remap bad blocks? Or should I store 3.x somewhere just for this purpose? Is it possible to get bad144 back? Yours, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message