Re: FreeBSD 5.x and "Bad File Descriptor" errors. Why?

From: Kris Kennaway <kris_at_obsecurity.org>
Date: Wed, 3 Dec 2003 10:52:44 -0800
On Wed, Dec 03, 2003 at 05:55:29PM +0200, Dan Naumov wrote:
> Kris Kennaway wrote
> 
> >You get that error from what command(s)?  Have you tried with 5.2,
> >which has a new ATA driver?
> >
> >Kris
> > 
> >
> I usually "discover" that I am having data corruption when trying to 
> update ports. A file that has a "Bad File Descriptor" refuses to let 
> cvsup overwrite and/or remove itself. I've also had "make installworld" 
> fail on me for the very same reason. A file in the base system would get 
> corrupted and would prevent anything from overwriting itself. These 
> problems would go away after a full system fsck, but the fsck would 
> remove the damaged files completely, sometimes leaving the system in a 
> severely broken state. And even if it did not, data corruption would 
> happen again in 8-12 days.

Are there any other console or system messages logged?  It sounds like
there should be some other error reported by the kernel before the
userland command receives the EBADF.

Kris

Received on Wed Dec 03 2003 - 09:52:46 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:32 UTC