<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>cyborgworkshop.org &#187; disk</title>
	<atom:link href="http://cyborgworkshop.org/tag/disk/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyborgworkshop.org</link>
	<description>Blurring the line</description>
	<lastBuildDate>Wed, 22 Feb 2012 14:31:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Ubuntu unstable on ESXi</title>
		<link>http://cyborgworkshop.org/2008/11/21/ubuntu-unstable-on-esxi/</link>
		<comments>http://cyborgworkshop.org/2008/11/21/ubuntu-unstable-on-esxi/#comments</comments>
		<pubDate>Fri, 21 Nov 2008 21:18:12 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[argh]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[scsi]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[unstable]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=179</guid>
		<description><![CDATA[I&#8217;m having some serious stability issues with all of my ubuntu VMs on ESXi. After a period of several days, they have all locked up with a message about the mtp driver having read errors, or something along those lines. The short summary is that it looks like the scsi disk (emulated by ESXi, actually [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m having some serious stability issues with all of my ubuntu VMs on ESXi. After a period of several days, they have all locked up with a message about the mtp driver having read errors, or something along those lines. The short summary is that it looks like the scsi disk (emulated by ESXi, actually an iscsi LUN) becomes unavailable and lots of sense key errors are generated. The VM goes to 100% CPU and I have to reboot the entire ESXi server to recover. In the meantime, my SAN, Fedora, Solaris and Windows VMs never skip a beat.  I&#8217;ve rebuilt the VM several times with different version of ubuntu in the 8.x line and different patch revisions, but have finally gave up. I&#8217;m back on Fedora and we&#8217;ll see if it remains stable.</p>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2008/11/21/ubuntu-unstable-on-esxi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quck command to find which filesystems are greater then 90%</title>
		<link>http://cyborgworkshop.org/2008/04/22/quck-command-to-find-which-filesystems-are-greater-then-90/</link>
		<comments>http://cyborgworkshop.org/2008/04/22/quck-command-to-find-which-filesystems-are-greater-then-90/#comments</comments>
		<pubDate>Tue, 22 Apr 2008 14:00:31 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[du]]></category>
		<category><![CDATA[filesystem]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=37</guid>
		<description><![CDATA[While I have a good monitoring system setup, some of my nodes can&#8217;t be monitored and require manual checkups. To speed things up, I use a little bash script to log into each host and check a few things out. This snippit below walks through each host in my host file and prints out file [...]]]></description>
			<content:encoded><![CDATA[<p>While I have a good monitoring system setup, some of my nodes can&#8217;t be monitored and require manual checkups. To speed things up, I use a little bash script to log into each host and check a few things out. This snippit below walks through each host in my host file and prints out file systems that are at greater then 90% utilization.</p>
<blockquote><p>for i in `cat /etc/hosts | grep -v localhost | awk {&#8216;print $3&#8242;}`; do<br />
   echo $i;<br />
   ssh $i &#8220;df -k | sed 1d | awk &#8216;\$5>90 {print}&#8217;&#8221;;<br />
done</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2008/04/22/quck-command-to-find-which-filesystems-are-greater-then-90/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting the number of used inodes</title>
		<link>http://cyborgworkshop.org/2008/04/21/getting-the-number-of-used-inodes/</link>
		<comments>http://cyborgworkshop.org/2008/04/21/getting-the-number-of-used-inodes/#comments</comments>
		<pubDate>Mon, 21 Apr 2008 14:00:57 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[inodes]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=36</guid>
		<description><![CDATA[I won&#8217;t go into the details of what inodes are and why they are important, but when you run out of them, you can have all of the free disk space in the world and not be able to do a darn thing with it. An easy way to see how many inodes are being [...]]]></description>
			<content:encoded><![CDATA[<p>I won&#8217;t go into the details of what inodes are and why they are important, but when you run out of them, you can have all of the free disk space in the world and not be able to do a darn thing with it.  An easy way to see how many inodes are being used on a linux system is with the df command</p>
<blockquote><p>df -i</p></blockquote>
<p>This will show you the number of inodes allocated to a file system and the number that are free.  Likewise in solaris, the command is df but you use a different option to get the same information.</p>
<blockquote><p>df -o i</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2008/04/21/getting-the-number-of-used-inodes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

