From owner-freebsd-questions Sun Jan 13 11:39:32 2002 Delivered-To: freebsd-questions@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 32D7D37B417 for ; Sun, 13 Jan 2002 11:39:28 -0800 (PST) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id g0DJdOl18129; Sun, 13 Jan 2002 14:39:24 -0500 (EST) Date: Sun, 13 Jan 2002 14:39:24 -0500 (EST) From: Zhihui Zhang X-Sender: zzhang@opal To: "Klaus-J. Wolf" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Bad file descriptor In-Reply-To: <20020112133523.A16609@coelis.nacamar.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. -Zhihui 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". > > How can I get rid of that trash? Can somebody please make fsck fit for > purging it? > > Regards, > k.j. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message