Crashed Temp space on SAS 9.4 BI server

[thesasuser]

Hello

My organization has a SAS BI server on Windows and clients connecting through SAS EG.

We have a system of getting notified when the space on any file system exceeds 90% of available space.
SASWORK exists on a separate drive and whenever the space consumption reaches 90% we get notified.

I recently joined the organization. Whenever such a notification is received I checked the system. 
Incidentally whenever I checked I observed that much of the space has been freed. My understanding is that the process(es) that consumed that space have completed normally and the space has been freed.

My understanding is that if there is an abnormal termination of a SAS processes than the temporary folder for that process would be orphaned and continue to exist until deleted either manually or with cleanup utility.

However according to  the SAS Admin (he has been around for a longer period) the file system crashed and deleted the offending files. So we see more space available.
I do not understand this logic.
Can anybody in the forum guide me in this.

[LinusH]

What part don't you understand?
There is a SAS utility cleanwork that deletes orphaned directories and files which should be scheduled daily at least.
If you reach 90% occasionally my recommendation is to enlarge your SASWORK file system, and/or investigated there is a reason for any overuse of SASWORK.

[thesasuser]

Thanks.

I am aware of the cleanup utility.

What I am looking for  is opinion on the statement "the file system crashed and deleted the offending files. ".

[Kurt_Bremser]

---

@thesasuser wrote:

Thanks.

I am aware of the cleanup utility.

What I am looking for  is opinion on the statement "the file system crashed and deleted the offending files. ".

---

If this is what was literally said, the statement is rubbish and reveals that somebody has no clue.

A filesystem that crashes needs to be re-initialized and its contents restored from the backup (if necessary). A crashed filesystem is usually inaccessible and often causes the system itself to halt. At best it stops being writeable.