Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jun 2003 13:01:07 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Jaime <jaime@snowmoon.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: bad file descriptor
Message-ID:  <20030617180107.GK64929@dan.emsphone.com>
In-Reply-To: <20030617122415.H96282@malkav.snowmoon.com>
References:  <20030617090348.G94567@malkav.snowmoon.com> <20030617155416.128df944.heikkis@ifi.uio.no> <20030617122415.H96282@malkav.snowmoon.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030617180107.GK64929>