From owner-freebsd-questions  Thu Mar 20 14:31:43 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA02344
          for questions-outgoing; Thu, 20 Mar 1997 14:31:43 -0800 (PST)
Received: from charmed.wilshire.net ([206.250.85.80])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA02324
          for <freebsd-questions@FreeBSD.ORG>; Thu, 20 Mar 1997 14:31:40 -0800 (PST)
Received: from EMILYD ([206.250.85.68]) by charmed.wilshire.net (8.8.5/8.8.3) with SMTP id OAA15384 for <freebsd-questions@FreeBSD.ORG>; Thu, 20 Mar 1997 14:35:35 -0800 (PST)
Received: by EMILYD with Microsoft Mail
	id <01BC353B.69A2A2A0@EMILYD>; Thu, 20 Mar 1997 14:31:35 -0800
Message-ID: <01BC353B.69A2A2A0@EMILYD>
From: "Riley J. McIntire" <rjmcintire@earthlink.net>
To: "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG>
Subject: RE: Bad file descriptor in security check output
Date: Thu, 20 Mar 1997 14:31:33 -0800
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

When I try to remove these files I get this:

bash# rm -i '#'06*
rm: #064448: Bad file descriptor
remove #064456? y
rm: #064456: Operation not permitted
remove #064504? y
rm: #064504: Operation not permitted
remove #064505? y
rm: #064505: Operation not permitted
remove #064513? y
rm: #064513: Operation not permitted
bash# ls -l
ls: #064448: Bad file descriptor
total 0
cr-srwsrwT  21077 57982986    2315373696  219, -2097151869 Nov 11  1975 #064456
br-srwSrwt  27506 1845521775  1869640805  116, 1819213941 Nov  4 11:56 #064504
br-xrws---  29440 1996515182  1735094895    0, 1380974628 Dec 12 16:53 #064505
br-xrw-r--  25902 96561670    9742848     101, 1768161394 May 26  1970 #064513

Trying chmod I get the same errors...

Thanks,

Riley




----------
From: 	Doug White
Sent: 	Thursday, March 20, 1997 1:45 PM
To: 	rjmcintire@wilshire.net
Cc: 	freebsd-questions@FreeBSD.ORG
Subject: 	Re: Bad file descriptor in security check output

On Wed, 19 Mar 1997, Riley J. McIntire wrote:
> some info on troubleshooting this?
.
.
.

These are recovered inodes from a bad crash and were recovered by fsck.
If the files are usable to you, then you can rename them; otherwise
they're probably useless and you should remove them.

.
.
.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major