clri(1M)                                                 clri(1M)



NAME
     clri - clears inodes

SYNOPSIS
     clri [-Tfile-system-type] file-system i-number...

ARGUMENTS
     file-system
          Specifies a special file name referring to a device
          containing a file system.

     i-number
          Specifies the inode that is to be cleared.

     -Tfile-system-type
          Specifies the file-system type, such as 4.2 or 5.2.  If
          this option is not used, clri attempts to determine the
          file-system type.

DESCRIPTION
     clri zeros (clears) the inode numbered i-number and
     increments the inode generation count.  After clri is
     executed, any blocks in the affected file show up as
     ``missing'' in an fsck(1M) of the file-system.  This command
     should only be used in emergencies, and extreme care should
     be exercised.

     Read and write permission is required on the specified
     file-system device.  The inode becomes allocatable.

     The primary purpose of this command 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.

EXAMPLES
     The command:

        clri /dev/rdsk/c0d0s0 65

     where /dev/rdsk/c0d0s0 is a legitimate file system and 65 is
     the inode number to be cleared.

WARNINGS
     This command should be used with caution.





January 1992                                                    1

clri(1M)                                                 clri(1M)



LIMITATIONS
     If the file is open, clri is likely to be ineffective.

FILES
     /etc/clri
          Executable file

SEE ALSO
     fsck(1M), fsdb(1M), ncheck(1M)

     fstyp(3), fs(4) in A/UX Programmer's Reference












































2                                                    January 1992