From owner-freebsd-questions Mon Jan 27 6:39:20 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CF5837B401 for ; Mon, 27 Jan 2003 06:39:19 -0800 (PST) Received: from mail.adelphia.net (pa-plum1b-166.pit.adelphia.net [24.53.161.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2769F43F13 for ; Mon, 27 Jan 2003 06:39:18 -0800 (PST) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([172.16.0.95]) by mail.adelphia.net (8.12.3/8.12.3) with ESMTP id h0REegiE006704; Mon, 27 Jan 2003 09:40:42 -0500 (EST) (envelope-from wmoran@potentialtech.com) Message-ID: <3E3544CE.9060708@potentialtech.com> Date: Mon, 27 Jan 2003 09:40:14 -0500 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021127 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Banning Cc: questions@freebsd.org Subject: Re: how to fix a botched directory References: <20030127012140.A31400@skytrackercanada.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 David Banning wrote: > I was linking the directory /C to my windows box C drive using shlight, > but now, for an unknown reason the directory is still there, but > is not viewable with ls. I can not re-create it, as the system states > that it exists. Here is the result of some of my commands; > > su-2.03# cd / > su-2.03# ls -ld C > ls: C: Input/output error > su-2.03# mkdir C > mkdir: C: File exists > su-2.03# rm -r C > rm: C: Input/output error > su-2.03# > su-2.03# mv C Z > mv: C: Input/output error > su-2.03# > > Any idea what I can do? There is nothing in the directory so it is > unimportant, but I would like to get this cleared up. Have you had a system crash recently? First, back up you / partition. Then reboot into single user mode and run fsck. See if that helps. (don't run fsck multi-user unless you know what you're doing. You shouldn't run fsck on filesystems that are in use) -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message