<?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>Malaysia VMware Communities &#187; partition</title>
	<atom:link href="http://malaysiavm.com/blog/tag/partition/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2011 15:50:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>ESX host &#8220;/var&#8221; partition full</title>
		<link>http://malaysiavm.com/blog/esx-host-var-partition-full/</link>
		<comments>http://malaysiavm.com/blog/esx-host-var-partition-full/#comments</comments>
		<pubDate>Tue, 10 Feb 2009 14:49:13 +0000</pubDate>
		<dc:creator>jlchannel</dc:creator>
				<category><![CDATA[Server]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[full]]></category>
		<category><![CDATA[logrotate]]></category>
		<category><![CDATA[partition]]></category>
		<category><![CDATA[var]]></category>
		<category><![CDATA[vmkernel]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=867</guid>
		<description><![CDATA[While I was trying to create a new virtual machine from template, I&#8217;m getting an error message: Failed to deploy template: A general system occured: Failed to create journal file provider. I found the problem because of &#8220;/var&#8221; partition are running out of space. Damn! During my previous VMware ESX setup, the partition setup are [...]]]></description>
			<content:encoded><![CDATA[<p>While I was trying to create a new <a href="http://malaysiavm.com/blog/tag/virtualmachine">virtual machine</a> from <a href="http://malaysiavm.com/blog/tag/template">template</a>, I&#8217;m getting an <a href="http://malaysiavm.com/blog/tag/error">error</a> message: <strong>Failed to deploy template: A general system occured: Failed to create journal file provider</strong>.</p>
<p><a href="http://www.malaysiavm.com/images/vmerror-var-log-full.JPG" rel="shadowbox[sbpost-867];player=img;"><img src="http://www.malaysiavm.com/images/vmerror-var-log-full.JPG" alt="Var partition full" width="501" height="74" rel="shadowbox" /></a></p>
<p>I found the problem because of &#8220;<strong><em>/var</em></strong>&#8221; <a href="http://malaysiavm.com/blog/tag/partition">partition</a> are running out of space. Damn!</p>
<p>During my previous VMware <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> setup, the partition setup are configure as  <strong>DEFAULT </strong>which is<strong> 2G </strong>for<strong> &#8220;/var/log&#8221;.<br />
</strong></p>
<p><em>[root@esxserver root]# df -kh<br />
Filesystem            Size  Used Avail Use% Mounted on<br />
/dev/sda2             4.9G  2.1G  2.6G  45% /<br />
/dev/sda1              99M   28M   67M  30% /boot<br />
/dev/sda6             2.0G  496M  1.4G  27% /var/log</em></p>
<p>Normally, <em>/var</em> partition won&#8217;t be filled up easily(1st time encounter this problem) and for some reasons, total of 36 <em>/var/log/vmkernel*</em> related files are fully occupied the <em>/var</em> <a href="http://malaysiavm.com/blog/tag/partition">partition</a>.</p>
<p><span id="more-867"></span><br />
For avoid the similar incident, I make a changes on <em>/etc/logrotate.d/<a href="http://malaysiavm.com/blog/tag/vmkernel">vmkernel</a></em> file.</p>
<p><em>/var/log/vmkernel{<br />
create 0600 root root<br />
missingok<br />
<strong>compress</strong> (originally nocompress)<br />
# keep a history over 1 years.<br />
monthly<br />
<strong>rotate 12</strong> (originally 36 for 3 years)<br />
#   max log size of 200k  (thus limiting total disk usage to under 8megs)<br />
size 200k<br />
sharedscripts<br />
postrotate<br />
/bin/kill -HUP `cat /var/run/syslogd.pid 2&gt; /dev/null` 2&gt; /dev/null || true<br />
endscript</em></p>
<p>Type <strong><em># <a href="http://malaysiavm.com/blog/tag/logrotate">logrotate</a> -f /etc/logrotate.d/vmkernel</em> </strong>and forced it run on the spot. </p>
<p>Personally I don&#8217;t think I need to keep vmkernel <a href="http://malaysiavm.com/blog/tag/log">log</a> files for more than a year and for space concern, I would prefer compress/<a href="http://malaysiavm.com/blog/tag/zip">zip</a> it. Again, the same logrotate option may apply to others log files.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/esx-host-var-partition-full/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.342 seconds -->

