Commit | Line | Data |
---|---|---|
e6817382 BJ |
1 | .TH CLRI 1M |
2 | .SH NAME | |
3 | clri \- clear i-node | |
4 | .SH SYNOPSIS | |
5 | .B clri | |
6 | filesystem i-number ... | |
7 | .SH DESCRIPTION | |
8 | .I Clri | |
9 | writes zeros on the i-nodes | |
10 | with the decimal | |
11 | .I i-numbers | |
12 | on the | |
13 | .I filesystem. | |
14 | After | |
15 | .I clri, | |
16 | any blocks | |
17 | in the affected file | |
18 | will show up as `missing' in an | |
19 | .IR icheck (1) | |
20 | of the | |
21 | .I filesystem. | |
22 | .PP | |
23 | Read and write permission is required on the specified | |
24 | file system device. | |
25 | The i-node becomes allocatable. | |
26 | .PP | |
27 | The primary purpose of this routine | |
28 | is to remove a file which | |
29 | for some reason appears in no | |
30 | directory. | |
31 | If it is used to zap an i-node | |
32 | which does appear in a directory, care should be taken to track down | |
33 | the entry and remove it. | |
34 | Otherwise, when the i-node is reallocated to some new file, | |
35 | the old entry will still point to that file. | |
36 | At that point removing the old entry will destroy the new file. | |
37 | The new entry will again point to an unallocated i-node, | |
38 | so the whole cycle is likely to be repeated again and again. | |
39 | .SH "SEE ALSO" | |
40 | icheck(1) | |
41 | .SH BUGS | |
42 | If the file is open, | |
43 | .I clri | |
44 | is likely to be ineffective. |