We have several files on a Windows server that show up in directory listings but can't be accessed. I can take ownership of the files, and the ACL shows that Everyone has read/write/execute access; but I can't open the files. chkdsk finds no problems on the volume.
The server is 64-bit Win 2008 R2 Standard SP1.
We had a BSOD recently on this server, and the files were modified shortly before the crash. The crash wasn't in anything filesystem-related, but I'm thinking it corrupted something in kernel memory and that corrupted the filesystem.
Here is some of what I'm seeing when trying to access file "com2.log":
D:\Logs\Application>dir com2*
Volume in drive D is Data
Volume Serial Number is 84D5-FD84
Directory of D:\Logs\Application
09/07/2011 06:57 PM 169,025 com2.log
1 File(s) 169,025 bytes
0 Dir(s) 39,320,612,864 bytes free
D:\Logs\Application>dir com2.log
Directory of \\.
File Not Found
D:\Logs\Application>dir com2.*
Directory of \\.
File Not Found
D:\Logs\Application>cacls com2.log
The filename, directory name, or volume label syntax is incorrect.
D:\Logs\Application>more com2.log
Cannot access file \\.\com2
D:\Logs\Application>more com2*
Cannot access file D:\Logs\Application\com2.log
(cacls doesn't show the ACL, but I can see it in Windows Explorer.)
It seems like it might be a problem with the extension. dir com2*
finds it but dir com2.*
does not.
The file shows up as com2.log in Windows explorer, but when I double-click it, I get this error in Notepad referring to a .txt file extension:
Cannot find the \\.\com2.txt file.
Do you want to create a new file?
Has anyone seen anything like this before? Any suggestions for troubleshooting?