From owner-freebsd-questions  Fri Mar 21 14:35:09 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA17673
          for questions-outgoing; Fri, 21 Mar 1997 14:35:09 -0800 (PST)
Received: from cube.i-pi.com (cube.i-pi.com [198.49.217.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA17662
          for <questions@freebsd.org>; Fri, 21 Mar 1997 14:35:05 -0800 (PST)
Received: (from ingham@localhost) by cube.i-pi.com (8.6.12/8.6.12) id PAA18693; Fri, 21 Mar 1997 15:34:58 -0700
From: Kenneth Ingham <ingham@i-pi.com>
Message-Id: <199703212234.PAA18693@cube.i-pi.com>
Subject: Re: Bad file descriptor in security check output
To: chaos@tgci.com
Date: Fri, 21 Mar 1997 15:34:57 -0700 (MST)
Cc: questions@freebsd.org
In-Reply-To: <199703212027.MAA16837@train.tgci.com> from "Riley J. McIntire" at Mar 21, 97 12:15:27 pm
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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