<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Crashed Temp space on SAS 9.4 BI server in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485050#M13831</link>
    <description>&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;I am aware of the cleanup utility.&lt;/P&gt;
&lt;P&gt;What I am looking for&amp;nbsp; is opinion on the statement "&lt;SPAN&gt;the file system crashed and deleted the offending files.&amp;nbsp;".&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Aug 2018 08:56:05 GMT</pubDate>
    <dc:creator>thesasuser</dc:creator>
    <dc:date>2018-08-08T08:56:05Z</dc:date>
    <item>
      <title>Crashed Temp space on SAS 9.4 BI server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485047#M13829</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;My organization has a SAS BI server on Windows and clients connecting through SAS EG.&lt;/P&gt;
&lt;P&gt;We have a system of getting notified when the space on any file system exceeds 90% of available space.&lt;BR /&gt;SASWORK exists on a separate drive and whenever the space consumption reaches 90% we get notified.&lt;/P&gt;
&lt;P&gt;I recently joined the organization. Whenever such a notification is received I checked the system.&amp;nbsp;&lt;BR /&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;However according to&amp;nbsp; 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.&lt;BR /&gt;I do not understand this logic.&lt;BR /&gt;Can anybody in the forum guide me in this.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Aug 2018 08:44:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485047#M13829</guid>
      <dc:creator>thesasuser</dc:creator>
      <dc:date>2018-08-08T08:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: Crashed Temp space on SAS 9.4 BI server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485048#M13830</link>
      <description>What part don't you understand?&lt;BR /&gt;There is a SAS utility cleanwork that deletes orphaned directories and files which should be scheduled daily at least.&lt;BR /&gt;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.</description>
      <pubDate>Wed, 08 Aug 2018 08:52:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485048#M13830</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2018-08-08T08:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: Crashed Temp space on SAS 9.4 BI server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485050#M13831</link>
      <description>&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;I am aware of the cleanup utility.&lt;/P&gt;
&lt;P&gt;What I am looking for&amp;nbsp; is opinion on the statement "&lt;SPAN&gt;the file system crashed and deleted the offending files.&amp;nbsp;".&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Aug 2018 08:56:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485050#M13831</guid>
      <dc:creator>thesasuser</dc:creator>
      <dc:date>2018-08-08T08:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: Crashed Temp space on SAS 9.4 BI server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485063#M13832</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/39715"&gt;@thesasuser&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;I am aware of the cleanup utility.&lt;/P&gt;
&lt;P&gt;What I am looking for&amp;nbsp; is opinion on the statement "&lt;SPAN&gt;the file system crashed and deleted the offending files.&amp;nbsp;".&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;If this is what was literally said, the statement is rubbish and reveals that somebody has no clue.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Aug 2018 10:01:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Crashed-Temp-space-on-SAS-9-4-BI-server/m-p/485063#M13832</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-08-08T10:01:05Z</dc:date>
    </item>
  </channel>
</rss>

