<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: More Filesystem Foo</title>
	<atom:link href="http://pthree.org/2008/04/23/more-filesystem-foo/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2008/04/23/more-filesystem-foo/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Fri, 17 May 2013 20:46:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta2-24176</generator>
	<item>
		<title>By: Danyel Lawson</title>
		<link>http://pthree.org/2008/04/23/more-filesystem-foo/#comment-100253</link>
		<dc:creator>Danyel Lawson</dc:creator>
		<pubDate>Fri, 09 May 2008 18:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=573#comment-100253</guid>
		<description><![CDATA[For reiserfs you may want to make sure you haven&#039;t enabled notall in the mount options.  Tailing allows reiserfs to use variable block sizes.  Filling in the gaps between large files using big block sizes.]]></description>
		<content:encoded><![CDATA[<p>For reiserfs you may want to make sure you haven&#8217;t enabled notall in the mount options.  Tailing allows reiserfs to use variable block sizes.  Filling in the gaps between large files using big block sizes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: textshell</title>
		<link>http://pthree.org/2008/04/23/more-filesystem-foo/#comment-99056</link>
		<dc:creator>textshell</dc:creator>
		<pubDate>Fri, 25 Apr 2008 15:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=573#comment-99056</guid>
		<description><![CDATA[I think your test is not very good. Some filesystems reserve space for metadata at file system creation and count it all as used and some filesystems account for the metadata only if it&#039;s used. 
So if you want to test how good they manage space add files to the FS (as root to avoid 5% for root reserves and such things) with realistic average size (or size distribution) until you get no space left on device and compare the total size of all saved files. (using du without accounting for filesystem overhead)]]></description>
		<content:encoded><![CDATA[<p>I think your test is not very good. Some filesystems reserve space for metadata at file system creation and count it all as used and some filesystems account for the metadata only if it&#8217;s used.<br />
So if you want to test how good they manage space add files to the FS (as root to avoid 5% for root reserves and such things) with realistic average size (or size distribution) until you get no space left on device and compare the total size of all saved files. (using du without accounting for filesystem overhead)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sacha</title>
		<link>http://pthree.org/2008/04/23/more-filesystem-foo/#comment-98998</link>
		<dc:creator>Sacha</dc:creator>
		<pubDate>Thu, 24 Apr 2008 23:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=573#comment-98998</guid>
		<description><![CDATA[You do realise that the data you entered using &#039;dd&#039; took exactly the same space on each filesystem right? So what was the compare?

The only reason some filesystems have less used than others is because of the 5% reserved for root on ext2/ext3 and reiser filesystem. You can disable this using -m 0 when creating or tuning.

You attempted to compare but somehow your conclusion is that all filesystems are equal. Try enabling most compression possible on each filesystem (since you don&#039;t care about speed) and don&#039;t use &#039;dd&#039; to add data. Try pasting the linux kernel source on to there or something.

You&#039;ll find that reiser fs wins in such a benchmark (I have seen many of these before). It has a better compression.]]></description>
		<content:encoded><![CDATA[<p>You do realise that the data you entered using &#8216;dd&#8217; took exactly the same space on each filesystem right? So what was the compare?</p>
<p>The only reason some filesystems have less used than others is because of the 5% reserved for root on ext2/ext3 and reiser filesystem. You can disable this using -m 0 when creating or tuning.</p>
<p>You attempted to compare but somehow your conclusion is that all filesystems are equal. Try enabling most compression possible on each filesystem (since you don&#8217;t care about speed) and don&#8217;t use &#8216;dd&#8217; to add data. Try pasting the linux kernel source on to there or something.</p>
<p>You&#8217;ll find that reiser fs wins in such a benchmark (I have seen many of these before). It has a better compression.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hk47</title>
		<link>http://pthree.org/2008/04/23/more-filesystem-foo/#comment-98905</link>
		<dc:creator>hk47</dc:creator>
		<pubDate>Thu, 24 Apr 2008 12:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=573#comment-98905</guid>
		<description><![CDATA[Try:
$ tune2fs -m 0 /dev/mapper/test-ext2

That should give you roughly the same amount of free space on (a freshly created) ext2 as on vfat or xfs. Likewise for ext3 minus journal data.

You might be interested in reading this article, though it&#039;s from 2006:
http://www.debian-administration.org/articles/388]]></description>
		<content:encoded><![CDATA[<p>Try:<br />
$ tune2fs -m 0 /dev/mapper/test-ext2</p>
<p>That should give you roughly the same amount of free space on (a freshly created) ext2 as on vfat or xfs. Likewise for ext3 minus journal data.</p>
<p>You might be interested in reading this article, though it&#8217;s from 2006:<br />
<a href="http://www.debian-administration.org/articles/388" rel="nofollow">http://www.debian-administration.org/articles/388</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Binns</title>
		<link>http://pthree.org/2008/04/23/more-filesystem-foo/#comment-98888</link>
		<dc:creator>Roger Binns</dc:creator>
		<pubDate>Thu, 24 Apr 2008 09:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=573#comment-98888</guid>
		<description><![CDATA[Note that unix filesystems typically under report free space by 5% as that is reserved for root.  In any event a better test is to create a directory structure with numerous small files such as untarring linux kernel source (directories can take up quite a bit of space) and then see what is the largest file you can create in the remaining space (dd if=/dev/urandom of=/mnt/$i/foo.img) - using /dev/zero allows the filesystem to create sparse files taking up no space hence using urandom.]]></description>
		<content:encoded><![CDATA[<p>Note that unix filesystems typically under report free space by 5% as that is reserved for root.  In any event a better test is to create a directory structure with numerous small files such as untarring linux kernel source (directories can take up quite a bit of space) and then see what is the largest file you can create in the remaining space (dd if=/dev/urandom of=/mnt/$i/foo.img) &#8211; using /dev/zero allows the filesystem to create sparse files taking up no space hence using urandom.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
