<?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: Why FAT Filesystem Sucks</title>
	<atom:link href="http://www.firdouss.com/2007/01/why-fat-filesystem-sucks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.firdouss.com/2007/01/why-fat-filesystem-sucks/</link>
	<description>Random Sharing under the Sun</description>
	<lastBuildDate>Thu, 15 Jul 2010 19:12:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: anon</title>
		<link>http://www.firdouss.com/2007/01/why-fat-filesystem-sucks/#comment-528</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Tue, 26 Jun 2007 01:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.firdouss.com/2007/01/31/why-fat-filesystem-sucks/#comment-528</guid>
		<description>It&#039;s not a fragmentation issue.

The problem is with the cluster size of the filesystems. In Fird&#039;s case, his files are given blocks of 16 KiB to fill up. Even if the GIF/PNG only needs 100 bytes, it will still occupy 16 KiB of space because of how the disk space is allocated.

8189 files * 16,384 bytes = 134,168,576 bytes

Throw in the overhead for the 73 directories and you&#039;ll have the disk space used.

FAT/FAT32 works fine with small disk space sizes, but they suck when trying to handle disk spaces of above 512 MiB and thousands of tiny files. It&#039;s better to use NTFS or other modern file systems.

Digital cameras can still use FAT/FAT32 efficiently because the photos are huge - the overhead of wasted disk space isn&#039;t as noticeable as having thousands of tiny icons.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not a fragmentation issue.</p>
<p>The problem is with the cluster size of the filesystems. In Fird&#8217;s case, his files are given blocks of 16 KiB to fill up. Even if the GIF/PNG only needs 100 bytes, it will still occupy 16 KiB of space because of how the disk space is allocated.</p>
<p>8189 files * 16,384 bytes = 134,168,576 bytes</p>
<p>Throw in the overhead for the 73 directories and you&#8217;ll have the disk space used.</p>
<p>FAT/FAT32 works fine with small disk space sizes, but they suck when trying to handle disk spaces of above 512 MiB and thousands of tiny files. It&#8217;s better to use NTFS or other modern file systems.</p>
<p>Digital cameras can still use FAT/FAT32 efficiently because the photos are huge &#8211; the overhead of wasted disk space isn&#8217;t as noticeable as having thousands of tiny icons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Albert Ng</title>
		<link>http://www.firdouss.com/2007/01/why-fat-filesystem-sucks/#comment-527</link>
		<dc:creator>Albert Ng</dc:creator>
		<pubDate>Tue, 27 Feb 2007 17:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.firdouss.com/2007/01/31/why-fat-filesystem-sucks/#comment-527</guid>
		<description>Another trick I like to do, especially to big fragmented files, is to move them to another drive, then move it back. It will most likely be defragmented.</description>
		<content:encoded><![CDATA[<p>Another trick I like to do, especially to big fragmented files, is to move them to another drive, then move it back. It will most likely be defragmented.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
