From owner-freebsd-questions Sun Jan 20 4:28:46 2002 Delivered-To: freebsd-questions@freebsd.org Received: from acutiator.nacamar.de (mxa.tiscali.de [194.162.162.215]) by hub.freebsd.org (Postfix) with ESMTP id 971A137B419 for ; Sun, 20 Jan 2002 04:28:42 -0800 (PST) Received: from coelis.nacamar.de (coelis.nacamar.de [195.63.228.175]) by acutiator.nacamar.de (Postfix) with ESMTP id 39AF55D01; Sun, 20 Jan 2002 13:28:39 +0100 (CET) Received: (from kjwolf@localhost) by coelis.nacamar.de (8.11.6/8.11.2) id g0KCTaF42925; Sun, 20 Jan 2002 13:29:36 +0100 (CET) (envelope-from klaus-juergen.wolf@de.tiscali.com) Date: Sun, 20 Jan 2002 13:29:36 +0100 From: "Klaus-J. Wolf" To: freebsd-questions@freebsd.org Cc: zzhang@cs.binghamton.edu Subject: Re: Bad file descriptor Message-ID: <20020120132936.A42921@coelis.nacamar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Tiscali Business GmbH Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Do you mean that you can not open those files even after you have run > fsck > successfully? If so, then fsck can not correct all corruptions. Hi, yes, in fact I did. fsck didn't complain about the concerned files. Only that you couldn't open or delete them. Regards, k.j. > On Sat, 12 Jan 2002, Klaus-J. Wolf wrote: > > > Hi, > > > it has happened to me several times: a machine crashes and > somewhere in > > the file system you'll find some trash afterwards which seems to be > > resistant against fsck: a file which you cannot open because the > system > > tells you: "bad file descriptor". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message