https://gunkies.org/index.php?action=history&feed=atom&title=32v_1m_clri 2026-05-18T03:08:15Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=32v_1m_clri&diff=6941&oldid=prev 2009-10-26T13:18:34Z

<p>New page: CLRI(1M) UNIX Programmer&#039;s Manual CLRI(1M) == NAME == clri - clear i-node == SYNOPSIS == clri filesystem i-number ... == DESCRIPTION == _C_l_r_i ...</p> <p><b>New page</b></p><div>CLRI(1M) UNIX Programmer's Manual CLRI(1M)<br /> <br /> <br /> <br /> == NAME ==<br /> clri - clear i-node<br /> <br /> == SYNOPSIS ==<br /> clri filesystem i-number ...<br /> <br /> == DESCRIPTION ==<br /> _C_l_r_i writes zeros on the i-nodes with the decimal _i-_n_u_m_b_e_r_s<br /> on the _f_i_l_e_s_y_s_t_e_m. After _c_l_r_i, any blocks in the affected<br /> file will show up as `missing' in an _i_c_h_e_c_k(1) of the<br /> _f_i_l_e_s_y_s_t_e_m.<br /> <br /> Read and write permission is required on the specified file<br /> system device. The i-node becomes allocatable.<br /> <br /> The primary purpose of this routine is to remove a file<br /> which for some reason appears in no directory. If it is<br /> used to zap an i-node which does appear in a directory, care<br /> should be taken to track down the entry and remove it. Oth-<br /> erwise, when the i-node is reallocated to some new file, the<br /> old entry will still point to that file. At that point<br /> removing the old entry will destroy the new file. The new<br /> entry will again point to an unallocated i-node, so the<br /> whole cycle is likely to be repeated again and again.<br /> <br /> == SEE ALSO ==<br /> [[32v 1m icheck|icheck(1)]]<br /> <br /> == BUGS ==<br /> If the file is open, _c_l_r_i is likely to be ineffective.<br /> <br /> [[Category:32v man section 1]]</div>

Neozeed