Return to icheck CVS log

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

Annotation of coherent/a/usr/man/COHERENT/icheck, revision 1.1

1.1     ! root        1: 
        !             2: 
        !             3: icheck                       Command                       icheck
        !             4: 
        !             5: 
        !             6: 
        !             7: 
        !             8: i-node consistency check
        !             9: 
        !            10: 
        !            11: iicchheecckk [-ss] [-bb _N ...] [ -vv ] _f_i_l_e_s_y_s_t_e_m ...
        !            12: 
        !            13: Each block  in a file  system must be  either free (i.e.,  in the
        !            14: free  list) or  allocated (i.e., associated  with exactly  one i-
        !            15: node).  icheck examines each specified filesystem, printing block
        !            16: numbers that  are claimed by more than one  i-node, or claimed by
        !            17: both an i-node and the free list.  It also checks for blocks that
        !            18: appear more  than once in the  block list of an  i-node or in the
        !            19: free list.
        !            20: 
        !            21: The option -v (verbose) causes icheck to print a summary of block
        !            22: usage in  the filesystem.  The option -s  causes icheck to ignore
        !            23: the free  list, to note which blocks are  claimed by i-nodes, and
        !            24: to rebuild  the free  list with the  remainder.  A list  of block
        !            25: numbers may be submitted with the -b flag; icheck prints the data
        !            26: structure  associated  with  each block  as  the  file system  is
        !            27: scanned.
        !            28: 
        !            29: The raw  device should be used, and the  filesystem should be un-
        !            30: mounted if possible.  If this  is not possible (e.g., on the root
        !            31: file  system) and  the  -s option  is  used, the  system must  be
        !            32: rebooted immediately to expunge the obsolete superblock.
        !            33: 
        !            34: The exit status bits for a bad return are as follows:
        !            35: 
        !            36: 
        !            37:      00xx0011 Miscellaneous error (e.g. out of space)
        !            38:      00xx0022 Too hard to fix without human intervention
        !            39:      00xx0044 Bad free block
        !            40:      00xx0088 Missing blocks
        !            41:      00xx1100 Duplicates in free list
        !            42:      00xx2200 Bad block in free list
        !            43: 
        !            44: 
        !            45: ***** See Also *****
        !            46: 
        !            47: clri, commands, dcheck, fsck, ncheck, sync, umount
        !            48: 
        !            49: ***** Diagnostics *****
        !            50: 
        !            51: The message  ``dups in  free'' indicates a  block is in  the free
        !            52: list more than  once.  ``bad freelist'' indicates the presence of
        !            53: bad blocks  on the free list.   A ``bad'' block is  one that lies
        !            54: outside the  bounds of the  file system.  A  ``dup'' (duplicated)
        !            55: block is one associated with the free list and an i-node, or with
        !            56: more than  one i-node.   All the  errors above must  be corrected
        !            57: before the file system is mounted.  ``bad ifree'' means allocated
        !            58: i-nodes are on the free i-node list; this is inconsequential.
        !            59: 
        !            60: This command has largely been replaced by fsck.
        !            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.