The problem with my / directory was cleared up by
rebooting. It seems to have been caused by someone mounting a
directory on "/." but I'm not sure how this was done. Kudos to Henry
Katz and Mike Stromski for figuring this out, and suggesting it might
have been tfs (translucent file system).
Other suggestions included dump & restore, making sure ls
wasn't corrupted, a permissions problem on /, and the possibility that
most things had been moved to /lost+found.
hkatz@nucmed.NYU.EDU (Henry Katz)
email@example.com (Perry Hutchison)
firstname.lastname@example.org (Celeste Stokely)
Dan Stromberg - OAC-DCS <email@example.com>
kmah@DCS-Systems.COM (Kevin Mah)
firstname.lastname@example.org (Mike Stromski)
> I have a problem with the root directory of a 4/260 running
>4.1.1. Essentially, the root directory is foobar. I'm not sure how
>to better describe this.
>cd / ; ls gets:
>extr not found
>06372700 not found
>joachim not found
>while ls / returns normal looking results, but a trace of ls -l finds
>that the command stops on an nfs mounted file system and waits. I can
>umount the file system, and get a message /lefort not mounted.
>links that traverse the rootfs, like /etc/termcap -> ../usr/lib/tercap
>are not followed, but I can cd to /usr/lib, or to /etc.
>fsck now runs cleanly.
>I'm really not sure of how to proceed in addressing this. Can someone
>give me some pointers?
>Thanks in advance, and of course I'll summarize,
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:22 CDT