Date: Fri, 21 Mar 1997 15:34:57 -0700 (MST) From: Kenneth Ingham <ingham@i-pi.com> To: chaos@tgci.com Cc: questions@freebsd.org Subject: Re: Bad file descriptor in security check output Message-ID: <199703212234.PAA18693@cube.i-pi.com> In-Reply-To: <199703212027.MAA16837@train.tgci.com> from "Riley J. McIntire" at Mar 21, 97 12:15:27 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Here's a solution, but it is somewhat drastic, and should be approached
with caution. Please read the man page clri before doing this.
take your system to single user.
Note the device which contains the bad files.
cd to the lost+found dir
do a ls -i
Note the inode numbers of the offending files (they should be the same
as the numbered part of the file name).
type:
clri device inode1 inode2 ...
where device is the device containing the files, and inode1, inode2, etc
are the various inode numbers.
run fsck on the filesystem. Expect to have to say 'y' to a few
questions.
Kenneth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703212234.PAA18693>