<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jq on Support Tools</title><link>https://support.tools/tags/jq/</link><description>Recent content in Jq on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 18 Nov 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://support.tools/tags/jq/index.xml" rel="self" type="application/rss+xml"/><item><title>Longhorn Volumes Stuck Degraded With Zero Rebuilds: rebuildRetryCount Exhaustion on Longhorn 1.12</title><link>https://support.tools/longhorn-degraded-volumes-rebuild-retry-count-exhausted/</link><pubDate>Wed, 18 Nov 2026 09:00:00 -0600</pubDate><guid>https://support.tools/longhorn-degraded-volumes-rebuild-retry-count-exhausted/</guid><description>&lt;p&gt;After a cluster-wide maintenance outage, every node was back, &lt;code&gt;Ready&lt;/code&gt;, and quiet. Cilium health checks were green. The network had been stable for hours. And 43 Longhorn volumes were still &lt;code&gt;degraded&lt;/code&gt;, with &lt;strong&gt;zero&lt;/strong&gt; replicas rebuilding, an empty &lt;code&gt;status.rebuildStatus&lt;/code&gt; on every affected engine, and twelve volumes running on a single healthy replica. Nothing was wrong with the cluster anymore. Longhorn had simply stopped trying.&lt;/p&gt;&#10;&lt;p&gt;The cause was a single per-replica counter, &lt;code&gt;spec.rebuildRetryCount&lt;/code&gt;, that had climbed to its hard-coded ceiling of 5 during an hour of network flapping and then never came back down. The usual remedy (delete the failed replica and let Longhorn create a fresh one) did not work on Longhorn 1.12. A SUSE knowledge base article describing the downstream symptom offered a cleanup filter that, run as written on 1.12, would have deleted replicas that were actively rebuilding. This post walks through the diagnosis, the trap, the one-field fix, and the copy-paste commands to find the same condition on any cluster.&lt;/p&gt;</description></item></channel></rss>