Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

clri(8) [osf1 man page]

clri(8) 						      System Manager's Manual							   clri(8)

NAME
clri - Clears i-nodes SYNOPSIS
/usr/sbin/clri filesystem i-number ... DESCRIPTION
The clri command is obsoleted for normal file system repair work by the fsck command. The clri command writes zeros on the i-nodes with the decimal i-numbers on the specified filesystem. After clri has finished its work, any blocks in the affected file are defined as "missing" when you run icheck on the filesystem. Read and write permission is required on the specified file system device. The i-node becomes allocatable. The primary purpose of this routine is to remove a file which does not appear in any directory. If you use the command to remove an i-node which does appear in a directory, take care to track down the entry and remove it. Otherwise, when the i-node is reallocated to some new file, the old entry will still point to that file. If you then remove the old entry, you will destroy the new file, and the new entry will again point to an unallocated i-node. Consequently, the entire cycle repeats itself. You must be root to use this command. If the file is open, clri is likely to be ineffective. FILES
Specifies the command path RELATED INFORMATION
Commands: icheck(8) delim off clri(8)

Check Out this Related Man Page

clri(1M)						  System Administration Commands						  clri(1M)

NAME
clri, dcopy - clear inode SYNOPSIS
clri [-F FSType] [-V] special i-number dcopy [-F FSType] [-V] special i-number DESCRIPTION
clri writes zeros on the inodes with the decimal i-number on the file system stored on special. After clri, any blocks in the affected file show up as missing in an fsck(1M) of special. Read and write permission is required on the specified file system device. The inode becomes allocatable. The primary purpose of this routine is to remove a file that for some reason appears in no directory. If it is used to zap an inode that does appear in a directory, care should be taken to track down the entry and remove it. Otherwise, when the inode is reallocated to some new file, the old entry will still point to that file. At that point, removing the old entry will destroy the new file. The new entry will again point to an unallocated inode, so the whole cycle is likely to be repeated again and again. dcopy is a symbolic link to clri. OPTIONS
-F FSType Specify the FSType on which to operate. The FSType should either be specified here or be determinable from /etc/vfstab by matching special with an entry in the table, or by consulting /etc/default/fs. -V Echo the complete command line, but do not execute the command. The command line is generated by using the options and argu- ments provided by the user and adding to them information derived from /etc/vfstab. This option should be used to verify and validate the command line. USAGE
See largefile(5) for the description of the behavior of clri and dcopy when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes). FILES
/etc/default/fs Default local file system type /etc/vfstab List of default parameters for each file system ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
fsck(1M), vfstab(4), attributes(5), largefile(5) NOTES
This command might not be supported for all FSTypes. SunOS 5.11 16 Sep 1996 clri(1M)
Man Page

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Help with can't get execution attributes

Hi Gurus, I am trying to create a FS using SVM but system is throwing the following error. newfs /dev/md/rdsk/d1002 newfs: construct a new file system /dev/md/rdsk/d1002: (y/n)? y /usr/sbin/clri: can't get execution attributes (1 Reply)
Discussion started by: rama krishna
1 Replies

2. Tips and Tutorials

How to manage file names with special characters

One of the common questions asked are: how do i remove/move/rename files with special (non-printable) characters in their name? "Special" doesn't always mean the same. As there are more and less special characters, some solutions are presented, ranging from simple to very complicated. Usually a... (0 Replies)
Discussion started by: bakunin
0 Replies

3. UNIX for Dummies Questions & Answers

Problems removing files with semicolons in the filename

There are some 40 files created by accident with filenames with semicolons, as well as other non-printable characters. I can not find a correct way to delete them. This is what I tried: bash-2.03# ls bad|head -1 000025;001;1377795616;ű bash-2.03# rm "bad/000025;001;1377795616;???" rm:... (17 Replies)
Discussion started by: migurus
17 Replies

4. Solaris

Modifying properties to use scsi-3 reservation for disks with two paths in sun cluster

Hi I am having two node cluster. I was trying to change the to use scsi3 reservation for all disks having two paths. Please let me know where I went wrong or there any issue to implement the same. On node1 bash-3.2# cldev status === Cluster DID Devices === Device Instance ... (8 Replies)
Discussion started by: sb200
8 Replies

5. UNIX for Beginners Questions & Answers

Can't delete a file in the trash on OSX 10.11.6

I use a Mac running OSX El Capitan = UNIX user the hood. After rearranging files on an external hard drive, I ended up with a folder in the trash containing a file called "~INITPicker 2.0". I cannot empty the trash, and so delete the file. I even tried terminal, using the rm file command and... (38 Replies)
Discussion started by: djfilms
38 Replies

6. OS X (Apple)

Undeletable file

Greetings, I'm trying to delete a file with a weird name from within Terminal on a Mac. It's a very old file (1992) with null characters in the name: “␀␀Word FinderÂŽ Plus™”. Here are some examples of what I've tried: 12FX009:5 dpontius$ ls ␀␀Word FinderÂŽ Plus™ 12FX009:5 dpontius$ rm... (29 Replies)
Discussion started by: dpontius
29 Replies

7. Solaris

Root user not recognizing on Solaris-10 (shadow file corruption)

Hello, I got into a wired state on one of solaris 10 server. When I noticed that server is having some issue, I found that there were dumpadm.conf entries in /etc/shadow and real entries were wiped of. Probably somebody fat fingers. I was able to boot into failsafe, break SVM mirror, copied... (25 Replies)
Discussion started by: solaris_1977
25 Replies