CLRI(8) System Manager's Manual CLRI(8)NAME
clri - clear i-node
clri filesystem i-number ...
Clri writes zeros on the i-nodes with the decimal i-numbers on the filesystem. After clri, any blocks in the affected file will show up as
`missing' in an icheck(8) of 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 for some reason appears in no directory. If it is used to zap an i-node
which does appear in a directory, care should be taken 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. At that point removing the old entry will destroy the new file. The new entry
will again point to an unallocated i-node, so the whole cycle is likely to be repeated again and again.
SEE ALSO fsck(8), icheck(8)BUGS
If the file is open, clri is likely to be ineffective.
Check Out this Related Man Page
clri - clear inode
special i-number ...
The command clears the inode i-number by filling it with zeros. special must be a special file name referring to a device containing a
file system. For proper results, special should not be mounted (see WARNINGS below). After is executed, all blocks in the affected file
show up as "missing" in an of special (see fsck(1M)). This command should only be used in emergencies.
Read and write permission is required on the specified special device. The inode becomes allocatable.
The primary purpose of this command is to remove a file that for some reason does not appear in any directory. If it is used to clear an
inode that does appear in a directory, care should be taken to locate the entry and remove it. Otherwise, when the inode is reallocated to
some new file, the old entry in the directory will still point to that file. At that point, removing the old entry destroys the new file,
causing the new entry to point to an unallocated inode, so the whole cycle is likely to be repeated again.
If the file system is mounted, is likely to be ineffective.
operates only on file systems of type
SEE ALSO fsck(1M), fsdb(1M), ncheck(1M).
clri: SVID2, SVID3
I am trying to create a FS using SVM but system is throwing the following error.
newfs: construct a new file system /dev/md/rdsk/d1002: (y/n)? y
/usr/sbin/clri: can't get execution attributes (1 Reply)
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)
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
bash-2.03# rm "bad/000025;001;1377795616;???"
rm:... (17 Replies)
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.
bash-3.2# cldev status
=== Cluster DID Devices ===
Device Instance ... (8 Replies)
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)
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)
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)