After prodel df -k does not show more free space available

RealHeavyDude

RealHeavyDude

Well-Known Member
OpenEdge 10.1C Sun Solaris SPARC 64Bit, NFS file system.

I've stumbled over a - to me - strange problem for which I have no explanation:

After deleting a database with the prodel command I failed to create a database of the same size with different extent sizes. A look at df -k revealed that, although I have deleted the database, the file system was still used at nearly the same ratio as it was before - certainly not what I was expecting as the database used almost 80% of the file system. Thus preventing me successfully to create a database either using the old structure description file or the new one (less but larger extents) ...

I must admit that I am no *NIX OS command know how expert, but that seems very strange to me.

Anybody know what I've done wrong or what the reason for this behavior could be?

Thanks in advance,
RealHeavyDude.
 
Check output of lsof +L1
Probably some process(es) had opened database files before you have deleted it. In such situation file is still accessible to such process, though no new process can open such file (because it has been unlinked from directory entries). When you close/kill process then OS should free disk space.
Progress also uses this mechanism - after starting session Progress creates lbi/srt files and then immediately unlinks them from FS.
 
The process may have the db open with -RO (which would explain why prodel worked).

It could even be a process on another system (since NFS is involved).
 
Thanks for your replies.

Lucky me, this was a test machine. As it turned out some process with root privileges was still sitting on the database files. This rogue process with root privileges resulted from a KEAX session which was not closed gracefully ...

Thanks, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top