BSD 4_3_Reno release

[unix-history] / usr / src / sbin / badsect / badsect.8

diff --git a/usr/src/sbin/badsect/badsect.8 b/usr/src/sbin/badsect/badsect.8
index 865bb16..fb45320 100644 (file)
--- a/usr/src/sbin/badsect/badsect.8
+++ b/usr/src/sbin/badsect/badsect.8
@@ -1,16 +1,29 @@
-.\" Copyright (c) 1980 Regents of the University of California.
-.\" All rights reserved.  The Berkeley software License Agreement
-.\" specifies the terms and conditions for redistribution.
+.\" Copyright (c) 1985 The Regents of the University of California.
+.\" All rights reserved.

 .\"
 .\"

-.\"    @(#)badsect.8   4.1 (Berkeley) %G%
+.\" Redistribution and use in source and binary forms are permitted provided
+.\" that: (1) source distributions retain this entire copyright notice and
+.\" comment, and (2) distributions including binaries display the following
+.\" acknowledgement:  ``This product includes software developed by the
+.\" University of California, Berkeley and its contributors'' in the
+.\" documentation or other materials provided with the distribution and in
+.\" all advertising materials mentioning features or use of this software.
+.\" Neither the name of the University nor the names of its contributors may
+.\" 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
+.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

 .\"
 .\"

-.TH BADSECT 8 4/10/81
+.\"    @(#)badsect.8   6.3 (Berkeley) 6/24/90
+.\"
+.TH BADSECT 8 "June 24, 1990"

 .UC 4
 .SH NAME
 badsect \- create files to contain bad sectors
 .SH SYNOPSIS
 .B /etc/badsect
 .UC 4
 .SH NAME
 badsect \- create files to contain bad sectors
 .SH SYNOPSIS
 .B /etc/badsect

-sector ...
+bbdir sector ...

 .SH DESCRIPTION
 .I Badsect
 makes a file to contain a bad sector.  Normally, bad sectors
 .SH DESCRIPTION
 .I Badsect
 makes a file to contain a bad sector.  Normally, bad sectors


@@ -21,30 +34,32 @@ 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
 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).
+.IR dd (1).

 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
 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

-Adding a sector which is suddenly bad to the bad sector table
-currently requires the running of the standard DEC formatter, as
-UNIX does not supply formatters.  Thus to deal with a newly bad block
+On some disks,
+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 
 .I badsect
 or on disks where the drivers
 do not support the bad-blocking standard 
 .I badsect

-may be used to good
-effect.
+may be used to good effect.

 .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.
 .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.)
+Make a directory BAD there.  Run
+.I badsect
+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
 and run
 .IR fsck (8)
 Then change back to the root directory, unmount the file system
 and run
 .IR fsck (8)


@@ -60,19 +75,26 @@ This will leave the bad sectors in only the BAD files.
 works by giving the specified sector numbers in a
 .IR mknod (2)
 system call,
 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
+creating an illegal file whose first block address is the block containing

 bad sector and whose name is the bad sector number.
 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
+When it is discovered by 
+.I fsck
+it will ask ``HOLD BAD BLOCK''?
+A positive response will cause 
+.I fsck
+to convert the inode to a regular file containing the bad block.

 .SH SEE ALSO
 .SH SEE ALSO

-bad144(8), fsck (8)
+bad144(8),
+fsck(8),
+format(8V)
+.SH DIAGNOSTICS
+.I Badsect
+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.

 .SH BUGS
 .SH BUGS

-If both sectors which comprise a (1024 byte) disk block are bad,
+If more than one sector which comprise a file system fragment are bad,

 you should specify only one of them to
 .I badsect,
 you should specify only one of them to
 .I badsect,

-as the blocks in the bad sector files actually cover both (bad)
-disk sectors.
+as the blocks in the bad sector files actually cover all the sectors in a
+file system fragment.