.\" Copyright (c) 1985 The Regents of the University of California.
.\" Redistribution and use in source and binary forms are permitted
.\" provided that the above copyright notice and this paragraph are
.\" duplicated in all such forms and that any documentation,
.\" advertising materials, and other materials related to such
.\" distribution and use acknowledge that the software was developed
.\" by the University of California, Berkeley. The name of the
.\" University may not be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
.\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
.\" @(#)badsect.8 6.2 (Berkeley) %G%
badsect \- create files to contain bad sectors
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
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
The technique used by this program is also less general than
bad blocks in the i-list of file systems or in swap areas.
adding a sector which is suddenly bad to the bad sector table
currently requires the running of the standard DEC formatter.
Thus to deal with a newly bad block
or on disks where the drivers
do not support the bad-blocking standard
may be used to good effect.
is used on a quiet file system in the following way:
First mount the file system, and change to its root directory.
Make a directory BAD there. Run
giving as argument the BAD directory followed by
all the bad sectors you wish to add.
(The sector numbers must be relative to the beginning of
the file system, but this is not hard as the system reports
relative sector numbers in its console error messages.)
Then change back to the root directory, unmount the file system
on the file system. The bad sectors should show up in two files
or in the bad sector files and the free list. Have
remove files containing the offending bad sectors, but
have it remove the BAD/\fInnnnn\fR files.
This will leave the bad sectors in only the BAD files.
works by giving the specified sector numbers in a
creating an illegal file whose first block address is the block containing
bad sector and whose name is the bad sector number.
it will ask ``HOLD BAD BLOCK''?
A positive response will cause
to convert the inode to a regular file containing the bad block.
refuses to attach a block that
resides in a critical area or is out of range of the file system.
A warning is issued if the block is already in use.
If more than one sector which comprise a file system fragment are bad,
you should specify only one of them to
as the blocks in the bad sector files actually cover all the sectors in a