inode

[christian_derek]

Hi,

I'm using a third party speedware. Each occurence of their tools create to file that can only be seen by typing ff -usF vxfs /dev/vgeva8/lvoleva2. The result of the command is ./(null) 1000 500000. Where ./(null) is the filename and 1000 inode of the file. Is there a way to display the containt of the file or know why those files are created. The reason behind that is every instance of speedware creates 600Kb, I'm trying to start 2000 users in a few minutes, that cause 1,6gb to be written to disk. A lot of io.

Thanks,

[Con O'Kelly · Accepted solution]

Hi Christian

Is it possible to use the find command on the inode number to determine the of type file and possibly read its contents.

EG
# find / -inum 1000 -exec file {} \;
# find / -inum 1000 -exec cat {} \;

Cheers
Con

[Cesare Salvioni]

hi
seems to me that this software, or maybe the way you use it, is not completly right. What i mean is that it looks like it is creating a file without linking it to a name. If the file does not disappear after the end of the running i would be very worry: this should ABSOLUTELY not happen.
If, on the contrary, after the run the disk space is back, it's just a temporary file that is written without being completly created: that's pretty normal.
Anyway, in my opinion, there is nothing to do but ask the programmer to modify the code if you think is not efficient.

not much, but hope it helps :-)
buy

[Ivajlo Yanakiev]

I'm in stress.
I think that when you rm somefile you just remove name from inod after that any new file can replace data from that file.
Unix treat files without name as a deleted file.

[christian_derek]

Hi,

Thank you for your answer, I try it, but still unable to see the contain. Just to let you know when the application log off, those files are gone.

Thanks,