Return to badsect.8 CVS log

Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8

Annotation of cci/usr/src/man/man8/badsect.8, revision 1.1.1.1

1.1       root        1: .TH BADSECT 8 "25 February 1983"
                      2: .UC 4
                      3: .SH NAME
                      4: badsect \- create files to contain bad sectors
                      5: .SH SYNOPSIS
                      6: .B /etc/badsect
                      7: bbdir sector ...
                      8: .SH DESCRIPTION
                      9: .I Badsect
                     10: makes a file to contain a bad sector.  Normally, bad sectors
                     11: are made inaccessible by the standard formatter, which provides
                     12: a forwarding table for bad sectors to the driver. 
                     13: If a driver supports the bad blocking standard it is much preferable to
                     14: use that method to isolate bad blocks, since the bad block forwarding
                     15: makes the pack appear perfect, and such packs can then be copied with
                     16: .IR dd (1).
                     17: The technique used by this program is also less general than
                     18: bad block forwarding, as
                     19: .I badsect
                     20: can't make amends for
                     21: bad blocks in the i-list of file systems or in swap areas.
                     22: .PP
                     23: .I Badsect
                     24: is used on a quiet file system in the following way:
                     25: First mount the file system, and change to its root directory.
                     26: Make a directory BAD there.  Run
                     27: .I badsect
                     28: giving as argument the BAD directory followed by
                     29: all the bad sectors you wish to add.
                     30: (The sector numbers must be relative to the beginning of
                     31: the file system, but this is not hard as the system reports
                     32: relative sector numbers in its console error messages.)
                     33: Then change back to the root directory, unmount the file system
                     34: and run
                     35: .IR fsck (8)
                     36: on the file system.  The bad sectors should show up in two files
                     37: or in the bad sector files and the free list.  Have
                     38: .I fsck
                     39: remove files containing the offending bad sectors, but 
                     40: .B "do not"
                     41: have it remove the BAD/\fInnnnn\fR files.
                     42: This will leave the bad sectors in only the BAD files.
                     43: .PP
                     44: .I Badsect
                     45: works by giving the specified sector numbers in a
                     46: .IR mknod (2)
                     47: system call,
                     48: creating an illegal file whose first block address is the block containing
                     49: bad sector and whose name is the bad sector number.
                     50: When it is discovered by 
                     51: .I fsck
                     52: it will ask ``HOLD BAD BLOCK''?
                     53: A positive response will cause 
                     54: .I fsck
                     55: to convert the inode to a regular file containing the bad block.
                     56: .SH SEE ALSO
                     57: fsck(8),
                     58: vdformat(8V)
                     59: .SH DIAGNOSTICS
                     60: .I Badsect
                     61: refuses to attach a block that
                     62: resides in a critical area or is out of range of the file system.
                     63: A warning is issued if the block is already in use.
                     64: .SH BUGS
                     65: If more than one sector which comprise a file system fragment are bad,
                     66: you should specify only one of them to
                     67: .I badsect,
                     68: as the blocks in the bad sector files actually cover all the sectors in a
                     69: file system fragment.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.