INODE issue

[Carl Munnelly]

In vain hope that I can avoid a system reboot.

A user had deleted a file in /tmp which was still accessed by a process. However, I don't know the process. Is there anyway of identifying the inode and process and killing it from my current situation. Other than a reboot obviously.

[Robert-Jan Goossens]

Hi,

You could try and use fuser or lsof on the tmp filesystem.

http://hpux.connect.org.uk/hppd/hpux/Sysadmin/lsof-4.70/

Regards,
Robert-Jan

[G. Vrijhoeven]

Hi,

If you rm-ed the file the inode gets removed when the Process keeping it open stops. To get the process, you can use lsof < not standard installed but the best tool for this kind of problems> or fuser -cu /tmp

HTH,

Gideon

PS. a link to lsof:

http://hpux.connect.org.uk/hppd/hpux/Sysadmin/lsof-4.70/

[Carl Munnelly]

I know lsof is ideal unfortunately not installed and can't download as blocked.

[Carl Munnelly]

Thanks guys,

I was investigating fuser and during that time the process must have sfinished as space released

[Mark Grant]

Other than the "fuser" suggestion above which on "/tmp" is probably going to be a bit of a nightmare, you can't do it in any easy way.

THere is no way you can reclaim the space without stopping that process.

If you know the name the file had, it might be useful. If it is a tempory file that usually has the same name, you could doa strings on on the binaries of your running applications to lookf for the filename and then stop that application.

[Robert-Jan Goossens · Accepted solution]

Attached lsof 11.0 64 bits tar.gz file.