From owner-freebsd-current@FreeBSD.ORG Wed Dec 3 10:52:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FB2316A4CE for ; Wed, 3 Dec 2003 10:52:46 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5966843F85 for ; Wed, 3 Dec 2003 10:52:45 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C718166C55; Wed, 3 Dec 2003 10:52:44 -0800 (PST) Date: Wed, 3 Dec 2003 10:52:44 -0800 From: Kris Kennaway To: Dan Naumov Message-ID: <20031203185244.GA66730@xor.obsecurity.org> References: <3FCDCC7D.5020306@ofw.fi> <20031203141959.GD61570@xor.obsecurity.org> <3FCE0771.1040602@ofw.fi> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <3FCE0771.1040602@ofw.fi> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Kris Kennaway Subject: Re: FreeBSD 5.x and "Bad File Descriptor" errors. Why? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 18:52:46 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 03, 2003 at 05:55:29PM +0200, Dan Naumov wrote: > Kris Kennaway wrote >=20 > >You get that error from what command(s)? Have you tried with 5.2, > >which has a new ATA driver? > > > >Kris > >=20 > > > I usually "discover" that I am having data corruption when trying to=20 > update ports. A file that has a "Bad File Descriptor" refuses to let=20 > cvsup overwrite and/or remove itself. I've also had "make installworld"= =20 > fail on me for the very same reason. A file in the base system would get= =20 > corrupted and would prevent anything from overwriting itself. These=20 > problems would go away after a full system fsck, but the fsck would=20 > remove the damaged files completely, sometimes leaving the system in a=20 > severely broken state. And even if it did not, data corruption would=20 > 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 --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/zjD8Wry0BWjoQKURAhltAJ97ZS81S5CnKE1Ze6LfX7Fc2PltRwCgojiT Ey4LGpd5tH9iVTDNcPDQPew= =z090 -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v--