<?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: How to Repair and Defragment Linux System Partitions and Directories	</title>
	<atom:link href="https://www.tecmint.com/defragment-linux-system-partitions-and-directories/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/defragment-linux-system-partitions-and-directories/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Fri, 19 Dec 2025 18:50:15 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: atomick		</title>
		<link>https://www.tecmint.com/defragment-linux-system-partitions-and-directories/comment-page-1/#comment-2372116</link>

		<dc:creator><![CDATA[atomick]]></dc:creator>
		<pubDate>Fri, 19 Dec 2025 18:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=17272#comment-2372116</guid>

					<description><![CDATA[Not to break the ice here, but speaking from a historical perspective:

NIX systems never required these fixated habits that later became “&lt;strong&gt;mandatory&lt;/strong&gt;” (sorry, this is the truth of infiltration) If something cannot be owned, it gets destroyed. 

One of the best ways to change a habit is to relearn a few core gesture practices.

Never create directory or file names with spaces ever. Not anywhere. Not anytime. Not in file managers or terminal/shell operations.

Always use an underscore &lt;code&gt;(_)&lt;/code&gt; or a dash &lt;code&gt;(-)&lt;/code&gt; for naming.

Step outside the box for a nanosecond and ask yourself why you crossed over to the *NIX side of safer computing in the first place. This goes deep—deep enough to silence the old geezer chatter.

Check this in the shell:
&lt;pre&gt;
blkid -k
&lt;/pre&gt;
Look at how many filesystems are supported and recognized. Now compare that to the “&lt;strong&gt;other side&lt;/strong&gt;&quot;, which sticks to a single filesystem format (you all know that game). It eats space terribly and degrades physical devices over time. Unnecessary bloat. Unnecessary boot partitions.

&lt;strong&gt;LILO&lt;/strong&gt; and early &lt;strong&gt;GRUB&lt;/strong&gt; did not need this. &lt;strong&gt;GRUB2&lt;/strong&gt; is dynamic and designed to locate bootstrap data across multiple filesystem types.

Fill in the gaps. Change the habit. You will extend time-to-failure and reduce unnecessary overhead.

&lt;strong&gt;Again&lt;/strong&gt;: do not use spaces in names - ever—going forward.

The *NIX world is far happier without them. It avoids wasted inode indexing, lost cycles, and fragile parsing caused by space-based naming conventions.

You have been warned.

“They types will argue any way they can.” Let them. Change is safer than argument.

And remember who once said: “&lt;strong&gt;Users will never need more than 640K of memory on a home computer&lt;/strong&gt;”. Now look at the latest “&lt;strong&gt;11&lt;/strong&gt;” that requires an I-can’t-afford-that amount of memory just to run.]]></description>
			<content:encoded><![CDATA[<p>Not to break the ice here, but speaking from a historical perspective:</p>
<p>NIX systems never required these fixated habits that later became “<strong>mandatory</strong>” (sorry, this is the truth of infiltration) If something cannot be owned, it gets destroyed. </p>
<p>One of the best ways to change a habit is to relearn a few core gesture practices.</p>
<p>Never create directory or file names with spaces ever. Not anywhere. Not anytime. Not in file managers or terminal/shell operations.</p>
<p>Always use an underscore <code>(_)</code> or a dash <code>(-)</code> for naming.</p>
<p>Step outside the box for a nanosecond and ask yourself why you crossed over to the *NIX side of safer computing in the first place. This goes deep—deep enough to silence the old geezer chatter.</p>
<p>Check this in the shell:</p>
<pre>
blkid -k
</pre>
<p>Look at how many filesystems are supported and recognized. Now compare that to the “<strong>other side</strong>&#8220;, which sticks to a single filesystem format (you all know that game). It eats space terribly and degrades physical devices over time. Unnecessary bloat. Unnecessary boot partitions.</p>
<p><strong>LILO</strong> and early <strong>GRUB</strong> did not need this. <strong>GRUB2</strong> is dynamic and designed to locate bootstrap data across multiple filesystem types.</p>
<p>Fill in the gaps. Change the habit. You will extend time-to-failure and reduce unnecessary overhead.</p>
<p><strong>Again</strong>: do not use spaces in names &#8211; ever—going forward.</p>
<p>The *NIX world is far happier without them. It avoids wasted inode indexing, lost cycles, and fragile parsing caused by space-based naming conventions.</p>
<p>You have been warned.</p>
<p>“They types will argue any way they can.” Let them. Change is safer than argument.</p>
<p>And remember who once said: “<strong>Users will never need more than 640K of memory on a home computer</strong>”. Now look at the latest “<strong>11</strong>” that requires an I-can’t-afford-that amount of memory just to run.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: kar		</title>
		<link>https://www.tecmint.com/defragment-linux-system-partitions-and-directories/comment-page-1/#comment-1918970</link>

		<dc:creator><![CDATA[kar]]></dc:creator>
		<pubDate>Wed, 23 Nov 2022 17:40:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=17272#comment-1918970</guid>

					<description><![CDATA[Even though the filesystem prevents defragmenting. HDD operation is slowing down due to the dispersion of data, you still need to defragment regularly not for fragmentation but to bring files back in sequential order.]]></description>
			<content:encoded><![CDATA[<p>Even though the filesystem prevents defragmenting. HDD operation is slowing down due to the dispersion of data, you still need to defragment regularly not for fragmentation but to bring files back in sequential order.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: David Ganz		</title>
		<link>https://www.tecmint.com/defragment-linux-system-partitions-and-directories/comment-page-1/#comment-1295003</link>

		<dc:creator><![CDATA[David Ganz]]></dc:creator>
		<pubDate>Mon, 25 Nov 2019 21:01:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=17272#comment-1295003</guid>

					<description><![CDATA[Very Useful article! Many thanks...]]></description>
			<content:encoded><![CDATA[<p>Very Useful article! Many thanks&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: inukaze		</title>
		<link>https://www.tecmint.com/defragment-linux-system-partitions-and-directories/comment-page-1/#comment-980665</link>

		<dc:creator><![CDATA[inukaze]]></dc:creator>
		<pubDate>Sun, 08 Apr 2018 02:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=17272#comment-980665</guid>

					<description><![CDATA[Conclusion : you are assuming all users on the internet reading this, are using &lt;strong&gt;&quot;ext4&quot;&lt;/strong&gt; filesystem, ignoring for complete, exist another like : ext2, ext3, reiserfs, reiser4, jfs, xfs, zfs, btrfs, etc. and for each filesystem the def rag its different.

And in the title should be something like &quot;&lt;strong&gt;How to Repair and Defragment Linux ext4 Partitions&lt;/strong&gt;&quot;]]></description>
			<content:encoded><![CDATA[<p>Conclusion : you are assuming all users on the internet reading this, are using <strong>&#8220;ext4&#8221;</strong> filesystem, ignoring for complete, exist another like : ext2, ext3, reiserfs, reiser4, jfs, xfs, zfs, btrfs, etc. and for each filesystem the def rag its different.</p>
<p>And in the title should be something like &#8220;<strong>How to Repair and Defragment Linux ext4 Partitions</strong>&#8220;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Flo		</title>
		<link>https://www.tecmint.com/defragment-linux-system-partitions-and-directories/comment-page-1/#comment-823830</link>

		<dc:creator><![CDATA[Flo]]></dc:creator>
		<pubDate>Mon, 03 Oct 2016 06:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=17272#comment-823830</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/defragment-linux-system-partitions-and-directories/comment-page-1/#comment-823828&quot;&gt;Flo&lt;/a&gt;.

Oh and you did not update the text to include the mounting of the filesystem.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/defragment-linux-system-partitions-and-directories/comment-page-1/#comment-823828">Flo</a>.</p>
<p>Oh and you did not update the text to include the mounting of the filesystem.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
