From owner-freebsd-current@FreeBSD.ORG Wed Dec 3 07:54: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 2076816A4CE for ; Wed, 3 Dec 2003 07:54:46 -0800 (PST) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9782943FBF for ; Wed, 3 Dec 2003 07:54:44 -0800 (PST) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id rejfoaaa for freebsd-current@freebsd.org; Wed, 3 Dec 2003 17:54:43 +0200 Message-ID: <3FCE0771.1040602@ofw.fi> Date: Wed, 03 Dec 2003 17:55:29 +0200 From: Dan Naumov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031110 Thunderbird/0.4a X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <3FCDCC7D.5020306@ofw.fi> <20031203141959.GD61570@xor.obsecurity.org> In-Reply-To: <20031203141959.GD61570@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AuthenticatedSender: dan.naumov@ofw.fi cc: freebsd-current@freebsd.org 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 15:54:46 -0000 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. Sincerely, Dan Naumov