<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Storage on Packets &amp; Regrets</title><link>https://matijazezelj.github.io/packets-and-regrets/tags/storage/</link><description>Recent content in Storage on Packets &amp; Regrets</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 19 Jul 2026 19:30:00 +0200</lastBuildDate><atom:link href="https://matijazezelj.github.io/packets-and-regrets/tags/storage/index.xml" rel="self" type="application/rss+xml"/><item><title>Prometheus on NFS: Healthy Until It Wasn't</title><link>https://matijazezelj.github.io/packets-and-regrets/posts/prometheus-on-nfs-healthy-until-it-wasnt/</link><pubDate>Sun, 19 Jul 2026 19:30:00 +0200</pubDate><guid>https://matijazezelj.github.io/packets-and-regrets/posts/prometheus-on-nfs-healthy-until-it-wasnt/</guid><description>&lt;p&gt;The monitoring page was green. The container was healthy. Queries worked.&lt;/p&gt;
&lt;p&gt;The storage design was still wrong.&lt;/p&gt;
&lt;p&gt;I had put the Prometheus time-series database on an NFS share. It was roomy, already mounted, and moved roughly 30 GiB away from a Docker VM whose local disk was tight. This seemed like a reasonable home-lab compromise right up to the moment the NAS stopped answering.&lt;/p&gt;
&lt;p&gt;Then Prometheus became the incident it was supposed to help explain.&lt;/p&gt;</description></item></channel></rss>