<?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>Flexion.Org Blog &#187; blocks</title>
	<atom:link href="http://blog.flexion.org/tag/blocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.flexion.org</link>
	<description>Bad grammar and typos for total strangers</description>
	<lastBuildDate>Tue, 17 Jan 2012 17:01:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Recovering reserved space from ext4</title>
		<link>http://blog.flexion.org/2010/01/07/recovering-reserved-space-ext4/</link>
		<comments>http://blog.flexion.org/2010/01/07/recovering-reserved-space-ext4/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 20:42:04 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[blocks]]></category>
		<category><![CDATA[Ext3]]></category>
		<category><![CDATA[Ext4]]></category>
		<category><![CDATA[reserved]]></category>
		<category><![CDATA[space]]></category>

		<guid isPermaLink="false">http://blog.flexion.org/?p=302</guid>
		<description><![CDATA[The Ext4 file system, like Ext3, reserves 5% of the blocks on the file system for the root user. The reserved blocks are there for root&#8217;s use as a safe guard if the filesystem gets full, it provides some wiggle room to enable the really important programs to still function. But in some cases there&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<div class="socialize-in-content" style="float:right;"><div class="socialize-in-button socialize-in-button-vertical"><g:plusone size="tall" href="http://blog.flexion.org/2010/01/07/recovering-reserved-space-ext4/"></g:plusone></div><div class="socialize-in-button socialize-in-button-vertical"><iframe src="http://www.facebook.com/plugins/like.php?href=http://blog.flexion.org/2010/01/07/recovering-reserved-space-ext4/&amp;layout=box_count&amp;show_faces=false&amp;width=&amp;action=like&amp;font=arial&amp;colorscheme=light&amp;height=65" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:px !important; height:65px;" allowTransparency="true"></iframe></div><div class="socialize-in-button socialize-in-button-vertical"><a href="http://twitter.com/share" class="twitter-share-button" data-url="http://blog.flexion.org/2010/01/07/recovering-reserved-space-ext4/" data-text="Recovering reserved space from ext4" data-count="vertical" data-via="@flexiondotorg" data-related="@flexiondotorg"><!--Tweetter--></a></div><div class="socialize-in-button socialize-in-button-vertical"><script type="in/share" data-url="http://blog.flexion.org/2010/01/07/recovering-reserved-space-ext4/" data-counter="top"></script></div></div><p>The Ext4 file system, like Ext3, reserves 5% of the blocks on the file system for the root user. The reserved blocks are there for root&#8217;s use as a safe guard if the filesystem gets full, it provides some wiggle room to enable the really important programs to still function. But in some cases there&#8217;s not much point in having space reserved for root.</p>
<p>I&#8217;ve recently upgrade my workstation with a 6TB internal RAID 0 array for data storage (music, videos, photos, etc) and an external 6TB RAID 0 array as a backup. My OS boot from a 1TB drive. For my 6TB arrays I want the maximum available storage and was interested to see what effect removing the reserved space would have. So, this is what I did.</p>
<p>First I made the Ext4 file system, mounted it and queried how much space was available.</p>
<pre>sudo mkfs.ext4 /dev/sdh1
sudo mount /dev/sdh1 /mnt
df -h</pre>
<p>Looks like I have 5.1TB of available space.</p>
<pre>/dev/sdh1             5.4T  186M  5.1T   1% /mnt</pre>
<p>Then I unmounted the file system, removed the reserved blocks, checked the consistency of the file system, mounted it and queried how much space was available.</p>
<pre>sudo umount /mnt
sudo tune2fs -m 0 /dev/sdh1
sudo e2fsck /dev/sdh1
df -h</pre>
<p>Looks like I have 5.4TB available now, a saving of 300GB.</p>
<pre>/dev/sdh1             5.4T  186M  5.4T   1% /mnt</pre>
<p>Now, I could have simply created the files system without the reserved blocks in the first place, but I was interested to see the comparison.</p>
<pre>sudo mkfs.ext4 -m 0 /dev/sdh1</pre>
<p>Before you start removing the reserved blocks from your ext3/ext4 file systems do a bit a research first.</p>
<ul>
<li><a href="http://ubuntuforums.org/showthread.php?t=215177" target="_blank">Disk capacity, free space, and Ext3 reserved blocks</a></li>
<li><a href="http://wiki.archlinux.org/index.php/Ext3_Filesystem_Tips" target="_blank">Ext3 Filesystem Tips</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.flexion.org/2010/01/07/recovering-reserved-space-ext4/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

