August 14, 200817 yr Anyone ever have this issue with bad/invalid filenames on reiserfs. The file below was "WHITE_NOISE.ISO". Something happened one day and it got changed to this invalid name. This isn't the first time, I noticed in one of my bittorrent directories some filenames were invalid too. I think this happens during an unclean crash or power issue. I think this is a source of why my ftw utility is failing. It cannot get past this when doing a tree walk (nor can slocate). In any case, I was curious how to remove it. I cannot access it in any manner and rm does not work -rw-r--r-- 1 root root 4681494528 Jan 6 1970 UNTRACEABLE.ISO -rw-r--r-- 1 rcotrone users 4681435136 Jun 27 2007 USUALSUSPECTS.ISO ???? ? ? ? ? ? WHIT"kMOISE_2.ISO root@Atlas:/mnt/disk2/Videos# rm "*WHIT*" rm: cannot remove `*WHIT*': No such file or directory Ok, I'm becoming more disenchanted with reiserfs, never had this issue with ext3.
August 14, 200817 yr Here is what I do. Assuming the file system is checked and it is just a mangled name: I use ls -li to get the inode number of the file with the mangled name (it is the number at the beginning of the ls -i output, shown in RED below). Then, I use the "find . -inum" command to rename the file. I did it here with a file named "junk" but it does not care what the name is, once you are referencing the file by its inode number. root@Tower:/boot# ls -li junk 777 -rwxr-xr-x 1 root root 0 Aug 14 11:36 junk* root@Tower:/boot# find . -inum 777 -exec mv {} junk_renamed \; root@Tower:/boot# ls -li jun* 777 -rwxr-xr-x 1 root root 0 Aug 14 11:36 junk_renamed*
August 14, 200817 yr Author ls -li 640 ???? ? ? ? ? ? WHIT"kMOISE_2.ISO root@Atlas:/mnt/disk2/Videos# find . -inum 640 -exec mv {} junk_renamed \; find: ./WHIT"kMOISE_2.ISO: No such file or directory Thoughts?
August 14, 200817 yr ls -li 640 ???? ? ? ? ? ? WHIT"kMOISE_2.ISO root@Atlas:/mnt/disk2/Videos# find . -inum 640 -exec mv {} junk_renamed \; find: ./WHIT"kMOISE_2.ISO: No such file or directory Thoughts? You have checked the file-system using reiserfsck? And it is OK? I would give it a try through SAMBA, or move all the other files out of the same directory and then cd to the parent directory and then rm -rf the directory. I had something like this happen to me long ago. The file corrupted file name had an embedded "/" within it. Darned OS kept trying to interpret it as a directory path component. It was a very old version of PC networking that did it on StarLAN that did it to me. I ended up using fsdb to fix it. Joe L.
August 15, 200817 yr Author I had to run reiserfsck with the --rebuild-tree option to clear this up. There was a corruption found. it took a long time (over an hour). When the filesystem came up, the bad filenames were no longer there.
August 15, 200817 yr I had to run reiserfsck with the --rebuild-tree option to clear this up. There was a corruption found. it took a long time (over an hour). When the filesystem came up, the bad filenames were no longer there. Did the normal reiserfsck tell you to use the --rebuild-tree option? Or did it pass its tests? Joe L.
August 15, 200817 yr Author I had to run reiserfsck with the --rebuild-tree option to clear this up. There was a corruption found. it took a long time (over an hour). When the filesystem came up, the bad filenames were no longer there. Did the normal reiserfsck tell you to use the --rebuild-tree option? Or did it pass its tests? Joe L. It said corruption found, run --rebuild-tree. Funny thing is I'm having problems with slocate scanning certain directories and capturing files along with ftw(). (the base routine). I'm wondering if there are issues with the filesystem and/or directories itself.
Archived
This topic is now archived and is closed to further replies.