File names that contain "01" act hidden

Haveing an issue. Anytime a file is created with "01" (zero one) in the name - it cannot be viewed by LS or any other file listing command. Although the file is there, it cannot be seen. I can edit it, run it, anything, except see it.....

What happened? Any ideas?

$ ls
01 01new
$ touch .01
$ ls
01 01new
$ ls -l
total 0
-rw-r--r-- 1 UID GID 0 Jun 7 15:50 01
-rw-r--r-- 1 UID GID 0 Jun 7 15:50 01new
$ ls -la
total 4
drwxr-xr-x 2 UID GID 512 Jun 7 15:52 .
drwxrwxrwx 7 UID GID 512 Jun 7 15:50 ..
-rw-r--r-- 1 UID GID 0 Jun 7 15:52 .01
-rw-r--r-- 1 UID GID 0 Jun 7 15:50 01
-rw-r--r-- 1 UID GID 0 Jun 7 15:50 01new
$ echo $SHELL

are you sure it is not beganing with "." ??

Those files that were created did not show up, but they were created.

The do not show up in the LS command
but they are there, like hidden system files on a PC in dos mode

Nothing with a dot, anything, and I mean anything, with "01" in the file name is not showing, its there, just not listing

did you try ls -la?

oh yeah - I covered every single basic

shared the files, shared the director to another unix server....

Every possible way to show those damn files. Even using samba via an NT server still does not show.

Driven me nuts here.

sorry man then i am at a loss.

Well poop!!!

This kinda sucks, I have no idea if it could be a hardware or software thing at this point. Sun references nothing like this on/in their documentations....

Any ideas on where to send me?

Thanks for tryin anyway

i would say it is a one of two things.

user error

no offense but it is usually the latter.

The same thing happened with me but we found the solution(Solaris)Solaris
See your PATH variable must be /usr/bin/ls , this is where ls command is searched for when you give ls command. Now if you want to see the 01 files also in fact all the files in your directory then add /usr/xpg4/bin/ls in your PATH variable before /usr/bin/ls path. Or if you are not using solaris then give man ls and look whether there is any alternative path where ls command is located. If yes then try using that path.
I bet this will work since it worked for me.