Mystery files, "not a directory"
Interesting and tricky problem. I downloaded the source of Pidgin plugin, which I attempted to install. The configure script made some files for this type:
Code:
./conf18760.dir/conf18760.file Every program I try to use on these files complains "Not a directory". I've tried stat, rm, unlink, ls and mv; they all say the same thing: "Not a directory". i.e.: Code:
bash-3.2$ stat conf18760.file Is there a way to transform this 'symbolic link' into a plain file, so I can delete it? All I'm trying to do is remove this directory tree. Other random bits of possibly helpful info:
|
Have you tried deleting using the -f (force) switch?
|
Hi,
What happens if you try to find the original file using find and the inode given? find -inum 6387 If at all possible try this as root (could be a problem, this being a university box). |
Quote:
Quote:
Thanks for both of your suggestions =) |
Hi,
6387 is the inode of the linked file, the original should have another inode. Example: Code:
$ touch real.file.A |
Solved (ish)
Okay, I've managed to delete these files afterall. I think it must have something to do with being mounted via Samba, and changes not propogating to the server.
I logged into a Linux server and 'rm -rf' on the directory tree: it worked. After refreshing the directory on my local machine, the files were gone. Perhaps there's a bug somewhere. |
Quote:
If my understanding is correct, then the inodes would be the same if linked.to.real.file.A was a hardlink. Perhaps this is what you were thinking of? Anyway, I'm not sure how or why this happened, but at least I've managed to delete the files. I suspect that remounting the Samba share would have had the same result as logging into another machine. Thanks for your help though! |
All times are GMT -5. The time now is 01:23 PM. |