DataMuseum.dk

top - metrics - download

    Length: 2328 (0x918)
    Types: TextFile
    Notes: UNIX file
    Names: »badsect.8«

└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
    └─⟦28c352965⟧ »/a« UNIX Filesystem
        └─⟦this⟧ »usr/man/man8/badsect.8« 

TextFile

.ig
	@(#)badsect.8	2.1	7/1/84
	@(#)Copyright (C) 1983 by National Semiconductor Corp.
..
.TH BADSECT 8
.SH NAME
badsect \- create files to contain bad sectors
.SH SYNOPSIS
.B /etc/badsect
sector ...
.SH DESCRIPTION
.I 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.
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
.IR dd (8).
The technique used by this program is also less general than
bad block forwarding, as
.I badsect
can't make amends for
bad blocks in the i-list of file systems or in swap areas.
.PP
.I Badsect
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 and change into it.  Run badsect
giving as argument all the bad sectors you wish to add.
(The sector numbers should be relative to the beginning of
the file system, but this is not hard to do as
the system reports relative sector numbers in its console error messages.)
Then change back to the root directory, unmount the file system
and run
.IR fsck (8)
on the file system.  The bad sectors should show up in two files
or in the bad sector files and the free list.  Have
.I fsck
remove files containing the offending bad sectors, but 
.B "do not"
have it remove the BAD/\fInnnnn\fR files.
This will leave the bad sectors in only the BAD files.
.PP
.I Badsect
works by giving the specified sector numbers in a
.IR mknod (2)
system call,
creating a regular file whose first block address is the block containing
bad sector and whose name is the bad sector number.
The file has 0 length, but the check programs
will still consider it to contain the block containing the sector.
This has the pleasant effect that the sector is completely inaccessible
to the containing file system
since it is not available by accessing the file.
.PP
.SH SEE ALSO
bad144(8), fsck (8)
.SH BUGS
If both sectors which comprise a (1024 byte) disk block are bad,
you should specify only one of them to
.I badsect,
as the blocks in the bad sector files actually cover both (bad)
disk sectors.