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

[Kris Kennaway]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031203/73236f24/attachment.bin