Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jan 2003 09:40:14 -0500
From:      Bill Moran <wmoran@potentialtech.com>
To:        David Banning <david@skytracker.ca>
Cc:        questions@freebsd.org
Subject:   Re: how to fix a botched directory
Message-ID:  <3E3544CE.9060708@potentialtech.com>
References:  <20030127012140.A31400@skytrackercanada.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E3544CE.9060708>