From nobody Sun Mar 03 11:58:59 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TngND3lRLz5CfQg for ; Sun, 3 Mar 2024 11:59:08 +0000 (UTC) (envelope-from 4250.82.1d52800017886f2.4c58cf38fdf0ea4e027a37661ce6df57@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TngNC3f2cz4mvX for ; Sun, 3 Mar 2024 11:59:07 +0000 (UTC) (envelope-from 4250.82.1d52800017886f2.4c58cf38fdf0ea4e027a37661ce6df57@email-od.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=email-od.com header.s=dkim header.b=I0xuikIK; dmarc=none; spf=pass (mx1.freebsd.org: domain of 4250.82.1d52800017886f2.4c58cf38fdf0ea4e027a37661ce6df57@email-od.com designates 142.0.176.198 as permitted sender) smtp.mailfrom=4250.82.1d52800017886f2.4c58cf38fdf0ea4e027a37661ce6df57@email-od.com DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1709467148; x=1712059148; h=content-transfer-encoding:content-type:mime-version:message-id:subject:to:from:date:x-thread-info:subject:to:from:cc:reply-to; bh=B07ASu3WwRstQKXAEywyaH31wlepqQ77ZwntkDXG4c4=; b=I0xuikIKZGQujZGNsmt/BTZfiGyDKWesfoFoy8pYWylPyWHFJW1FILW6MZLXvJMN83MNE2wvPaAc2Iblcoi6zlpDpmKonlUYjkm+UoJ1JwxprZlCXn+1cejzvKIFsa8sCqIte9CwjUpTxQDMFPXi8wOXp5LVl1y7KJYSW+1rhKo= X-Thread-Info: NDI1MC4xMi4xZDUyODAwMDE3ODg2ZjIuZnJlZWJzZC1xdWVzdGlvbnM9ZnJlZWJzZC5vcmc= Received: from r3.h.in.socketlabs.com (r3.h.in.socketlabs.com [142.0.180.13]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sun, 3 Mar 2024 06:59:01 -0500 Received: from smtp.lan.sohara.org (EMTPY [185.202.17.215]) by r3.h.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sun, 3 Mar 2024 06:59:00 -0500 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.95 (FreeBSD)) (envelope-from ) id 1rgkUd-00010k-BS for freebsd-questions@freebsd.org; Sun, 03 Mar 2024 11:58:59 +0000 Date: Sun, 3 Mar 2024 11:58:59 +0000 From: Steve O'Hara-Smith To: freebsd-questions@freebsd.org Subject: ZFS pool/filesystem space oddity Message-Id: <20240303115859.922d34bb2f47b6df9093315a@sohara.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.1) X-Clacks-Overhead: "GNU Terry Pratchett" List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.70 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MV_CASE(0.50)[]; FORGED_SENDER(0.30)[steve@sohara.org,4250.82.1d52800017886f2.4c58cf38fdf0ea4e027a37661ce6df57@email-od.com]; R_DKIM_ALLOW(-0.20)[email-od.com:s=dkim]; R_SPF_ALLOW(-0.20)[+ip4:142.0.176.0/20]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7381, ipnet:142.0.176.0/22, country:US]; DMARC_NA(0.00)[sohara.org]; RCVD_COUNT_THREE(0.00)[3]; DWL_DNSWL_NONE(0.00)[email-od.com:dkim]; FROM_NEQ_ENVFROM(0.00)[steve@sohara.org,4250.82.1d52800017886f2.4c58cf38fdf0ea4e027a37661ce6df57@email-od.com]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; DKIM_TRACE(0.00)[email-od.com:+] X-Rspamd-Queue-Id: 4TngNC3f2cz4mvX Hi, My NAS runs a ZFS pool called archive striped over two mirrored pairs of 4TB drives. It all works fine but I had a space eater recently and so have been paying closer attention to space reports than normal - which is why I noticed the oddity that the filesystems in the pool are reported as having more free space than the pool. Why is this ? Which is right ? From zpool iostat -v capacity operations bandwidth pool alloc free read write read write ----------------- ----- ----- ----- ----- ----- ----- archive 4.38T 2.87T 59 52 880K 1.14M One of the filesystems in the archive pool: ✓ steve@holdall ~ $ df -H /data Filesystem Size Used Avail Capacity Mounted on archive/data 7.0T 4.0T 3.0T 57% /data -- Steve O'Hara-Smith