From owner-freebsd-questions@FreeBSD.ORG Tue Jun 17 11:01:11 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E4E337B421 for ; Tue, 17 Jun 2003 11:01:11 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E33A43F75 for ; Tue, 17 Jun 2003 11:01:10 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h5HI17ph012220; Tue, 17 Jun 2003 13:01:07 -0500 (CDT) (envelope-from dan) Date: Tue, 17 Jun 2003 13:01:07 -0500 From: Dan Nelson To: Jaime Message-ID: <20030617180107.GK64929@dan.emsphone.com> References: <20030617090348.G94567@malkav.snowmoon.com> <20030617155416.128df944.heikkis@ifi.uio.no> <20030617122415.H96282@malkav.snowmoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030617122415.H96282@malkav.snowmoon.com> X-OS: FreeBSD 5.1-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: heikki soerum cc: freebsd-questions@freebsd.org Subject: Re: bad file descriptor X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 18:01:11 -0000 In the last episode (Jun 17), Jaime said: > On Tue, 17 Jun 2003, heikki soerum wrote: > > > zeus# rm "#pico29506#" > > > rm: #pico29506#: Bad file descriptor > > > zeus# whoami > > > root > > > > # is usually an special character, I usually delete such files with > > Midnight Commander (mc shell), another possibility might be to not use > > "" but rather use an \ backslash before every special character. > > I tried that first. That didn't work, either. :( "Bad file descriptor" when trying to access a file usually means filesystem corruption. A fsck run should delete it, and if it doesn't you can use the clri command to zap the inode (dismount the filesystem first) then run fsck. -- Dan Nelson dnelson@allantgroup.com