![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to vdformat.8s CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8|
Return to vdformat.8s CVS log | Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8 |
1.1.1.2 ! root 1: .TH VDFORMAT 8S "01 March 1985" 1.1 root 2: .UC 4 3: .SH NAME 4: .I Vdformat 1.1.1.2 ! root 5: \- Format disk media and / or relocate bad sectors on drives attached ! 6: to VDDC disk controllers. 1.1 root 7: .SH DESCRIPTION 8: .PP 1.1.1.2 ! root 9: \fBVDFORMAT\fP can be used to format disk drives, relocate ! 10: known flawed sectors, verify disk surfaces, print seek profile graphs ! 11: for disk drives, exercise disk drives, and perform general disk drive ! 12: maintenance procedures. ! 13: .PP ! 14: VDFORMAT keeps track of all known flaws by placing their addresses in a ! 15: \fBbad sector map\fP on the last cylinder of each disk drive. This information ! 16: is used during subsequent formatter operations to keep all known ! 17: bad sectors correctly relocated. ! 18: .PP ! 19: Flaw addresses are loaded into the bad sector map in four ways. ! 20: The first is by ! 21: reading the manufacturer's flaw map directly from the disk surface. ! 22: The second is by automatically adding any new flaws found during verify ! 23: operations. The third is by direct operator entry. The fourth ! 24: is by reading the ! 25: entire disk surface once and taking note of any errors or relocations ! 26: found during the reads. ! 27: .PP ! 28: .SH Command overview ! 29: .PP ! 30: The following basic commands are \fIalways\fP ! 31: available, even when long formatting ! 32: operations are underway: 1.1 root 33: .PP 34: .nf 1.1.1.2 ! root 35: .in +3m ! 36: \fICommand\fP \fIAction\fP 1.1 root 37: 1.1.1.2 ! root 38: \fBHelp\fP Prints a list of available options. ! 39: \fBStatus\fP Display current state of formatter. ! 40: \fBKill\fP Aborts all operations. ! 41: .in -3m 1.1 root 42: .fi 1.1.1.2 ! root 43: .PP ! 44: There are two abbreviations available for the above commands. ! 45: These abbreviations are strictly for operator convenience. ! 46: They are: ! 47: .PP 1.1 root 48: .nf 1.1.1.2 ! root 49: .in +3m ! 50: \fIAbbreviation\fP \fICommand\fP ! 51: \fB?\fP Help ! 52: \fB!\fP Status ! 53: .in -3m 1.1 root 54: .fi 1.1.1.2 ! root 55: .PP ! 56: In addition, the following ! 57: commands are available from the \fIOperation\fP prompt level: ! 58: .PP 1.1 root 59: .nf 1.1.1.2 ! root 60: .in +3m ! 61: \fICommand\fP \fIAction\fP ! 62: ! 63: \fBList\fP List all operations specified so far. ! 64: \fBDelete\fP Delete specific operations. ! 65: \fBReset\fP Reinitialize \fBVDFORMAT\fP, and start all over again. ! 66: \fBStart\fP Start operations. ! 67: \fBInfo\fP Tell everything that is known about a disk. ! 68: \fBFormat\fP Format and verify disk surface. ! 69: \fBVerify\fP Non-destructively verify disk surface. ! 70: \fBRelocate\fP Add known flaws to bad sector map. ! 71: \fBCorrect\fP Correct erroneous relocations or drive identification. ! 72: \fBProfile\fP Print a graph of seek time vs seek length. ! 73: \fBExercise\fP Perform read / write / seek exercises on disk. ! 74: .in -3m 1.1 root 75: .fi 1.1.1.2 ! root 76: .PP ! 77: The starting banner prints the program name, version number, and enough ! 78: information for the operator to get started without ! 79: reading this manual page. 1.1 root 80: .nf 1.1.1.2 ! root 81: ! 82: \fIExample\fP ! 83: ! 84: \fBVDFORMAT\fP Version 3.0 ! 85: ! 86: Type "Help" for help, "Start" to start specified operations. ! 87: ! 88: Operation? 1.1 root 89: .fi 1.1.1.2 ! root 90: .PP ! 91: .SH Help ! 92: .PP ! 93: The operator has a help command available for use at \fIany\fP time. ! 94: The \fBHelp\fP command displays available options according to the ! 95: current context. ! 96: .PP ! 97: In addition to the examples below there are further examples of help ! 98: messages throughout the operation examples. 1.1 root 99: .nf 1.1.1.2 ! root 100: ! 101: \fIExample\fP ! 102: ! 103: Operation? \fBHelp\fP ! 104: The following operations are available: ! 105: Reset - Reinitialize \fBVDFORMAT\fP and start over. ! 106: List - List all operations specified so far. ! 107: Delete - Delete specific operations. ! 108: Format - Format and verify disk surface. ! 109: Verify - Non-destructively verify disk surface. ! 110: Relocate - Add known flaws to bad sector map. ! 111: Correct - Correct erroneous relocations or drive ID. ! 112: Info - Display known disk information. ! 113: Profile - Display seek profile graph of disk. ! 114: Exercise - Perform seek exercises on disk. ! 115: Start - Start operations. ! 116: ! 117: Operation? 1.1 root 118: .fi 1.1.1.2 ! root 119: .SH Status ! 120: .PP ! 121: The \fBStatus\fP command may be typed in at any time to determine the ! 122: status of the formatter. The status message will explain ! 123: what the formatter is waiting for, ! 124: the current operation, and a progress report ! 125: if the formatter is busy. 1.1 root 126: .nf 1.1.1.2 ! root 127: ! 128: \fIExample\fP ! 129: ! 130: Starting format on controller 0, drive 1, drive type is FSD. ! 131: ! 132: \fBHelp\fP ! 133: The following commands are available: ! 134: Status - Display current state of formatter. ! 135: ! 136: \fBStatus\fP ! 137: Formatting on controller 0, drive 1, drive type is FSD. ! 138: Inspecting disk to determine current state. ! 139: Currently inspecting cylinder 120, track 10, sector 15. ! 140: ! 141: Formatting completed successfully. 1.1 root 142: .fi 1.1.1.2 ! root 143: .SH Kill ! 144: .PP ! 145: The \fBKill\fP command may be used to stop operations that are in ! 146: progress already. \fBKill\fP will always have meaning, may ! 147: be issued at any time, and will always leave disks in a consistent state. ! 148: .SH Specifying operations ! 149: .PP ! 150: Formatter operations are broken into two phases: entry ! 151: and execution. ! 152: .PP ! 153: During the entry phase the operator enters all the ! 154: disk operations that he / she wants to execute during the execution ! 155: phase. After the operation list is entered correctly the operator ! 156: issues the start command and execution begins. ! 157: .PP ! 158: The execution phase executes all commands specified during the entry phase ! 159: on the specified disks. These commands are accumulated and executed ! 160: later because each operation may require up to several hours to complete. ! 161: By deferring operations, \fBVDFORMAT\fP frees the operator to do other ! 162: work during this time period. ! 163: .PP ! 164: The commands that are detailed in this section ! 165: are grouped according to the immediacy of their ! 166: actions. Commands such as \fBDelete\fP and \fBReset\fP, ! 167: which will execute the moment they are ! 168: keyed into the system, are termed immediate commands. ! 169: Commands which ! 170: effect after the \fBStart\fP command is issued ! 171: are termed deferred commands. ! 172: .SH Immediate commands ! 173: .PP ! 174: Instead of forcing the operator to specify one operation on one drive ! 175: at a time, ! 176: comma separated lists and dash separated ranges can ! 177: be entered for operations, controller ! 178: numbers, and drive numbers. ! 179: Please refer to examples. ! 180: .SH List operation ! 181: .PP ! 182: The \fBList\fP operation displays all commands that ! 183: were keyed in by the operator and are ready to ! 184: be executed when the \fBStart\fP command is issued. 1.1 root 185: .nf 1.1.1.2 ! root 186: ! 187: \fIExample\fP ! 188: ! 189: Operation? \fBList\fP ! 190: The following operations will occur when Start is issued: ! 191: ! 192: Format on Controller 0, drive 1, type FSD. ! 193: Format on Controller 0, drive 2, type XFD. ! 194: Format on Controller 0, drive 3, type XFD. ! 195: Relocate on Controller 0, drive 0, type FSD. 1.1 root 196: .fi 1.1.1.2 ! root 197: .SH Delete operation ! 198: .PP ! 199: Delete is intended to provide a simple editing facility for command ! 200: lists. Between the \fBDelete\fP operation and the ability to add more ! 201: operations to the operation list, Any error in the operation list ! 202: can be corrected. ! 203: .PP ! 204: When the delete operation is specified, a numbered list of operations ! 205: is printed on the console and \fBVDFORMAT\fP will repeatedly ! 206: ask for line numbers to delete. ! 207: .PP ! 208: Line numbering for the \fBDelete\fP operation will remain the same ! 209: even after a line is deleted. This is done to avoid confusion, but ! 210: it implies that the same line can be deleted multiple times. This ! 211: presents no problems for the formatter and no error will be returned ! 212: if this is done. ! 213: .PP ! 214: The \fBDelete\fP prompt level is terminated by entering 'Quit' ! 215: (or the \fBKill\fP command) as shown in the following example: 1.1 root 216: .nf 1.1.1.2 ! root 217: ! 218: \fIExample\fP ! 219: ! 220: Operation? \fBDelete\fP ! 221: 1) Format on Controller 0, drive 1, type FSD. ! 222: 2) Format on Controller 0, drive 2, type XFD. ! 223: 3) Format on Controller 0, drive 3, type XFD. ! 224: 4) Format on Controller 1, drive 0, type XSD. ! 225: 5) Format on Controller 1, drive 1, type XSD. ! 226: 6) Format on Controller 1, drive 2, type XSD. ! 227: 7) Format on Controller 1, drive 3, type XSD. ! 228: 8) Relocate on Controller 0, drive 0, type FSD. ! 229: ! 230: Delete line? \fB2\fP ! 231: 2) Format using Controller 0, drive 2, type FSD has been deleted. ! 232: Delete line? \fB8\fP ! 233: 8) Relocate using Controller 0, drive 0, type FSD has been deleted. ! 234: Delete line? \fBQuit\fP ! 235: ! 236: Operation? ! 237: 1.1 root 238: .fi 1.1.1.2 ! root 239: .SH Reset operation ! 240: .PP ! 241: The \fBReset\fP operation clears all commands keyed in so far ! 242: and executes internal consistency checks for the ! 243: formatter. The main use is to quickly delete all operations, ! 244: and reset internal state. ! 245: The operator who really messed up the command sequence can start ! 246: again from the top. 1.1 root 247: .nf 1.1.1.2 ! root 248: ! 249: \fIExample\fP ! 250: ! 251: Operation? \fBReset\fP ! 252: Reset the world. Are you sure? \fBYes\fP ! 253: ! 254: All operations specified have been deleted. ! 255: ! 256: Operation? 1.1 root 257: .fi 1.1.1.2 ! root 258: .SH Start operations ! 259: .PP ! 260: The \fBStart\fP command starts processing the command list ! 261: that was typed in by the operator. The operator should be sure ! 262: that all commands are correct before proceeding. 1.1 root 263: .nf 1.1.1.2 ! root 264: ! 265: \fIExample\fP ! 266: ! 267: Operation? \fBStart\fP ! 268: ! 269: Starting format on controller 0, drive 1, drive type is FSD. 1.1 root 270: .fi 1.1.1.2 ! root 271: .SH All the following commands are deferred commands. 1.1 root 272: .sp 1 1.1.1.2 ! root 273: .SH Info operation ! 274: .PP ! 275: \fBInfo\fP gives a full report of everything that is known about a drive. ! 276: This includes which ! 277: sectors were bad, to what sector they were relocated, ! 278: how were the errors detected, and ! 279: the current format state. ! 280: .PP 1.1 root 281: .nf 1.1.1.2 ! root 282: ! 283: \fIExample\fP ! 284: ! 285: Operation? \fBInfo\fP ! 286: Gather information on which controller? \fB0\fP ! 287: Drives on controller 0? \fB1\fP ! 288: Drive type for controller 0 drive 1? \fBfsd\fP ! 289: ! 290: Operation? \fBStart\fP ! 291: ! 292: Gathering information for controller 0, drive 1. ! 293: ! 294: Module number is 123456789. ! 295: Drive type is FSD. ! 296: Drive contains a bad sector map. ! 297: The following sectors are known to be bad: ! 298: cyl 181, head 2, pos 4470, len 1 (Sector #57991) -> sector 261760. ! 299: cyl 210, head 6, pos 8880, len 1 (Sector #67406) -> sector 261764. ! 300: cyl 292, head 3, pos 19590, len 1 (Sector #93567) -> sector 261761. ! 301: cyl 293, head 3, pos 19590, len 1 (Sector #93887) -> sector 261762. ! 302: Information display completed successfully. 1.1 root 303: .fi 1.1.1.2 ! root 304: .SH Format operation ! 305: .PP ! 306: The \fBformat\fP operation will read ! 307: the flaw map information directly from the drives and use that information to ! 308: map out all flaws after formatting the drive's surface. ! 309: .PP ! 310: After formatting the drive's surface the drive surface is verified using ! 311: the number of patterns requested by the operator. The number of patterns ! 312: may range from 0 to 16. It is suggested that at least one pattern be used ! 313: so potential drive problems are more likely to be found before real information ! 314: is written on the drives. ! 315: .PP 1.1 root 316: .nf 1.1.1.2 ! root 317: ! 318: \fIExample\fP ! 319: ! 320: Operation? \fBFormat\fP ! 321: Format on which controller? \fBHelp\fP ! 322: The following controllers are attached to the system ! 323: Controller 0, which is a VDDC controller. ! 324: Controller 1, which is an SMD-E controller. ! 325: Controller 2, which is an SMD-E controller. ! 326: ! 327: Format on which controller? \fB0\fP ! 328: Number of patterns to use when verifying? \fB1\fP ! 329: Drives on controller 0? \fBHelp\fP ! 330: Drives 0 through 3 are acceptable on VDDC controllers. ! 331: ! 332: Drives on controller 0? \fB1\fP ! 333: Drive type for controller 0 drive 1? \fBHelp\fP ! 334: The following drive types are available to VDDC controllers: ! 335: FSD - 160 Mb Control Data winchester drive. ! 336: SMD - 300 Mb Control Data Removable media drive. ! 337: XFD - 340 Mb Control Data winchester drive. ! 338: ! 339: Drive type for controller 0 drive 1? \fBfsd\fP ! 340: Module serial number for controller 0 drive 1? \fB1234\fP ! 341: ! 342: Operation? \fBStart\fP ! 343: ! 344: Starting format on controller 0, drive 1, drive type is FSD. ! 345: ! 346: ** Warning - Unable to relocate sector 12347, ! 347: to map out using BADSECT use the following values: ! 348: On the 'a' partition use block 6000 ! 349: On the 'c' partition use block 25 ! 350: ! 351: Formatting completed successfully. 1.1 root 352: .fi 1.1.1.2 ! root 353: .SH Verify operation ! 354: .PP ! 355: The verify operation can be used to check for new flaws on a disk ! 356: that currently has data ! 357: on it. This is accomplished by ! 358: writing the necessary patterns on the drive's surface, reading the information ! 359: back, and comparing the results to the original pattern. ! 360: If a flaw is found ! 361: the sector is relocated immediately. ! 362: Each new flaw will be relocated and permanently ! 363: added to the bad sector map. ! 364: .PP 1.1 root 365: .nf 1.1.1.2 ! root 366: ! 367: \fIExample\fP ! 368: ! 369: Operation? \fBVerify\fP ! 370: Verify on which controller? \fB0\fP ! 371: Drives on controller 0? \fB1\fP ! 372: Drive type for controller 0 drive 1? \fBfsd\fP ! 373: ! 374: Operation? \fBStart\fP ! 375: ! 376: Starting verify on controller 0, drive 1, drive type is FSD. ! 377: ! 378: Verification completed successfully. 1.1 root 379: .fi 1.1.1.2 ! root 380: .SH Relocate operation ! 381: .PP ! 382: The operator has the ability to manually type in known flaws ! 383: using the CDC flaw map format, UNIX file-system / block numbers, ! 384: absolute sector numbers, and absolute track numbers. ! 385: .PP ! 386: \fBVDFORMAT\fP will automatically switch back and forth between ! 387: the various forms of inputing flaw addresses ! 388: by looking at the first character on any ! 389: line. If the first character is between 'a' and 'h' then ! 390: it is assumed that the character is a file system name and the ! 391: next input will be the actual UNIX block number, if the first character is ! 392: an 's' then sector numbers are entered, if the first character is an 't' ! 393: then track numbers are entered, otherwise ! 394: flaw map format is assumed. ! 395: .nf ! 396: ! 397: \fIExample\fP ! 398: ! 399: Operation? \fBRelocate\fP ! 400: Relocate on controller? \fB0\fP ! 401: Drives on controller 0? \fB0\fP ! 402: Drive type for controller 0 drive 0? \fBfsd\fP ! 403: ! 404: Operation? \fBStart\fP ! 405: ! 406: Adding flaws to bad sector map on Controller 0, drive 1, type FSD. ! 407: Location? \fBa 20\fP ! 408: Confirm block 20 on file-system 'a' ? \fBYes\fP ! 409: Location? \fB10 5 12594 10\fP ! 410: Confirm Cyl 10, head 5, offset 12594, len 10 (Sector 12345)? \fBYes\fP ! 411: Location? \fBSector 1000\fP ! 412: Confirm sector 1000? \fBYes\fP ! 413: Location? \fBTrack 25\fP ! 414: Confirm track 25? \fBYes\fP ! 415: Location? \fBa 200\fP ! 416: Confirm relocation of block 200 on file-system 'a' ? \fBYes\fP ! 417: Location? \fBStart\fP ! 418: Relocation complete. ! 419: ! 420: Operation? 1.1 root 421: .fi 1.1.1.2 ! root 422: .SH Correct operation ! 423: .PP ! 424: The correct operation is used to correct any information that ! 425: was incorrectly written to disk. ! 426: This information includes sectors that were wrongly specified by ! 427: the operator and the operator entered pack identification. ! 428: .PP 1.1 root 429: .nf 1.1.1.2 ! root 430: ! 431: \fIExample\fP ! 432: ! 433: Operation? \fBCorrect\fP ! 434: Correct on controller? \fB0\fP ! 435: Drives on controller 0? \fB0\fP ! 436: Drive type for controller 0 drive 0? \fBfsd\fP ! 437: ! 438: Operation? \fBStart\fP ! 439: ! 440: Making corrections to bad sector map on Controller 0, drive 0, type FSD ! 441: Location? \fBID\fP ! 442: Pack ID is 123456789. Change to? \fB1234567890\fP ! 443: Pack ID changed to 1234567890. ! 444: Location? \fBse 20\fP ! 445: Confirm relocation removal of sector 20? \fBYes\fP ! 446: Sector 20 removed. ! 447: Location? \fBt 21\fP ! 448: Confirm relocation removal of track 21? \fBYes\fP ! 449: Track 21 removed. ! 450: Location? \fB10 5 125\fP ! 451: Confirm relocation removal of Cylinder 10, head 5, offset 125? \fBYes\fP ! 452: Cylinder 10, head 5, offset 125 removed. ! 453: Location? \fBStart\fP ! 454: Relocation complete. ! 455: ! 456: Operation? 1.1 root 457: .fi 1.1.1.2 ! root 458: .SH Profile operation ! 459: .PP ! 460: The profile operation is used to print a graph of seek time verses seek ! 461: distance for the specified drive. Each point on the graph prints as either ! 462: a star ('*') or a plus ('+') to indicate which direction the point ! 463: was rounded. The star shows that the point was rounded up, and the plus ! 464: shows rounding down has taken place. ! 465: .nf ! 466: ! 467: \fIExample\fP ! 468: ! 469: Operation? \fBProfile\fP ! 470: Profile on controller? \fB0\fP ! 471: Drives on controller 0? \fB0\fP ! 472: Drive type for controller 0 drive 0? \fBxsd\fP ! 473: Operation? \fBStart\fP ! 474: ! 475: Disk seek profile for controller 0, drive 0, type XSD. ! 476: ! 477: Seek | Seek time (ms) ! 478: Length |0 5 10 15 20 25 30 35 40 45 50 ! 479: -------|-----+----+----+----+----+----+----+----+----+----+ ! 480: 1 | * ! 481: 13 | + ! 482: 25 | + ! 483: 37 | * ! 484: 49 | * ! 485: 61 | + ! 486: 73 | + ! 487: 85 | + ! 488: 97 | * ! 489: 109 | + ! 490: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ! 491: ! 492: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ! 493: 577 | * ! 494: 589 | + ! 495: 601 | * ! 496: 613 | * ! 497: 625 | + ! 498: 637 | * ! 499: 697 | + ! 500: 709 | * ! 501: -------|-----+----+----+----+----+----+----+----+----+----+ ! 502: |0 5 10 15 20 25 30 35 40 45 50 ! 503: ! 504: Profile completed successfully. 1.1 root 505: .fi 1.1.1.2 ! root 506: .SH Exercise operation ! 507: .PP ! 508: The exercise operation does an exhaustive test of the drive read / write / seek ! 509: logic on a drive. The test is destructive and calculations show that it ! 510: should take about 22 weeks to complete the entire test. It is suggested that ! 511: the test be run for as long as the operator can take it before killing the test. ! 512: (24 hours is about right.) ! 513: .nf ! 514: ! 515: \fIExample\fP ! 516: ! 517: Operation? \fBExercise\fP ! 518: Profile on controller? \fB0\fP ! 519: Drives on controller 0? \fB0\fP ! 520: Drive type for controller 0 drive 0? \fBxsd\fP ! 521: Operation? \fBStart\fP ! 522: ! 523: Starting disk exercise on controller 0, drive 0, type XSD. ! 524: Pass 1... ! 525: Pass 2... ! 526: Pass 3... ! 527: . ! 528: . ! 529: . ! 530: Pass 710... ! 531: Exercise completed successfully. 1.1 root 532: .fi 1.1.1.2 ! root 533: ! 534: .SH DIAGNOSTICS ! 535: .PP ! 536: The controller status will be printed out after any unrecoverable error ! 537: is found. The exact meaning of the error words can be found in \fBvddc(4)\fP. ! 538: .SH SEE ALSO ! 539: .PP ! 540: vddc(4)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.