topic which process is still using deleted files in Operating System - HP-UX

which process is still using deleted files

GTFSpanneer — Mon, 09 Aug 2010 05:56:11 GMT

Hi All,

We have deleted some files but the file system space is not getting reclaimed. how to check which process is still using deleted files in hp ux

Thanks in advance.

Panneer

Re: which process is still using deleted files

AnthonySN — Mon, 09 Aug 2010 06:15:12 GMT

which files have you deleted, are they any datasbase files or normal text files?

Re: which process is still using deleted files

GTFSpanneer — Mon, 09 Aug 2010 06:24:37 GMT

Hi SASj,

database file.

tbs1_tmp01.dbf

Re: which process is still using deleted files

rariasn — Mon, 09 Aug 2010 06:28:04 GMT

Hi:

Restart application.

Use lsof utility.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=110362

rgs,

Re: which process is still using deleted files

Asif Sharif — Mon, 09 Aug 2010 06:31:38 GMT

Hi,

shutdown/Start up your database will solve your issue.

Regards,
Asif Sharif

Re: which process is still using deleted files

AnthonySN — Mon, 09 Aug 2010 06:31:48 GMT

and how did u delete that file doing rm -rf, which is not the correct way of doing it.
you need to restart db.

Re: which process is still using deleted files

Berd — Mon, 09 Aug 2010 13:39:24 GMT

I would use lsof utility.

Re: which process is still using deleted files

Viktor Balogh — Tue, 10 Aug 2010 23:36:50 GMT

Hi,

Use this command to identify the processes which use the already deleted files:

# lsof +D / +L1

Look for the files with NLINK count of zero.

Regards,
Viktor

Re: which process is still using deleted files

Elmar P. Kolkman — Wed, 11 Aug 2010 08:47:20 GMT

And if you don't have lsof installed but a working version of glance, you could use that.

But in this case, you know which file it is, so you might also know which database had that file. That means that you or your DBA should be able to find which database and which databases process is using the file (possibly all processes of the database, if it's the temporary tablespace for your oracle database, for instance). Restarting the database should solve your issue from a Sysadmin point of view, though I suspect it means the database is broken from a DBA point of view...