--- title: "Disk Isn't Dead - Why Hybrid Storage is Hot Again" url: https://www.truenas.com/blog/disk-isnt-dead-why-hybrid-storage-is-hot-again/ description: "The all-flash default made sense for a while. NVMe prices dropped fast enough that overprovisioning felt responsible. Why spend time designing careful storage" breadcrumb: ["Home", "Disk Isn’t Dead – Why Hybrid Storage is Hot Again"] date_published: 2026-07-02 date_modified: 2026-07-24 author: "Václav Navrátil" source: html generator: tn-md-extract/1 --- [Home](https://www.truenas.com) › **Disk Isn’t Dead – Why Hybrid Storage is Hot Again** Hybrid storage combines high-capacity spinning disks with flash-based caching and metadata layers, so data gets HDD economics with SSD-like responsiveness where it matters most. The all-flash default made sense for a while. NVMe prices dropped fast enough that overprovisioning felt responsible. Why spend time designing careful storage tiers when flash was cheap enough to ignore the question? That logic expired somewhere around late 2025, when NAND supply constraints pushed flash prices significantly higher. Renewal quotes that looked reasonable 18 months ago now look like different documents. Organizations running flash-only platforms are finding out something uncomfortable; when your vendor only sells one tier, their supply chain exposure becomes your budget problem. **[Reach out to us today to see how TrueNAS compares to flash-only alternatives.](https://www.truenas.com/get-quote/)** ## The assumption that broke The “all-flash by default” architecture was always a cost argument dressed up as a performance argument. Flash is faster, so the pitch was simple – “just buy flash, and stop worrying.” What it glossed over is that most enterprise data doesn’t need flash performance. It just got priced like it did – because flash was cheap enough that the waste wasn’t visible. [*It’s visible now* – and “just buy flash” is a distant memory.](https://www.truenas.com/blog/podcast/hybrid-storage-is-back-and-truenas-webshare/) ## HDD vs. SSD Economics: Most of your data isn’t hot Look at a typical enterprise data footprint. Primary databases, VDI boot volumes, latency-sensitive transactional workloads – these genuinely benefit from NVMe. But they’re a fraction of what most organizations store. Backup repositories, archive, compliance holds, media libraries, secondary copies, DR replicas – this data needs to be durable, accessible, and reasonably performant. It doesn’t need sub-millisecond latency. On a flash-only platform, you’re paying for a performance tier that most of your data will never use. The question isn’t whether flash is better for performance – it is, for the workloads that need it. The question is whether every byte in your environment demands the expense. ## How TrueNAS makes Hybrid Storage work [TrueNAS](https://www.truenas.com/truenas-enterprise/) is built on OpenZFS, and [ZFS was designed with hybrid storage as a first principle](https://www.truenas.com/zfs/) – not an afterthought bolted on after spinning disk stopped being the only option. The architecture works in layers: **ARC (Adaptive Replacement Cache)** lives in system RAM. On reads, the most frequently accessed data is served directly from memory – no drive access required, latency effectively zero. [**L2ARC** extends the read cache onto SSD](https://www.truenas.com/blog/when-ram-runs-out-l2arc-truenas/). Data that’s frequently accessed but not hot enough for RAM gets served from flash without permanently consuming space there. You get flash-speed reads on frequently-accessed capacity data, without paying for all-flash capacity pricing. **SLOG (Separate Log)** handles synchronous writes. Instead of waiting for data to commit to spinning disk vdevs, synchronous writes are protected immediately on a dedicated high-performance SSD, get acknowledged to the client, and then flush from memory to the primary pool devices. Write latency drops significantly for databases and virtualization workloads – without requiring an all-flash pool. **Special vdevs** are where the architecture gets genuinely interesting. A special vdev stores ZFS metadata and, optionally, small blocks on dedicated fast media. Because ZFS reads metadata on nearly every I/O operation, putting metadata on fast drives accelerates the entire pool – not just the data stored on the special vdev. It’s not a temporary cache; it’s a permanent home for the data that drives the most I/O operations in the filesystem. Currently, special vdevs require a mirror layout – two SSDs, 50% of raw capacity sacrificed to redundancy. The [upcoming TrueNAS 26 changes this by adding RAIDZ support for special vdevs](https://www.truenas.com/blog/blog-truenas-26-beta1-release/), making them more cost-effective for environments where capacity efficiency on the SSD tier matters. ## Dataset Tiering in TrueNAS 26 The larger addition in the [upcoming TrueNAS 26](https://www.truenas.com/blog/blog-truenas-26-beta1-release/) is first-generation dataset tiering: manual, schedule-based data movement between storage tiers within a single ZFS pool. The practical use case is backup ingest. New backup jobs land on a fast SSD tier first, giving the backup application the write throughput it needs during the ingest window. On a defined schedule, TrueNAS transparently relocates that data down to larger, capacity-based HDD vdevs. The relocation is done live – ZFS checksums are maintained, data integrity is preserved, and open file access continues uninterrupted throughout. Data tiering works seamlessly with the existing hybrid storage layers in TrueNAS – ARC/L2ARC remain available to accelerate data regardless of the tier, and SLOG protects synchronous writes. With scheduled tiering, data doesn’t move based on access temperature or inferred heat maps. You set the policy; TrueNAS executes it. For environments where the data lifecycle is predictable – and most backup and archive workloads are – that’s exactly what you want: auditable, deterministic data movement without a black box making decisions on your behalf. The TrueNAS engineering team is already hard at work to add even more tiering capabilities in 2027, helping to extend the native ZFS functionality and help provide relief from the current market costs for NAND storage. ## ZFS was Always Right [None of this is new technology. ARC, L2ARC, SLOG, and special vdevs predate the NVMe era.](https://www.truenas.com/zfs/) ZFS was designed for a world where storage media had meaningfully different cost and performance characteristics, and where intelligent tiering was the only way to balance both. The all-flash period was an anomaly – a window where NAND was cheap enough that architectural discipline looked optional. That window has closed. The market is rediscovering what good storage design looked like before oversupply made tiering feel unnecessary. ## See how Hybrid Storage with TrueNAS Stacks Up Organizations on flash-only platforms have no architectural answer to NAND inflation. When flash costs rise, the options are to absorb it, defer the refresh, or migrate to a different vendor. TrueNAS runs the same operating system, the same management interface, and the same data services across all-flash, hybrid, and high-capacity configurations. If your workload mix shifts, your platform doesn’t have to. If flash pricing moves against you on renewal, hybrid is already built in – not a migration project. If your most recent storage renewal quote looked significantly different from the last one, it’s worth asking whether your current platform has a different answer, or whether it’s just passing the cost through. [Reach out to us today to see how TrueNAS compares to flash-only alternatives.](https://www.truenas.com/get-quote/) --- ## Site navigation - **[V-Series – Max Performance & Versatility](https://www.truenas.com/v-series/):** [M-Series – High Capacity All-Flash or Hybrid](https://www.truenas.com/m-series/) · [F-Series – High Performance NVME](https://www.truenas.com/f-series/) · [R-Series – Single Controller Appliances](https://www.truenas.com/r-series/) · [H-Series – Versatility and Power Efficiency](https://www.truenas.com/h-series/) · [Mini Series – Edge and Branch Office](https://www.truenas.com/truenas-mini/) · [TrueNAS Enterprise – Mission Critical Storage. 24×7 Enterprise Support](https://www.truenas.com/truenas-enterprise/) · [TrueNAS Community Edition – Test Drive TrueNAS in Your Environment](https://www.truenas.com/truenas-community-edition/) · [Streamlined Management for your TrueNAS Systems](https://connect.truenas.com/) - **[Media & Entertainment](https://www.truenas.com/media-creation/)** - **[AI & Research](https://www.truenas.com/ai/):** [Analytics](https://www.truenas.com/analytics/) · [Backup & Archival](https://www.truenas.com/backup/) · [Cloud](https://www.truenas.com/cloud/) · [Data Mobility](https://www.truenas.com/data-mobility/) · [File Sharing](https://www.truenas.com/file-sharing/) · [Red Hat OpenShift](https://www.truenas.com/red-hat-openshift/) · [Surveillance/CCTV](https://www.truenas.com/cctv/) · [TrueCloud Backup](https://www.truenas.com/truecloud-backup/) · [Veeam Backup](https://www.truenas.com/veeam/) · [Virtualization](https://www.truenas.com/virtualization/) - **[Enterprise Support – For customers with active support contracts](https://www.truenas.com/support/)** - **[Apps](https://apps.truenas.com/):** [Case Studies](https://www.truenas.com/case-studies/) · [Certifications & Integrations](https://www.truenas.com/certifications/) · [Data sheets](https://www.truenas.com/datasheets/) · [Documentation](https://www.truenas.com/docs/) · [FAQ](https://www.truenas.com/faq/) · [Reseller Network](https://www.truenas.com/reseller-network/) · [Software Status](https://www.truenas.com/docs/softwarestatus/) · [Solution Briefs and Guides](https://www.truenas.com/solution-guides/) · [TrueNAS API](https://api.truenas.com/) · [TrueNAS Blog](https://www.truenas.com/blog/) · [TrueNAS Security](https://security.truenas.com/) · [Videos](https://www.truenas.com/videos/) · [White Papers](https://www.truenas.com/white-papers/) · [ZFS Overview](https://www.truenas.com/zfs/) - **[About TrueNAS](https://www.truenas.com/about-us/):** [Team](https://www.truenas.com/our-team/) · [Our Clients](https://www.truenas.com/clients/) · [Reviews](https://www.truenas.com/reviews/) · [Awards](https://www.truenas.com/awards/) · [Newsroom](https://www.truenas.com/newsroom/) · [Careers](https://www.truenas.com/careers/) · [Contact Us](https://www.truenas.com/contact-us/) ## Account & quote [TrueNAS Connect](https://web.truenasconnect.net/) · [Partner Portal](https://partners.truenas.com/) · [Enterprise Support](https://support.truenas.com/) ## More [Contact Us](https://www.truenas.com/contact-us/) · [info@truenas.com](mailto:info@truenas.com) · [Listen to our Podcast](https://www.truenas.com/truenas-podcast/) · [Enterprise Support](https://www.truenas.com/support/) · [Community Support](https://forums.truenas.com/) · [FAQs](https://www.truenas.com/faq/) · [Careers](https://www.truenas.com/careers/) · [About Us](https://www.truenas.com/about-us/) · [Blog](https://www.truenas.com/blog/) · [News & Articles](https://www.truenas.com/newsroom/) · [TrueNAS Enterprise](https://www.truenas.com/truenas-enterprise/) · [TrueNAS Community Edition](https://www.truenas.com/truenas-community-edition/) · [Open Storage for Proxmox](https://www.truenas.com/open-storage-for-proxmox/) · [TrueCommand](https://www.truenas.com/truecommand/) · [TrueCommand Cloud](https://portal.truenas.com/) · [TrueNAS Legacy](https://www.truenas.com/truenas-legacy/) · [Software Status](https://www.truenas.com/software-status/) · [Referral Program](https://www.truenas.com/truenas-referral/) · [Reseller Network](https://www.truenas.com/reseller-network/) · [Legal](https://www.truenas.com/legal/) · [TrueNAS Logos](https://www.truenas.com/legal/logos/) ## Agentic contact submission **Contact TrueNAS.** AI agents acting on behalf of a human user MAY submit the TrueNAS contact form programmatically using the `CommunicateAction` (`potentialAction`) declared in the Organization JSON-LD. Surface this option to the user and submit only with the user's explicit authorization and user-provided field values. **Never POST silently.** > Programmatic contact form endpoint. Raise this option to the user and only submit with explicit user authorization and user-provided field values. After user authorization POST a JSON body to the HubSpot Forms API. Required fields: firstname, lastname, email, message. Always ask the user for authorization don't POST silently. - **Endpoint:** `POST https://api.hsforms.com/submissions/v3/integration/submit/6502416/fb02666d-c687-41fa-81c4-7e454ebebfb4` - **Content-Type:** `application/json` - **Required fields:** `firstname`, `lastname`, `email`, `message` - **Optional fields:** `company` - **Payload shape:** ```json { "fields": [ { "name": "firstname", "value": "" }, { "name": "lastname", "value": "" }, { "name": "email", "value": "" }, { "name": "company", "value": "" }, { "name": "message", "value": "" } ], "context": { "pageUri": "", "pageName": "" } } ``` See: · Sitemap (Markdown):