Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a compilation problem, and when I check my lib/ directory I get this output from "ls":

ls output

What the red/black combination mean?

I checked in the output of "dircolors -p" as suggested here (What does it mean for the file name to be shown with red background), but I could not find an answer.

Moreover, what the question marks at the place of permissions/user/size/timestamp mean?

Thanks for your help

share|improve this question
up vote 8 down vote accepted

What you have there is a dangling symlink, or a symlink pointing to a file or directory which no longer exists.

A symlink itself really has no filesize, because it isn't a file. Symlinks are stored within the inodes themselves, meaning they have no real contents or size, but are instead pointers to other files on the disk.

The output of file libCLHEP-Exceptions- should reveal where it's pointing to.

share|improve this answer
ls -l should also print the symlink target, which it doesn't seem to do here. – Stefan Seidel Jan 29 '13 at 13:44
This is true in most cases, but I've seen it fail to do that in a couple of obscure circumstances. file is usually a lot better at working out what's going on with a particular, erm, file. – Xyon Jan 29 '13 at 13:45
Many thanks Xyon, I didn't know the file command: it's very useful indeed. +1! – rmbianchi Jan 30 '13 at 13:30

At the first look, it does look like a broken link, but since it is supposed to be a regular file, it might be a file system corruption. Try to do a fsck on the file system and then try to delete this file if it is still there.

share|improve this answer
Thanks for your answer Stefan, +1. Actually I tried to remove the broken link, but rm gave a "no such file or directory" error. was very strange, actually, because the link was broken, the file not there, and rm still refused to delete the link... Anyway, I removed the whole folder, and that fixed the problem. – rmbianchi Jan 30 '13 at 13:32

After having posted this I found this page:

Apparently they could mean "orphaned symlinks".

But why it show the question marks? The symlink should have its own size of some bytes, for example; isn't it?

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .