Return to bad CVS log

Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT

coherent

bad                          Command                          bad




Maintain list of bad blocks

bbaadd _o_p_t_i_o_n _f_i_l_e_s_y_s_t_e_m [ block ... ]

A hard  disk or floppy  disk may have  bad blocks on  it: a ``bad
block'' is a portion of disk that cannot be used reliably because
read or write errors occur  on them.  The COHERENT system keeps a
list of bad blocks so it can avoid using them.

The  command  bad  maintains the  bad-block  list  for the  given
filesystem, which  must be a block-special  file.  option must be
exactly one of  the characters acdl, which tell bad  to do one of
the following:


     aa   Add each given _b_l_o_c_k to the bad-block list
     cc   Clear the bad-block list
     dd   Delete each given _b_l_o_c_k from the bad-block list
     ll   List all blocks on the bad-block list


bad does  not deallocate any i-node associated  with a block when
adding  it to  the bad-block  list.  You  should run  the command
icheck with  the -s option  immediately after bad  to correct the
problem, or run the command fsck.

filesystem should be unmounted if possible.  The user who invokes
bad must  have appropriate permissions for  the given filesystem.
For many  file systems, only the superuser may  use bad to change
the  bad-block  list.   Use  the  command  badscan  to  create  a
prototype file.

When  the  mkfs  command creates  a  file  system, the  prototype
specification may include a bad  block list for the new file sys-
tem.

***** See Also *****

badscan, commands, icheck, mkfs, umount

















COHERENT Lexicon                                           Page 1

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.