Date: Thu, 24 Aug 1995 17:10:55 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: hackers@freebsd.org Subject: Re: On ESDI install. Message-ID: <199508241511.RAA17646@uriah.heep.sax.de> In-Reply-To: <199508241304.IAA19423@bonkers.taronga.com> from "Peter da Silva" at Aug 24, 95 08:04:56 am
next in thread | previous in thread | raw e-mail | index | archive | help
As Peter da Silva wrote:
>
> Xenix did all their bad blocks that way. Created a .badblock file in the
> partition root and filled it with bad blocks. Was a lot more convenient than
> bad144...
BADSECT(8) UNIX System Manager's Manual BADSECT(8)
NAME
badsect - create files to contain bad sectors
SYNOPSIS
/etc/badsect bbdir sector ...
DESCRIPTION
Badsect makes a file to contain a bad sector. Normally, bad sectors are
made inaccessible by the standard formatter, which provides a forwarding
table for bad sectors to the driver; see bad144(8) for details. If a
driver supports the bad blocking standard it is much preferable to use
that method to isolate bad blocks, since the bad block forwarding makes
the pack appear perfect, and such packs can then be copied with dd(1).
The technique used by this program is also less general than bad block
forwarding, as badsect can't make amends for bad blocks in the i-list of
file systems or in swap areas.
"/etc/badsect", hmmm. :) Despite of this, the problems of this
approach are clearly outlined above.
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508241511.RAA17646>