From 9231611746dbd8a26179a159a30d26354aa6d26f Mon Sep 17 00:00:00 2001 From: Afonso Jorge Ramos Date: Thu, 20 Aug 2026 14:23:12 +0200 Subject: [PATCH] docs(truenas): clarify how storage values are derived --- apps/docs/docs/integrations/truenas/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/docs/integrations/truenas/index.mdx b/apps/docs/docs/integrations/truenas/index.mdx index 5e57f3a89..00f8f0093 100644 --- a/apps/docs/docs/integrations/truenas/index.mdx +++ b/apps/docs/docs/integrations/truenas/index.mdx @@ -27,7 +27,7 @@ import Alert from '@theme/Admonition'; ]} /> -The storage values shown by these widgets use the root ZFS dataset's usable `used` and `available` space, including RAIDZ parity overhead and dataset limits. +The storage values shown by these widgets come from each pool's root ZFS dataset, so they already account for RAIDZ parity overhead and dataset limits and match what `zfs list` and the TrueNAS web interface report. When a pool cannot report its dataset space, Homarr falls back to the pool's physical values, which read higher on RAIDZ. ### Adding the integration