topic Re: INODE issue in Operating System - HP-UX

INODE issue

Carl Munnelly — Mon, 08 Mar 2004 05:35:45 GMT

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.

Re: INODE issue

Robert-Jan Goossens — Mon, 08 Mar 2004 05:38:32 GMT

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

Re: INODE issue

G. Vrijhoeven — Mon, 08 Mar 2004 05:40:36 GMT

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/

Re: INODE issue

Carl Munnelly — Mon, 08 Mar 2004 05:56:29 GMT

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

Re: INODE issue

Carl Munnelly — Mon, 08 Mar 2004 06:00:08 GMT

Thanks guys,

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

Re: INODE issue

Mark Grant — Mon, 08 Mar 2004 06:00:50 GMT

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.

Re: INODE issue

Robert-Jan Goossens — Mon, 08 Mar 2004 06:01:43 GMT

Attached lsof 11.0 64 bits tar.gz file.