checkpoint of hacking for mail.cs.berkeley.edu
[unix-history] / usr / src / sbin / clri / clri.8
CommitLineData
a89e138e 1.\" Copyright (c) 1980 Regents of the University of California.
37d5dc12 2.\" All rights reserved.
a89e138e 3.\"
37d5dc12
CL
4.\" %sccs.include.proprietary.roff%
5.\"
6.\" @(#)clri.8 6.2 (Berkeley) %G%
a89e138e 7.\"
55cea326 8.TH CLRI 8 ""
a89e138e
KM
9.UC 4
10.SH NAME
11clri \- clear i-node
12.SH SYNOPSIS
13.B /etc/clri
14filesystem i-number ...
15.SH DESCRIPTION
16.B N.B.:
17.I Clri
18is obsoleted for normal file system repair work by
19.IR fsck (8).
20.PP
21.I Clri
22writes zeros on the i-nodes
23with the decimal
24.I i-numbers
25on the
26.I filesystem.
27After
28.I clri,
29any blocks
30in the affected file
31will show up as `missing' in an
0904b7f1 32.IR icheck (8)
a89e138e
KM
33of the
34.I filesystem.
35.PP
36Read and write permission is required on the specified
37file system device.
38The i-node becomes allocatable.
39.PP
40The primary purpose of this routine
41is to remove a file which
42for some reason appears in no
43directory.
44If it is used to zap an i-node
45which does appear in a directory, care should be taken to track down
46the entry and remove it.
47Otherwise, when the i-node is reallocated to some new file,
48the old entry will still point to that file.
49At that point removing the old entry will destroy the new file.
50The new entry will again point to an unallocated i-node,
51so the whole cycle is likely to be repeated again and again.
52.SH "SEE ALSO"
53icheck(8)
54.SH BUGS
55If the file is open,
56.I clri
57is likely to be ineffective.