clri(1M)							      clri(1M)

NAME    [Toc]    [Back]

     clri - clear EFS inode

SYNOPSIS    [Toc]    [Back]

     clri special i-number ...

DESCRIPTION    [Toc]    [Back]

     clri writes nulls on the inode table entry	for i-number.  This
     effectively eliminates the	inode at that address.	special	is the device
     name on which an EFS filesystem has been defined.	After clri is
     executed, any blocks in the affected file shows up	as ``not accounted
     for'' when	fsck(1M) is run	against	the filesystem.	 The inode can be
     allocated to a new	file.

     Read and write permission is required on the specified special device.

     This command is used to remove a file that	appears	in no directory, that
     is, to get	rid of a file that cannot be removed with the rm command.

SEE ALSO    [Toc]    [Back]

     findblk(1M), fsck(1M), fsdb(1M), ncheck(1M), rm(1), efs(4).

WARNINGS    [Toc]    [Back]

     If	the file is open for writing, clri does	not work.  The filesystem
     containing	the file should	not be mounted.

     If	clri is	used on	the inode number of a file that	does appear in a
     directory,	it is imperative to remove the entry in	the directory at once,
     since the inode can be allocated to a new file.  The old directory	entry,
     if	not removed, continues to point	to the same file.  This	sounds like a
     link but does not work like one.  Removing	the old	entry destroys the new
     file.

     There is no equivalent command for	XFS filesystems.  If clri is applied
     to	an XFS filesystem, the messages:
	  bad superblock magic number in /dev/rdsk/dksxxx
	  clri:	/dev/dsk/dksxxx	is not an extent filesystem
     will appear.


									PPPPaaaaggggeeee 1111