UNIX for Dummies Questions & Answers

If the file system is not corrupted in the sense that an fsck won't find an error,
then you still have got a bug in the file system handler (in the Unix kernel): it allows to create directory entries (names) that cannot be handled afterwards.
What does a

Code:

df bad

show?

added unlink to my code

Code:

printf("%li\t%s\n", di->d_ino, di->d_name);
if(unlink(di->d_name) == -1)
{
        err = errno;
        printf("unlink rc=%i %s\n", err, strerror(err));
}

and I am getting same

Code:

129935  000025;001;1377795616;��^A
unlink rc=2 No such file or directory

Any ideas?

If unlink is puking on valid filenames, I'm not sure what you can do; those files are effectively blocked off, to the kernel, invisible, it can't see them. You may need to work with things at a lower level than that, dangerous things, disk-editing sort of things.

You might want to consult a little tutorial of mine.

I hope this helps.

bakunin

Thanks, I don't have filedb on this system, but I do have clri, will investigate.

Just a side note - someone moved this thread and I found it just by luck. Why? How people follow their threads when topics are moved?

Moderator's Comments:

edit by bakunin: In fact colleague Scott moved it, perhaps because he is convinced that this thread belongs to this forum. How to find your thread is easy: there is an (expiring) redirect in the original place, but it is removed after some time (default is 6 hours). You can also access your "subscribed threads" from the UserCP (have a look at the top of this page, horizontal main menu, second item from the left side) once you have placed a post (which automatically subscribes you to a thread). This is how i keep track of the threads i am engaged in. Threads with new posts will be displayed in emphasized fashion. Finally you can use the search function (in the same horizontal menu, third item from the right side) and search for either keywords or/and user-IDs.

You might want to try one of the less complicated methods first, namely the variant using "find" and the inode-number.

Use an "ls -i" to list the files with inode-numbers, capture that to a file and delete all the lines with files which should stay. Then read this file and execute for every line the "rm", like in this sketch of a script:

Code:

while read inum ; do
     find -inum "$inum" -exec rm -f {} \;
done

I hope this helps.

bakunin

Suggested and failed (posts #3 and #4).

Even passing readdir's pathnames directly to unlink doesn't work. Whatever is going on here, if going directly from readdir to unlink doesn't work, then nothing that depends on the syscall interface will work.

Regards,
Alister