Strange filename(?) - where did it come from and how to get

QNX Newsgroups (Archives) qnx.qnx4
1

Running QNX 4.25 patch G I have under /usr/tmp an entry “I\003QNX”.
(The ‘\003’ character appears in the command window as a heart glyph.)

It apparently is not a real file:

ls -l /usr/tmp

ls: No such file or directory (/usr/tmp/IQNX)
drwxrwxr-x 1 root root 4096 Aug 15 12:31 /

I have attempted to get rid of it:

rm -Rf /usr/tmp

rm: Can’t remove directory /usr/tmp: Corrupted file system detected

Doing an initial chkfsys at bootup shows:

[ //1/usr/tmp/IQNX ]
link lost
Paused (Cannot fix)…

Any idea of where this came from? (My suspicions are the NFS server, since
it apparently creates an entry mountdtab under /usr/tmp, the only other
file in this directory before I removed it.) And of course, how to I get
rid of it?

  • Will
2

Will Parsons wrote:

Running QNX 4.25 patch G I have under /usr/tmp an entry “I\003QNX”.
(The ‘\003’ character appears in the command window as a heart glyph.)
It apparently is not a real file:

The I-heart-QNX is a directory signature (hidden after the “.” name as
a fingerprint to chkfsys to verify the block really is a directory). It
should be: “2E 00 49 03 51 4E 58 00 08 00 00 00 00 00 00 00” (first 16
bytes of directory block, can use “spatch” to examine this vs a good
one). Sounds like your data has shifted 2 bytes over (or the 00 has
turned into a 08 or other backspacing character)?! You could try to
remove the corrupt directory using “zap /usr/tmp”.

3

John Garvey wrote:

Will Parsons wrote:
Running QNX 4.25 patch G I have under /usr/tmp an entry “I\003QNX”.
(The ‘\003’ character appears in the command window as a heart glyph.)
It apparently is not a real file:

The I-heart-QNX is a directory signature (hidden after the “.” name as
a fingerprint to chkfsys to verify the block really is a directory). It
should be: “2E 00 49 03 51 4E 58 00 08 00 00 00 00 00 00 00” (first 16
bytes of directory block, can use “spatch” to examine this vs a good
one). Sounds like your data has shifted 2 bytes over (or the 00 has
turned into a 08 or other backspacing character)?! You could try to
remove the corrupt directory using “zap /usr/tmp”.

Thanks, zap -R took care of it.

  • Will