<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ext4 on tsvinc</title>
		<link>https://tsvinc.dev/tags/ext4/</link>
		<description>Recent content in Ext4 on tsvinc</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://tsvinc.dev/tags/ext4/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Salvaging a dying disk by partitioning around the wound</title>
				<link>https://tsvinc.dev/posts/partition-around-the-wound/</link>
				<pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/partition-around-the-wound/</guid>
				<description>&lt;div class=&#34;tldr&#34;&gt;&#xA;  &lt;span class=&#34;tldr-label&#34;&gt;TL;DR&lt;/span&gt;&#xA;  &lt;code&gt;badblocks&lt;/code&gt; tells you &lt;em&gt;how many&lt;/em&gt; bad blocks; its &lt;code&gt;-o&lt;/code&gt; logfile tells you &lt;em&gt;where&lt;/em&gt;, and that changes the verdict. All 58 failures on this 8 TB drive sat in the first 5.23% of the platter. Partition past the wound, leave the damaged region unallocated, and the healthy 94.8% — about 6.7 TiB — goes back to work as disposable scratch space. Not for anything you&#39;d miss.&#xA;&lt;/div&gt;&#xA;&#xA;&lt;p&gt;Every &lt;code&gt;badblocks&lt;/code&gt; run leaves two artifacts, and the useful one is the file almost nobody opens. There&#39;s the summary line everyone reads:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
