Strange case: Text file that exist and doesn't exist

I'm entirely puzzled concerning a trouble with a solitary simple message documents in my system fedora 12. I made use of a well-known software program in bioinformatics, manufacturer, to generate great deals of simple message files and also among them it appears to be "inaccessible".

Specifically, my documents called Clon1918K_PCC1.gff is detailed when I make use of ls, ls -a, ls -li commands yet when I attempt to access it by cat, vim, cp, ls etc it shows up constantly the very same mistake Clon1918K_PCC1.gff: No such file or directory.

Nonetheless, when I replicate all the files with cp *.gff or cp * this documents it is additionally replicated.

Additionally I attempted to open it with nautilus without trouble and also in either instances when I replicated the web content to an additional documents with the very same name the trouble goes away. Surprisingly in this instance the weird documents is not revised and also 2 files with specifically the very same name show up, among them obtainable and also an additional hard to reach. I sought surprise personalities yet all appears ok.

A person has any kind of suggestion concerning this weird instance?? Thanks!

5
2022-06-07 14:39:50
Source Share
Answers: 5

It is not feasible in linux to have 2 files with the very same name staying in very same directory site.

Attempt to vim the moms and dad directory site and afterwards browse to "stranger" documents and also see, if you can access it

0
2022-06-07 15:10:12
Source

attempt to relabel the documents with nautilus, yet type the wanted name (do not replicate paste). That need to absolutely remove any kind of unique personalities. It could also be a room after/before the filename that is unseen to you yet noticeable to the OS and also programs. I generally make use of mc to manage actual' unusual filenames.

2
2022-06-07 15:10:10
Source

You can not have 2 files with the very same name in the very same directory site. Filenames are necessarily one-of-a-kind keys.

What you have is likely an unique personality. I recognize you looked for them, yet just how specifically? You can claim something like ls *gff | hexdump -C to locate where the unique personalities are. Any kind of byte with the high little bit set (that is, hexadecimal values in between 80 and also FF) will certainly be a sign of something failed. Anything listed below 20 (decimal 32) is additionally an unique personality. An additional tip is the visibility of dots . in the right, message column of hexdump -C.

There are countless personalities that resemble United States ASCII personalities in UTF - 8. Also in United States ASCII, 1 and also l can usually look comparable. After that, you have The C from Cyrillic (U+0421), the Greek Lunate Sigma (U+03F9, additionally specifically like a C), Cyrillic/Greek lower instance 'o', etc And those are simply the noticeable ones. There are plenty of unseen Unicode personalities that can be therein.


Description: why does the high little bit indicate something failed? The filename 'Clon1918K_PCC1. gff' seems 100% 7 - little bit United States ASCII. Placing it via hexdump -C generates this:

00000000  43 6c 6f 6e 31 39 31 38  4b 5f 50 43 43 31 2e 67  |Clon1918K_PCC1.g|
00000010  66 66                                             |ff|

All of these byte values are listed below 0x80 (8th little bit clear) due to the fact that they are all 7 - little bit United States ASCII codepoints. Unicode codepoints U+0000 to U+007F stand for the typical 7 - little bit United States ASCII personalities. Codepoints U+0080 and also above stand for various other personalities and also are inscribed as 2 to 6 bytes in UTF - 8 (on Linux, attempt man utf8 for a great deal of details on just how this is done). Necessarily, UTF - 8 inscribes United States - ASCII codepoints as themselves (i.e. hex ASCII personality 41, Unicode U+0041, is inscribed as the solitary byte 41). Codepoints ≥ 128 are inscribed as 2 to 6 bytes, each of which have the 8th little bit set . The visibility of a non - ASCII personality can conveniently be identified by this without needing to translate the stream . As an example, claim I change the 3rd personality in the filename, 'o' (ASCII 6f, U+006F) with the Unicode personality 'U+03FB GREEK SMALL LETTER OMICRON' which resembles this: 'ο'. hexdump -C after that generates this:

00000000  43 6c ce bf 6e 31 39 31  38 4b 5f 50 43 43 31 2e  |Cl..n1918K_PCC1.|
00000010  67 66 66                                          |gff|

The 3rd personality is currently inscribed as the UTF - 8 series ce bf, each byte of which has its 8th little bit set. And also this is your indicator of problem in this instance. Additionally, note just how hexdump, which just translates 7 - little bit ASCII, falls short to translate the solitary UTF - 8 personality and also reveals 2 unprintable personalities (..) rather.

9
2022-06-07 15:09:40
Source

Have you taken into consideration the visibility of a rootkit? Once, I had accessibility to a Solaris equipment that had actually a rootkit mounted. Files called' *01' were not noticeable with ls *01 or ls -altr, yet did turn up with an echo *01. The installment of the rootkit had actually transformed ls (and also a variety of various other executables) to make sure that particular files and also procedures did not show up under the common conditions. Your summary appears a whole lot like the rootkit I ran into.

1
2022-06-07 15:09:26
Source

It is most likely that there is a "strange" personality in the documents name: probably a room, or a control personality, or a non - ASCII personality that resembles an ASCII personality. Given that the documents is matched by *.gff, any kind of unique chararcter would certainly be prior to the ..

Run LC_ALL=C ls -l --quoting-style=c *.gff to see a non - unclear depiction of the documents name.

Run mv -i *.gff Clon1918K_PCC1.gff to rename the documents to a well-known name.

1
2022-06-07 14:47:54
Source