From owner-freebsd-current@FreeBSD.ORG Wed Dec 3 03:43:16 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 C942916A4CE for ; Wed, 3 Dec 2003 03:43:16 -0800 (PST) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B5F243FE5 for ; Wed, 3 Dec 2003 03:43:15 -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 oxefoaaa for freebsd-current@freebsd.org; Wed, 3 Dec 2003 13:43:11 +0200 Message-ID: <3FCDCC7D.5020306@ofw.fi> Date: Wed, 03 Dec 2003 13:43:57 +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: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AuthenticatedSender: dan.naumov@ofw.fi Subject: 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 11:43:16 -0000 Hello What follows is a description of a problem I used to have when running FreeBSD 5.0 and 5.1. I am not running FreeBSD right now, but I am considering going back to it but I need to figure out how to prevent this issue from happening again. My system has 2 harddrives, a 16 GB Seagate that I use for backups and mount it under /mnt/backup and a 40 GB Maxtor that I am using for everything else. After the installation of the OS (usually about 8-12 days of running non-stop) I start getting "Bad File Descriptor" errors on random files all around the Maxtor drive and I have to go to single-user mode in order to run a full fsck on the system. After that, the system works, until in 8-12 days time even more files get "corrupted" this way and the process has to be repeated. Eventually, so many files are damaged that a full OS reinstall is required. Now if not for a few things, I'd probably come to the conclusion that my Maxtor HD is dying on me as my Seagate drive isn't causing me any headaches. However this doesn't seem to be the case, as if Linux (EXT3) or Windows (NTFS) are used, no data loss ever occurs even if the system is left running for many weeks in a row. Now what exactly could be causing this bizarre behavior ? If this is of any help, the exact model number of the HD is "MAXTOR 4K040H2" and I was using UFS2 on both drives. Thanks in advance. Sincerely, Dan Naumov