From owner-freebsd-questions  Fri Mar 21 17:53:39 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA02074
          for questions-outgoing; Fri, 21 Mar 1997 17:53:39 -0800 (PST)
Received: from train.tgci.com ([205.185.169.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA02069
          for <questions@freebsd.org>; Fri, 21 Mar 1997 17:53:35 -0800 (PST)
Received: from emilyd ([206.250.85.68]) by train.tgci.com (8.6.12/8.6.9) with SMTP id SAA18190; Fri, 21 Mar 1997 18:03:46 -0800
Message-Id: <199703220203.SAA18190@train.tgci.com>
Comments: Authenticated sender is <chaos@mail.tgci.com>
From: "Riley J. McIntire" <chaos@mail.tgci.com>
To: Kenneth Ingham <ingham@i-pi.com>
Date: Fri, 21 Mar 1997 17:52:04 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Bad file descriptor in security check output
Reply-to: chaos@tgci.com
CC: questions@freebsd.org
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.42a)
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I tried this:

bash# clri /dev/wd0 64456
clri: /dev/wd0: superblock magic number 0xce0038, not 0x11954.

Trying  /dev/rwd0a etc produced a device busy error.  

The directory still looks like:

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-xrw-r--  25902 96561670    9742848     101, 1768161394 May 26  1970 #064513
bash#

Cheers,

Riley


> From:          Kenneth Ingham <ingham@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

> 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
> 
>