https://gunkies.org/index.php?action=history&feed=atom&title=32v_1m_icheck 2026-05-06T04:51:25Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=32v_1m_icheck&diff=6971&oldid=prev 2009-10-26T14:17:15Z

<p>New page: ICHECK(1M) UNIX Programmer&#039;s Manual ICHECK(1M) == NAME == icheck - file system storage consistency check == SYNOPSIS == icheck [ -s ] [ -b numbers ] [ fil...</p> <p><b>New page</b></p><div>ICHECK(1M) UNIX Programmer's Manual ICHECK(1M)<br /> <br /> <br /> <br /> == NAME ==<br /> icheck - file system storage consistency check<br /> <br /> == SYNOPSIS ==<br /> icheck [ -s ] [ -b numbers ] [ filesystem ]<br /> <br /> == DESCRIPTION ==<br /> _I_c_h_e_c_k examines a file system, builds a bit map of used<br /> blocks, and compares this bit map against the free list<br /> maintained on the file system. If the file system is not<br /> specified, a set of default file systems is checked. The<br /> normal output of _i_c_h_e_c_k includes a report of<br /> <br /> The total number of files and the numbers of regular,<br /> directory, block special and character special files.<br /> <br /> The total number of blocks in use and the numbers of<br /> single-, double-, and triple-indirect blocks and direc-<br /> tory blocks.<br /> <br /> The number of free blocks.<br /> <br /> The number of blocks missing; i.e. not in any file nor<br /> in the free list.<br /> <br /> The -s option causes _i_c_h_e_c_k to ignore the actual free list<br /> and reconstruct a new one by rewriting the super-block of<br /> the file system. The file system should be dismounted while<br /> this is done; if this is not possible (for example if the<br /> root file system has to be salvaged) care should be taken<br /> that the system is quiescent and that it is rebooted immedi-<br /> ately afterwards so that the old, bad in-core copy of the<br /> super-block will not continue to be used. Notice also that<br /> the words in the super-block which indicate the size of the<br /> free list and of the i-list are believed. If the super-<br /> block has been curdled these words will have to be patched.<br /> The -s option causes the normal output reports to be<br /> suppressed.<br /> <br /> Following the -b option is a list of block numbers; whenever<br /> any of the named blocks turns up in a file, a diagnostic is<br /> produced.<br /> <br /> _I_c_h_e_c_k is faster if the raw version of the special file is<br /> used, since it reads the i-list many blocks at a time.<br /> <br /> == FILES ==<br /> Default file systems vary with installation.<br /> <br /> == SEE ALSO ==<br /> [[32v 1m dcheck|dcheck(1)]], [[32v 1m ncheck|ncheck(1)]], [[32v 5m filsys|filsys(5)]], [[32v 1m clri|clri(1)]]<br /> <br /> == DIAGNOSTICS ==<br /> For duplicate blocks and bad blocks (which lie outside the<br /> file system) _i_c_h_e_c_k announces the difficulty, the i-number,<br /> and the kind of block involved. If a read error is encoun-<br /> tered, the block number of the bad block is printed and<br /> _i_c_h_e_c_k considers it to contain 0. `Bad freeblock' means<br /> that a block number outside the available space was encoun-<br /> tered in the free list. `_n dups in free' means that _n<br /> blocks were found in the free list which duplicate blocks<br /> either in some file or in the earlier part of the free list.<br /> <br /> == BUGS ==<br /> Since _i_c_h_e_c_k is inherently two-pass in nature, extraneous<br /> diagnostics may be produced if applied to active file sys-<br /> tems.<br /> It believes even preposterous super-blocks and consequently<br /> can get core images.<br /> <br /> [[Category:32v man section 1]]</div>

Neozeed