1753855 Members
7303 Online
108808 Solutions
New Discussion юеВ

File with no name

 
SOLVED
Go to solution
Fabian Brise├▒o
Esteemed Contributor

File with no name

Hello guys.
I got a strange one for you, Today as I was checking a root filesystem that was getting full I found a file that was created yesterday morning at 6:30 AM, but the weird thing is that the file has no name.

Im continuing to investigate what generated this file, as always any help you can provide is welcomed, have a nice day.

Im attaching the screenshot.

Look at filesize 43423744.
Knowledge is power.
5 REPLIES 5
James R. Ferguson
Acclaimed Contributor
Solution

Re: File with no name

Hi Fabian:

No doubt that the file name consists on un-printable characters. You could do:

# ls -lb

An easy way to rename or remove it is to use its inode number from:

# ls -il
# find /path_to_file -xdev -inum -exec rm -i {} ;

If you do this, make sure that you restrict the search for the file by inode number to the filesystem in which the file lives. Inodes are only unique with a filesystem!

Regards!

...JRF...
mobidyc
Trusted Contributor

Re: File with no name

Hello,

Your filename surely contains nonprinting characters.

to see it, you can use the -b flag to ls :
# ls -b

to remove or rename this file :

check the inode number
# ls -i

work on it with find:
# find . -xdev -inum -exec mv {} new_name.file \;

Regards,
Cedrick Gaillard
Best regards, Cedrick Gaillard
Fabian Brise├▒o
Esteemed Contributor

Re: File with no name

Hey.
Thanks for the quick response guys.

let me try your seggestions.

I'll get back to you.

Knowledge is power.
Fabian Brise├▒o
Esteemed Contributor

Re: File with no name

Mr. Ferguson and Mr. Mobidyc.

Your suggestions worked like a charm.

I renamed the file and foud out it is an INDEX file from FBACKUP.

I'll continue to investigate as to why this file was generated in the root filesystem.

Thanks a lot for your help.

I owe you a cold one.
Knowledge is power.
Fabian Brise├▒o
Esteemed Contributor

Re: File with no name

Guys im closing this thread out.
The root of the problem (no pun intended) was that my tape device was in a NO_HW state so the output of the INDEX file was sent to root.

I logged a report to HP and deleted the file.

Have a nice day.
Knowledge is power.