make_bad_inode(9) [centos man page]

MAKE_BAD_INODE(9)						   The Linux VFS						 MAKE_BAD_INODE(9)

NAME

       make_bad_inode - mark an inode bad due to an I/O error

SYNOPSIS

       void make_bad_inode(struct inode * inode);

ARGUMENTS

       inode
	   Inode to mark bad

DESCRIPTION

       When an inode cannot be read due to a media or remote network failure this function makes the inode "bad" and causes I/O operations on it
       to fail from this point on.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							 MAKE_BAD_INODE(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)