bdf output differs from du -k

[Brian Watkins]

Our DBA's dropped a 2GB tablespace from a database and deleted the dbf file from the server.

When a bdf is run on the filesystem that used to host the dbf file, the result shows that 2.1GB is used. When a du -k is run against the same filesystem, it shows approximately 4.3MB of space used.

I've heard of this happening before (Oracle "reserves" filesystem space even if it's not using it), but have never actually encountered it. Any explanations/ideas as to why this happened and how to resolve it?

Any input would be appreciated! Thanks in advance... :)

[Ken Hubnik_2]

There could be a process that must be killed before it releases the space.

[Jeff Schussele · Accepted solution]

This occurs when someone deletes a file that's still open by a process.
Exactly what happened in your case. The space will only be freed when the process ends, is halted or terminated.

Rgds,
Jeff

[Chris Vail]

Yeah....the process hasn't died. Oracle still has a reservation on the space. There's a couple of ways to fix this: the easiest is to stop and restart Oracle, or even reboot the server.

You can locate the process which has the file reserved with lsof. Killing that process will return the reserved space. ISTR that fuser will also locate the proces that has the the open file.

Chris

[Brian Watkins]

Thanks for the quick responses! That's why I love these forums...

After working with the DBAs, we arrived at same conclusion as all of you did: Oracle still has the space reserved and the only way to release it would be to bounce the database.

Thanks again! 8^)