﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel><title>ola.kodar.se</title>
<description>Sharing is caring</description>
<generator>ola.kodar.se</generator>
<link>http://ola.kodar.se/</link>
<item>
  <title>Strangest cannot resolve symbol error ever</title>
  <link>http://ola.kodar.se/blog/strangest-cannot-resolve-symbol-error-ever/</link>
  <description>&lt;p&gt;This is a not so uncommon error: &lt;a href="/files/2010/03/cannot-resolve-symbol-wtf.png"&gt;&lt;img title="Cannot resolve symbol &amp;#39;PooledHttpClient&amp;#39;" class="size-full wp-image-146" alt="" src="/files/2010/03/cannot-resolve-symbol-wtf.png" width="470" height="132" /&gt;&lt;/a&gt;     &lt;br /&gt; But when I switched to PooledHttpClient.java I got a bit confused:    &lt;br /&gt;&lt;a href="/files/2010/03/PooledHttpClient.png"&gt;&lt;img title="PooledHttpClient.java" class="size-full wp-image-147" alt="" src="/files/2010/03/PooledHttpClient.png" width="559" height="163" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;Seriously w t f happened here? Has my RAID controller gone berserk on the poor file? &lt;/p&gt;  &lt;p&gt; A couple of weeks ago I saw something similary happend on a production server (VPS).    &lt;br /&gt; Suddenly one of my static HTML-files contained fragments of code from something completely different.     &lt;br /&gt; As far as I can tell, these errors seems to originate from a broken file system.     &lt;br /&gt;Perhaps one should take stuff like this as a sign that it might be wise to start replacing the disks in the raid array.&lt;/p&gt;</description>
  <author>test@example.com</author>
  <category>error-of-the-day</category>
  <guid isPermaLink="false">http://ola.kodar.se/blog/strangest-cannot-resolve-symbol-error-ever/</guid>
  <pubDate>Sun, 25 Apr 2010 14:30:59 GMT</pubDate>
</item>
<item>
  <title>ASP.NET: System.IO.IOException: The file or directory is corrupted and unreadable.</title>
  <link>http://ola.kodar.se/blog/aspnet-systemioioexception-the-file-or-directory-is-corrupted-and-unreadable/</link>
  <description>&lt;p&gt;A couple of month ago all sites died on one of my old servers (a Windows 2003 based Virtuozzo VPS).    &lt;br /&gt;I wrote a line about it in one of my previous &lt;a href="/2010/03/19/strangest-cannot-resolve-symbol-ever/cannot-resolve-symbol-wtf"&gt;posts&lt;/a&gt;, at least one static HTML-file contained fragments of code from something completely different. &lt;/p&gt;  &lt;p&gt;One of the first observation I did on the server was that every site had their own strange error even though almost everyone was running the same version of &lt;a href="http://umbraco.org/"&gt;Umbraco&lt;/a&gt;.     &lt;br /&gt;As an example, one site did not start at all while another could start but would end up crashing after a couple of hours and bringing down the whole server again. (Not just the application pool.) &lt;/p&gt;  &lt;p&gt;I quickly migrated all critical sites from the server leaving just one behind. Today I decided to fix the one that was left behind and also try and determine what was wrong with the server. After a bit of digging I managed to find one useful error message. &lt;/p&gt;  &lt;blockquote&gt;Exception Details: System.IO.IOException: The file or directory is corrupted and unreadable.&lt;/blockquote&gt; And my good friend google told me that this might just be an issue with the ASP.NET file cache. I quickly located the cache in :   &lt;pre lang="text"&gt; C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root
 &lt;/pre&gt;

&lt;p&gt;Deleted all folders in it... 
  &lt;br /&gt;..and IT WORKED! &lt;/p&gt;

&lt;p&gt;So note to self, next time IIS/ASP.NET starts behaving strange, try cleaning up the temp files first. &lt;/p&gt;</description>
  <author>test@example.com</author>
  <guid isPermaLink="false">http://ola.kodar.se/blog/aspnet-systemioioexception-the-file-or-directory-is-corrupted-and-unreadable/</guid>
  <pubDate>Sun, 25 Apr 2010 13:39:59 GMT</pubDate>
</item></channel>
</rss>