Unix and Linux Discussions Tagged with inode |
|
Thread / Thread Starter |
Last Post |
Replies |
Views |
Forum |
|
|
|
4 |
1,619 |
UNIX for Advanced & Expert Users |
|
|
|
1 |
11,433 |
UNIX for Dummies Questions & Answers |
|
|
|
3 |
6,799 |
UNIX for Dummies Questions & Answers |
|
|
|
4 |
10,608 |
UNIX for Advanced & Expert Users |
|
|
|
3 |
4,482 |
Shell Programming and Scripting |
|
|
|
9 |
13,130 |
Red Hat |
|
|
|
4 |
6,299 |
UNIX for Dummies Questions & Answers |
|
|
|
7 |
11,144 |
Shell Programming and Scripting |
|
|
|
6 |
14,731 |
AIX |
|
|
|
1 |
7,706 |
UNIX for Advanced & Expert Users |
|
|
|
1 |
4,719 |
Solaris |
|
|
|
0 |
5,490 |
Filesystems, Disks and Memory |
|
|
|
2 |
6,441 |
UNIX for Dummies Questions & Answers |
|
|
|
2 |
4,059 |
UNIX for Dummies Questions & Answers |
|
|
|
2 |
3,534 |
UNIX for Dummies Questions & Answers |
|
|
|
7 |
45,437 |
Solaris |
|
|
|
7 |
24,778 |
UNIX for Advanced & Expert Users |
|
|
|
4 |
9,888 |
Solaris |
|
|
|
3 |
14,510 |
Linux |
|
|
|
3 |
11,706 |
Solaris |
|
|
|
1 |
4,228 |
Ubuntu |
|
|
|
2 |
5,450 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
6,010 |
UNIX for Dummies Questions & Answers |
|
|
|
0 |
7,596 |
Solaris |
|
|
|
1 |
9,173 |
AIX |
|
|
|
3 |
6,564 |
Linux |
|
|
|
3 |
6,940 |
UNIX for Dummies Questions & Answers |
|
|
|
0 |
9,742 |
UNIX for Advanced & Expert Users |
|
|
|
3 |
8,390 |
Solaris |
|
|
|
5 |
15,009 |
Linux |
|
|
|
2 |
2,487 |
UNIX for Advanced & Expert Users |
|
|
|
5 |
26,777 |
UNIX for Dummies Questions & Answers |
|
|
|
4 |
7,184 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
7,606 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
5,016 |
Programming |
|
|
|
2 |
10,453 |
UNIX for Dummies Questions & Answers |
|
|
|
4 |
35,794 |
UNIX for Dummies Questions & Answers |
CLRI(8) BSD System Manager's Manual CLRI(8)
NAME
clri -- clear an inode
SYNOPSIS
clri special_device inode_number ...
DESCRIPTION
Clri is obsoleted for normal file system repair work by fsck(8).
Clri zeros out the inodes with the specified inode number(s) on the filesystem residing on the given special_device. The fsck(8) utility is
usually run after clri to reclaim the zero'ed inode(s) and the blocks previously claimed by those inode(s). Both read and write permission
are required on the specified special_device.
The primary purpose of this routine is to remove a file which for some reason is not being properly handled by fsck(8). Once removed, it is
anticipated that fsck(8) will be able to clean up the resulting mess.
SEE ALSO
fsck(8), fsdb(8), icheck(8), ncheck(8)
BUGS
If the file is open, the work of clri will be lost when the inode is written back to disk from the inode cache.
4th Berkeley Distribution April 19, 1994 4th Berkeley Distribution