<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ssd on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ssd/</link>
    <description>Recent content in Ssd on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ssd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux SSD TRIM &amp; Block Discard Management: fstrim vs blkdiscard vs systemd Timer</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-linux-ssd-trim-block-discard-fstrim-blkdiscard-systemd-guide/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-linux-ssd-trim-block-discard-fstrim-blkdiscard-systemd-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Solid-state drives (SSDs) have become the standard storage medium for self-hosted servers, replacing spinning disks in everything from home labs to enterprise data centers. But unlike traditional hard drives, SSDs require proactive maintenance to sustain write performance over time. The key mechanism is &lt;strong&gt;TRIM&lt;/strong&gt; (also known as &lt;strong&gt;discard&lt;/strong&gt; in Linux terminology) — a command that informs the SSD controller which data blocks are no longer in use and can be erased internally.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
