I know nothing about this stuff, so this is probably no help, but going on the title alone, I occasionally have that problem, and for me it's a permissions thing. I have to go in and change the permissions on the file or directory to delete it.

The closest thing I ever encountered like this was when I noticed a file using my site host's FTP panel.

Ended up it was a "symbolic link".

Definitely isn't a symbolic link, that would have been apparent in the ls -la command.

ralph_m said:

I know nothing about this stuff, so this is probably no help, but going on the title alone, I occasionally have that problem, and for me it's a permissions thing. I have to go in and change the permissions on the file or directory to delete it.

Yeah, but sudo should trump any permission issues shouldn't it? If I can't delete it using sudo and root is disabled... what is left? I've never had this happen to me before... Granted, maybe I need to actually login to the NAS directly to see if I can't remove it there and it is a CIFS issue... hmm... I'll try that real quick.

Got it! Oddly enough, connecting to the NAS over a shared folder and deleting it from a Windows box works. Strange that I can't delete it from a Linux box or on the NAS itself... Whatever Windows sent as the delete command worked like a charm!

I guess it would have worked by escaping the weird character with \, like:

rm -f myweirdfiles-NoGrp/myweirdfile.\\_.part01.rar

Where "_" would be the weird char.

Nope. Did that plenty of times, the files always remained. I still haven't a clue what character or encoding the character was in that caused it to not be deleted on Linux, but now that it is gone, I'm happy

Part of the issue could be that I couldn't tell what the character was supposed to be, so I could never match the filename. What really strikes me as odd, is even telling it to remove ALL of the files via wildcard didn't work...

Well, rm still reads each single file name and apparently the charset was that messed up, that none of the pipes was able to read/process it properly. Another option would have been to just move the upper folder to /dev/null.