minor rearrangements

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

diff --git a/usr/src/usr.sbin/bad144/bad144.8 b/usr/src/usr.sbin/bad144/bad144.8
index 2ae6c4e..30e6b2d 100644 (file)
--- a/usr/src/usr.sbin/bad144/bad144.8
+++ b/usr/src/usr.sbin/bad144/bad144.8
@@ -2,18 +2,39 @@
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"

-.\"    @(#)bad144.8    4.1 (Berkeley) %G%
+.\"    @(#)bad144.8    6.3 (Berkeley) %G%

 .\"
 .\"

-.TH BAD144 8 "5/11/81"
+.TH BAD144 8 ""

 .UC 4
 .SH NAME
 bad144 \- read/write dec standard 144 bad sector information
 .SH SYNOPSIS
 .UC 4
 .SH NAME
 bad144 \- read/write dec standard 144 bad sector information
 .SH SYNOPSIS

-.B bad144
+.B /etc/bad144
+[
+.B \-f
+] [
+.B \-c
+] [
+.B \-v
+]

 disktype disk
 [ sno [
 bad ...
 ] ]
 disktype disk
 [ sno [
 bad ...
 ] ]

+.br
+.B /etc/bad144
+.B \-a
+[
+.B \-f
+] [
+.B \-c
+] [
+.B \-v
+]
+disktype disk
+[
+bad ...
+]

 .SH DESCRIPTION
 .I Bad144
 can be used to inspect the information stored on a disk that is used by
 .SH DESCRIPTION
 .I Bad144
 can be used to inspect the information stored on a disk that is used by


@@ -22,19 +43,24 @@ the information is specified by DEC standard 144, as follows.
 .PP
 The bad sector information is located in the first 5 even numbered sectors
 of the last track of the disk pack.  There are five identical copies of
 .PP
 The bad sector information is located in the first 5 even numbered sectors
 of the last track of the disk pack.  There are five identical copies of

-the information, described by the dkbad structure.
+the information, described by the
+.I dkbad
+structure.

 .PP
 Replacement sectors are allocated starting with the first sector before
 the bad sector information and working backwards towards the beginning
 of the disk.  A maximum of 126 bad sectors are supported.  The position
 .PP
 Replacement sectors are allocated starting with the first sector before
 the bad sector information and working backwards towards the beginning
 of the disk.  A maximum of 126 bad sectors are supported.  The position

-of the bad sector in the bad sector table determines which replacement
-sector it corresponds to.
+of the bad sector in the bad sector table determines the replacement
+sector to which it corresponds.
+The bad sectors must be listed in ascending order.

 .PP
 The bad sector information and replacement sectors are conventionally
 .PP
 The bad sector information and replacement sectors are conventionally

-only accessable through the ``c'' file system partition of the disk.  If
+only accessible through the ``c'' file system partition of the disk.  If

 that partition is used for a file system, the user is responsible for
 making sure that it does not overlap the bad sector information or any
 replacement sectors.
 that partition is used for a file system, the user is responsible for
 making sure that it does not overlap the bad sector information or any
 replacement sectors.

+Thus, one track plus 126 sectors must be reserved to allow use
+of all of the possible bad sector replacements.

 .PP
 The bad sector structure is as follows:
 .PP
 .PP
 The bad sector structure is as follows:
 .PP


@@ -51,37 +77,70 @@ struct dkbad {
 };
 .fi
 .PP
 };
 .fi
 .PP

-Unused slots in the bt_bad array are filled with all bits set, a putatively
+Unused slots in the
+.I bt_bad
+array are filled with all bits set, a putatively

 illegal value.
 .PP
 .I Bad144
 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device
 illegal value.
 .PP
 .I Bad144
 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device

-name (e.g. hk0, hp1, etc.).  It reads the first sector of the last track
+name (e.g. hk0, hp1, etc.).  With no optional arguments
+it reads the first sector of the last track

 of the corresponding disk and prints out the bad sector information.
 of the corresponding disk and prints out the bad sector information.

-It may also be invoked giving a serial number for the pack and a list
-of bad sectors, and will then write the supplied information onto the
-same location.  Note, however, that 
+It issues a warning if the bad sectors are out of order.
+.I Bad144
+may also be invoked with a serial number for the pack and a list
+of bad sectors.
+It will write the supplied information into all copies
+of the bad-sector file, replacing any previous information.
+Note, however, that 

 .I bad144
 does not arrange for the specified sectors to be marked bad in this case.
 .I bad144
 does not arrange for the specified sectors to be marked bad in this case.

-This option should only be used to restore known bad sector information which
+This procedure should only be used to restore known bad sector information which

 was destroyed.
 was destroyed.

+It is necessary to reboot before any change will take effect.

 .PP
 .PP

-New bad sectors can be added by running the standard DEC formatter in
-section ``bad''.
+With the
+.B \-a
+option,
+the argument list consists of new bad sectors to be added to an existing
+list.
+The new sectors are sorted into the list,
+which must have been in order.
+Replacement sectors are moved to accommodate the additions;
+the new replacement sectors are cleared.
+The entire process is described as it happens in gory detail if
+.B \-v
+(verbose) is given.
+The
+.B \-c
+option forces an attempt to copy the old sector to the replacement,
+and may be useful when replacing an unreliable sector.
+.PP
+If the disk is an RP06, RM03, RM05, Fujitsu Eagle,
+or SMD disk on a Massbus, the
+.B \-f
+option may be used to mark the new bad sectors as ``bad''
+by reformatting them as unusable sectors.
+\fBNOTE:  this can be done safely only when there is no other disk activity\fP,
+preferably while running single-user.
+This option is required unless the sectors have already been marked bad,
+or the system will not be notified that it should use the replacement sector.

 .SH SEE ALSO
 .SH SEE ALSO

-badsect (8), format (8)
+badsect(8),
+format(8V)

 .SH BUGS
 .SH BUGS

-It should be possible to both format disks on-line under UNIX and to change
-the bad sector information, marking new bad sectors, without running
-a standalone program.
+It should be possible to format disks on-line under UNIX.
+.PP
+It should be possible to mark bad sectors on drives of all type.

 .PP
 .PP

-The bootstrap drivers used to boot the system do not understand bad sectors,
-handle ECC errors, or the special SSE (skip sector) errors of RM80 type disks.
+On an 11/750,
+the standard bootstrap drivers used to boot the system do
+not understand bad sectors,
+handle ECC errors, or the special SSE (skip sector) errors of RM80-type disks.

 This means that none of these errors can occur when reading the file
 This means that none of these errors can occur when reading the file

-/vmunix to boot.  When a disk drive is used to load the bootstrap code
-(the alternative would be that the bootstrap would be loaded from the console
-media), sector 0 of the disk drive and the file /boot in the root file
-system of that drive must also not have any of these errors in it.
+/vmunix to boot.  Sectors 0-15 of the disk drive
+must also not have any of these errors.

 .PP
 The drivers which write a system core image on disk after a crash do not
 handle errors; thus the crash dump area must be free of errors and bad
 .PP
 The drivers which write a system core image on disk after a crash do not
 handle errors; thus the crash dump area must be free of errors and bad