1863034 Members
1165 Online
110446 Solutions
New Discussion

disc space utilization

 
SOLVED
Go to solution
Donald Thaler
Super Advisor

disc space utilization

deleted all files on drive u03, yet bdf shows that 70% of the space is still used, and when we try to reload files we get an indication that we've run out of disc space after only a few of the files have been copied back? what could be causing the system to think there is no space available?
4 REPLIES 4
Geoff Wild
Honored Contributor

Re: disc space utilization

Sounds like a file was open prior to delete...

Try unmounting file system - you may have to do a fuser -cu /mount then kill them...

Then remount

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Alzhy
Honored Contributor
Solution

Re: disc space utilization

Donald,

You probably deleted certain files while they are still open by whatever processes that use them. You should just have nulled (cp /dev/null bigfiles) or killed the process if possible.

Only way out is to kill the process that have access to the files that you whacked.. Use lsof (to list the process that have a hook to the no longer existent files and or use fuser -ku on the entire filesystem..)

Hakuna Matata.
Sanjay_6
Honored Contributor

Re: disc space utilization

Hi Donald,

Looks like a file was deleted while a process was still writing to it. you can download and install lsof (if you don't have it already) from this site.

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.72/

lsof command with a +aL1 option would list the process that has a open file in the filesystem. if the mount point for this case is /mount_point

lsof +aL1 /mount_point will list all the processes that has a file open in that filesystem.

Hope this helps.

Regds


Donald Thaler
Super Advisor

Re: disc space utilization

thank you, we forgot to shutdown our test instance of oracle before we deleted all the tablespaces. once we killed the leftover process from the test instance the used space went to 0.