Sponsored Content
Full Discussion: what is this
Top Forums UNIX for Dummies Questions & Answers what is this Post 7614 by Perderabo on Friday 28th of September 2001 08:57:31 AM
Old 09-28-2001
I would suspect a damaged filesystem possibly caused by incorrect use of the clri command. I would make a tape backup of this filesystem pronto. Then I would umount the filesystem and try a manual fsck. If that doesn't work, the next step would be rebuilding the filesystem.
 
CLRI(8) 						    BSD System Manager's Manual 						   CLRI(8)

NAME
clri -- clear an inode SYNOPSIS
clri special_device inode_number ... DESCRIPTION
Clri is obsoleted for normal file system repair work by fsck(8). Clri zeros out the inodes with the specified inode number(s) on the filesystem residing on the given special_device. The fsck(8) utility is usually run after clri to reclaim the zero'ed inode(s) and the blocks previously claimed by those inode(s). Both read and write permission are required on the specified special_device. The primary purpose of this routine is to remove a file which for some reason is not being properly handled by fsck(8). Once removed, it is anticipated that fsck(8) will be able to clean up the resulting mess. SEE ALSO
fsck(8), fsdb(8), icheck(8), ncheck(8) BUGS
If the file is open, the work of clri will be lost when the inode is written back to disk from the inode cache. 4th Berkeley Distribution April 19, 1994 4th Berkeley Distribution
All times are GMT -4. The time now is 01:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy