ilookup5(9) [suse man page]

ILOOKUP5(9)							   The Linux VFS						       ILOOKUP5(9)

NAME

       ilookup5 - search for an inode in the inode cache

SYNOPSIS

       struct inode * ilookup5(struct super_block * sb, unsigned long hashval, int (*test) (struct inode *, void *), void * data);

ARGUMENTS

       sb
	   super block of file system to search

       hashval
	   hash value (usually inode number) to search for

       test
	   callback used for comparisons between inodes

       data
	   opaque data pointer to pass to test

DESCRIPTION

       ilookup5 uses ifind to search for the inode specified by hashval and data in the inode cache. This is a generalized version of ilookup for
       file systems where the inode number is not sufficient for unique identification of an inode.

       If the inode is in the cache, the inode lock is waited upon and the inode is returned with an incremented reference count.

       Otherwise NULL is returned.

       Note, test is called with the inode_lock held, so can't sleep.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							       ILOOKUP5(9)

clri(1M)																  clri(1M)

NAME

       clri - clear inode

SYNOPSIS

       special i-number  ...

DESCRIPTION

       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.

WARNINGS

       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.

DEPENDENCIES

       operates only on file systems of type

SEE ALSO

       fsck(1M), fsdb(1M), ncheck(1M).

STANDARDS CONFORMANCE

       clri: SVID2, SVID3

																	  clri(1M)