|
|
1.1 ! root 1: ! 2: ! 3: bad Command bad ! 4: ! 5: ! 6: ! 7: ! 8: Maintain list of bad blocks ! 9: ! 10: bbaadd _o_p_t_i_o_n _f_i_l_e_s_y_s_t_e_m [ block ... ] ! 11: ! 12: A hard disk or floppy disk may have bad blocks on it: a ``bad ! 13: block'' is a portion of disk that cannot be used reliably because ! 14: read or write errors occur on them. The COHERENT system keeps a ! 15: list of bad blocks so it can avoid using them. ! 16: ! 17: The command bad maintains the bad-block list for the given ! 18: filesystem, which must be a block-special file. option must be ! 19: exactly one of the characters acdl, which tell bad to do one of ! 20: the following: ! 21: ! 22: ! 23: aa Add each given _b_l_o_c_k to the bad-block list ! 24: cc Clear the bad-block list ! 25: dd Delete each given _b_l_o_c_k from the bad-block list ! 26: ll List all blocks on the bad-block list ! 27: ! 28: ! 29: bad does not deallocate any i-node associated with a block when ! 30: adding it to the bad-block list. You should run the command ! 31: icheck with the -s option immediately after bad to correct the ! 32: problem, or run the command fsck. ! 33: ! 34: filesystem should be unmounted if possible. The user who invokes ! 35: bad must have appropriate permissions for the given filesystem. ! 36: For many file systems, only the superuser may use bad to change ! 37: the bad-block list. Use the command badscan to create a ! 38: prototype file. ! 39: ! 40: When the mkfs command creates a file system, the prototype ! 41: specification may include a bad block list for the new file sys- ! 42: tem. ! 43: ! 44: ***** See Also ***** ! 45: ! 46: badscan, commands, icheck, mkfs, umount ! 47: ! 48: ! 49: ! 50: ! 51: ! 52: ! 53: ! 54: ! 55: ! 56: ! 57: ! 58: ! 59: ! 60: ! 61: ! 62: ! 63: ! 64: COHERENT Lexicon Page 1 ! 65: ! 66:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.