<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linstor on Cozystack</title><link>https://deploy-preview-641--cozystack.netlify.app/topics/linstor/</link><description>Recent content in Linstor on Cozystack</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 04 Aug 2026 22:25:34 +0500</lastBuildDate><atom:link href="https://deploy-preview-641--cozystack.netlify.app/topics/linstor/index.xml" rel="self" type="application/rss+xml"/><item><title>Blockstor: a LINSTOR-compatible storage system for Kubernetes, written from scratch in Go</title><link>https://deploy-preview-641--cozystack.netlify.app/blog/2026/08/blockstor-linstor-compatible-storage-for-kubernetes/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-641--cozystack.netlify.app/blog/2026/08/blockstor-linstor-compatible-storage-for-kubernetes/</guid><description>&lt;figure&gt;&lt;img src="https://deploy-preview-641--cozystack.netlify.app/blog/2026/08/blockstor-linstor-compatible-storage-for-kubernetes/blockstor-announcement.png"
			alt="Blockstor — a LINSTOR-compatible storage system for Kubernetes, written from scratch in Go" width="720"&gt;
&lt;/figure&gt;

&lt;p&gt;The Cozystack team has open-sourced Blockstor, a control plane for block storage in Kubernetes: LVM and ZFS as backends, replication over DRBD, and a LINSTOR-compatible REST API. The project lives in the cozystack organization and is developed as part of Cozystack, a platform accepted into the CNCF Sandbox. The license is Apache 2.0.&lt;/p&gt;
&lt;p&gt;The main thing that makes it worth a look: it is not a fork, and it is not a wrapper. Blockstor is written from scratch in Go, but it speaks the same REST API as LINSTOR — so all the client tooling you already run keeps working without a single change: the &lt;code&gt;linstor&lt;/code&gt; CLI, linstor-csi, piraeus-operator, and the golinstor library.&lt;/p&gt;</description></item><item><title>How LINSTOR and DRBD Keep Your Data Alive When a Server Dies</title><link>https://deploy-preview-641--cozystack.netlify.app/blog/2026/07/linstor-drbd-replicated-storage/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-641--cozystack.netlify.app/blog/2026/07/linstor-drbd-replicated-storage/</guid><description>&lt;p&gt;&lt;img src="https://deploy-preview-641--cozystack.netlify.app/blog/2026/07/linstor-drbd-replicated-storage/linstor-drbd-replicated-storage.png" alt="DRBD synchronous block replication on Cozystack: a failed disk on one node while the volume stays online on the surviving replica node."&gt;&lt;/p&gt;
&lt;p&gt;Every bare-metal operator&amp;rsquo;s nightmare: a disk fails at 3 AM. If your storage is node-local (a &lt;code&gt;local-path&lt;/code&gt; or &lt;code&gt;hostPath&lt;/code&gt; volume pinned to one node), you&amp;rsquo;re restoring from backup and praying it&amp;rsquo;s recent. Ceph gives you replication but demands 3+ dedicated storage nodes, a PhD in CRUSH maps, and constant tuning. Most teams either over-invest in storage infrastructure or under-invest and pay the price in outages.&lt;/p&gt;</description></item></channel></rss>