From nobody Sun Oct 15 16:39:22 2023 X-Original-To: freebsd-hackers@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 4S7mDG3wSLz4x8V4 for ; Sun, 15 Oct 2023 16:39:26 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4S7mDF5bwVz4Qrg for ; Sun, 15 Oct 2023 16:39:25 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=kw7+FRze; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=v+xCsEfb; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.25 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 1E02B5C0293 for ; Sun, 15 Oct 2023 12:39:25 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 15 Oct 2023 12:39:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1697387965; x=1697474365; bh=85 YPfeWur7fmUktK76iOKXLgsx0uSxndMS6iNH5XFIU=; b=kw7+FRze8mJ6CKAK1a OAcHwFdYtKEBuf4QzMMrSVmaV/icb4oYmyoMpAjceJwV2qB94gZgZNhglidDeeXL W34toE83iYOkWlG1wrtPXRORzQmjwNNT4kCELe9WB+hCoeewEdxVeAPGvPgrfv6p UxP/mO3FgxAT27TgLHuiTv72Gsmn+MMvRQdUniCO0KuXBnbQg1CyEIFxsiJILkV8 xxhhNlAYxg7FvfH3wnioktz3bhpZYlkUa2hDMlg1fd2v1gM/m6LirKBbVoMaIbdV 26URNhnijIFbpxJDYaBXc5b5fIeYOXU/b3DdGV+n46b/LWjXHHuCUoIpSwpRgpSA +chA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1697387965; x=1697474365; bh=85YPfeWur7fmU ktK76iOKXLgsx0uSxndMS6iNH5XFIU=; b=v+xCsEfbUFQhAjEXYRMl7g02kATpu JwuhtX5riIQov0vF3wO0UTln+3fceQQWLEqFXKLJkbPnPdYfo3+y+XOPtPPsug7i 3bWm2q+hurm83jOPO7C3YBnlT+FKDvX/lWMrCj2GMfaC/2rYsH2NWxqUF4wegEv2 zUpIzoi2mUXIOTRTmRA4FkBpdaD+eUz3ZzewY+3kmyLBsGPiJ/+L5avzHBIsdy1n pdCoaZonxeGFgoiDHRJRutAPx6oTYmAko1BYLZQOYi9y33+DbmY+ZTa/vCrEtnwz tmZjPjY6YWUzXyQyth32FGYY7k7d0xuhzjIFpvZjWkyKvcT2Icu+1v6tg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrieekgdelkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertd dttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrght thgvrhhnpeekleduvdelhfeileefgffghfffkedtheellefgudfgvdegkeejjedutdehhe fgueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehv ohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 15 Oct 2023 12:39:24 -0400 (EDT) Date: Sun, 15 Oct 2023 17:39:22 +0100 From: void To: freebsd-hackers@freebsd.org Subject: Re: zpool geli encryption question Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.61 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.91)[-0.913]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.25:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.25:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; BLOCKLISTDE_FAIL(0.00)[66.111.4.25:server fail]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4S7mDF5bwVz4Qrg On Sun, Oct 15, 2023 at 07:17:57AM -0700, Alan Somers wrote: >How much of the FreeBSD VM's disk is actually in-use? (in the example below, another vm instance, same observation) from the host: NAME USED AVAIL REFER MOUNTPOINT ssdzfs/fbsd140Rv1 97.5G 309G 21.3G - within the booted vm: NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD zroot 74.8G 9.97G 0B 96K 0B 9.97G zroot/ROOT 74.8G 4.61G 0B 96K 0B 4.61G zroot/ROOT/default 74.8G 4.61G 0B 4.61G 0B 0B zroot/home 74.8G 59.6M 0B 59.6M 0B 0B zroot/tmp 74.8G 120K 0B 120K 0B 0B zroot/usr 74.8G 5.28G 0B 96K 0B 5.28G zroot/usr/ports 74.8G 5.28G 0B 5.28G 0B 0B zroot/usr/src 74.8G 96K 0B 96K 0B 0B zroot/var 74.8G 1.17M 0B 96K 0B 1.08M zroot/var/audit 74.8G 96K 0B 96K 0B 0B zroot/var/crash 74.8G 96K 0B 96K 0B 0B zroot/var/log 74.8G 564K 0B 564K 0B 0B zroot/var/mail 74.8G 252K 0B 252K 0B 0B zroot/var/tmp 74.8G 96K 0B 96K 0B 0B gzipped archive: -rw-r--r-- 1 root wheel 21G 15 Oct 16:39 2023.10.15_15:57.fbsd140Rv1.gz >Maybe you are using TRIM with FreeBSD, which punches holes in the host's ZFS >storage. On the bhyve host (14.0-BETA3 #0 releng/14.0-n265111) vfs.zfs.vdev.trim_min_active: 1 vfs.zfs.vdev.trim_max_active: 2 vfs.zfs.trim.queue_limit: 10 vfs.zfs.trim.txg_batch: 32 vfs.zfs.trim.metaslab_skip: 0 vfs.zfs.trim.extent_bytes_min: 32768 vfs.zfs.trim.extent_bytes_max: 134217728 vfs.zfs.l2arc.trim_ahead: 0 vfs.ffs.dotrimcons: 1 Does this mean trim is enabled and active on the host? I didn't set it. Maybe it was automatically set because zfs knows the hardware is SSD? > That would explain why compression seems to save space, even > though the data is encrypted. That's really smart. TYVM for the explainer. --