This is what happened~ I am trying to cleanup a hidden file generated by a background process running remotely. And the file is on a mounted share (cifs). The ls command output on linux:

I am logging as root and it shows question mark for the file info:

[root@msbg01 FromABC]# cd FromABC_bak/
[root@msbg01 FromABC_bak]# ls -altr
ls: cannot access .rc_lock: No such file or directory
total 8
-?????????? ? ? ? ? ? .rc_lock

I doubted that the file is already corrupted somehow (I am not an expert on various file mount formats). Does anyone have any idea how to delete it from linux box? Thank you in advance.

Running

As root should do the trick. Just make sure you are in the folder where it is.

Just make sure that by deleting it you are not going to mess up something runnig elsewhere.

Thank you for the response. I've already tried several times and didn't work. It's the file stats on permission concerns me, and I can't even see the info as root:

[root@msbg01 FromABC_bak]# ls -altr
ls: cannot access .rc_lock: No such file or directory
total 8
-?????????? ? ? ? ? ? .rc_lock
drwxr-xr-x. 2 nemedia nasshare 0 Sep 25 15:20 .
drwxr-xr-x. 7 nemedia nasshare 0 Sep 26 09:09 ..
[root@msbg01 FromABC_bak]# rm -rf .rc_lock
[root@msbg01 FromABC_bak]# ls -altr
ls: cannot access .rc_lock: No such file or directory
total 8
-?????????? ? ? ? ? ? .rc_lock
drwxr-xr-x. 2 nemedia nasshare 0 Sep 25 15:20 .
drwxr-xr-x. 7 nemedia nasshare 0 Sep 26 09:09 ..

[root@msbg01 FromABC_bak]# rm -rf .rc_lock

Could you double check that this is what you entered? If it is you are trying to delete a hidden file called rc_lock

There will be no such file.

Copy the command i stated above exactly and make sure you are in the directory.

You must pass *.rc_lock without * it will fail.

1. it sounds like it may have disconnected /unmounted at some point whilst still being used, so its confused now.
Can you try a proper umount/mount (make sure you are not on the mnt when you do that)?

2. I wouldn't use the '-r' option - that's recursive and used for removing recalcitrant dirs, not files.
What you could do is backup one level, backup any other files you need to save, THEN remove the dir, put it back and put back any files.

@chrism - good call, i missed that one! Getting into a dangerous routine of using recursive because lots of file system relables going on at the moment.

Let's be real careful with that - way too easy to wipe out the entire system if run as root....

how was that drive mounted? (what are the mount options)

If the filename was forgotten, yes.sorry for that slip up guys.