<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ZFS on Support Tools</title><link>https://support.tools/tags/zfs/</link><description>Recent content in ZFS on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://support.tools/tags/zfs/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenZFS Block Cloning in Production: BRT Internals, the 2.2 Corruption Incident, and Safe Rollout</title><link>https://support.tools/openzfs-block-cloning-brt-internals-corruption-incident-safe-rollout/</link><pubDate>Wed, 29 Jul 2026 09:00:00 -0500</pubDate><guid>https://support.tools/openzfs-block-cloning-brt-internals-corruption-incident-safe-rollout/</guid><description>&lt;p&gt;Copying a 21 GiB virtual machine image on a pool with block cloning enabled finishes in about a quarter of a second and consumes no additional space. The copy is a real, independent file: it has its own inode, its own permissions, and its own future. It simply points at the same on-disk blocks as the original until one of them is modified. This is &lt;strong&gt;block cloning&lt;/strong&gt;, the OpenZFS implementation of what XFS, Btrfs, and Windows ReFS call a reflink, and it is one of the highest leverage storage features available to anyone running VM fleets, container image caches, or backup pipelines.&lt;/p&gt;&#10;&lt;p&gt;It is also the feature that shipped enabled by default in OpenZFS 2.2.0, silently corrupted files for a subset of users, got emergency-disabled in 2.2.1, and then spent the better part of two years switched off by default while the project rebuilt confidence in it. That history is not a reason to avoid block cloning. It is a reason to understand exactly what it does, which version floor is safe, how to verify it is actually engaging, and where the savings quietly evaporate. This guide covers the mechanism, the incident, and the operational practices that make it safe to turn on.&lt;/p&gt;</description></item><item><title>Complete Linux Filesystem and Partition Management Guide: Advanced Storage Administration for Enterprise Environments</title><link>https://support.tools/linux-filesystem-partition-management-guide/</link><pubDate>Tue, 25 Mar 2025 10:00:00 -0500</pubDate><guid>https://support.tools/linux-filesystem-partition-management-guide/</guid><description>&lt;p&gt;Linux filesystem and partition management represents a critical skillset for systems administrators managing enterprise storage infrastructure. This comprehensive guide covers traditional and modern storage technologies, advanced resizing techniques, enterprise-grade management practices, and automated solutions for production environments.&lt;/p&gt;</description></item><item><title>Create an Encrypted ZFS Pool on Linux (Native Encryption)</title><link>https://support.tools/how-to-create-encrypted-zfs-pool/</link><pubDate>Sun, 16 Feb 2025 01:00:00 -0500</pubDate><guid>https://support.tools/how-to-create-encrypted-zfs-pool/</guid><description>&lt;p&gt;This guide creates a ZFS pool with OpenZFS native encryption on Linux, unlocks it automatically at boot from a key file, and covers the tuning, monitoring and backup steps that matter once the pool holds real data.&lt;/p&gt;</description></item><item><title>How to grow a zvol in ZFS</title><link>https://support.tools/post/how-to-grow-a-zvol/</link><pubDate>Thu, 24 Jun 2021 23:58:00 +0000</pubDate><guid>https://support.tools/post/how-to-grow-a-zvol/</guid><description>&lt;p&gt;In ZFS, there are two types of filesystems (datasets and zvol). The ZFS dataset can be grown by setting the quota and reservation properties. But zvols have to extend by setting the volsize property to a new size.&lt;/p&gt;</description></item></channel></rss>