From nobody Mon Aug 28 19:00:30 2023 X-Original-To: freebsd-current@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 4RZKdr33Gbz4rrXG for ; Mon, 28 Aug 2023 19:01:04 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-yw1-x112c.google.com (mail-yw1-x112c.google.com [IPv6:2607:f8b0:4864:20::112c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RZKdr2Z6tz3Ygg for ; Mon, 28 Aug 2023 19:01:04 +0000 (UTC) (envelope-from mavbsd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-5924093a9b2so42601167b3.2 for ; Mon, 28 Aug 2023 12:01:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693249263; x=1693854063; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=iXIal3U5iWlvwODxkpglXMdrPBJiF7CLQ+tAFbbzBRw=; b=P5SXWW16uaXhii5WvIZTC2iKHCmRiTKzUefjbhzpv8Fu1jr/mfkmaZhgiHzv/LmjKj onlZnyp7X0suOp7Ac2CsYsq+AmKwJTuvAhfiUgr0cmThyhiAYQ1c1uMcgNvoe1giEr4x 0E6CEFlkB2T/r3YZ/iN6PsXm50F2y1zUs894+BxYwOlQ4V5ylTwTUaGS2BB4RhKBi06S wYkJgK9Q8aX4IzqlH9jE/BcbseBkSm8SL7eSsiT7uiegwOg7zdSDRU64HaY40LLgtQVJ jbV6T25x6CnFPyyV9kIuzxu3n6fbPPw+mbWjIdyKXwMXl/5muNdpizyPcA/N78UhAVqT J2kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693249263; x=1693854063; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iXIal3U5iWlvwODxkpglXMdrPBJiF7CLQ+tAFbbzBRw=; b=QCTekd7YqSYvi8mI5mXGBwD+YztkyYiYYe/aZgg3u+OE5P0X0aCUmBdKlFmjMpz6xT e2IitNLfMD2HO79o6qNfuX59psHXaPipeSYpPU3GmSf1YgvcqD7YnFy/mMJlloREdIkN lRa+V8k/AO2EQpUiehr2kYUK6lJ5yQjAHRD7o/bdJJ78VTi9KOtoZGNVY+GNHDv9LiC6 Zcz7KX4kfBci44U/jbOGhc0RJNUeFmw7qqPbt6KZ3A+Rtr0786Qj7BWqvpgjwBZTXeT2 4HMipA3c0prOlh7VmzKFhrU05PPoGq4QIuCdPr/FAoRngC1FXrFx8Lo2KHxaGD1DzzBn B9yQ== X-Gm-Message-State: AOJu0Ywp+9FfpZINrNPdAyY1rJX9ADomZiHnERztrGVKK9rXKKNEVaer eFq44puVQEW1yIh+Ii2yk67PtE8l5Fk= X-Google-Smtp-Source: AGHT+IFL4K315YyvgnALyjNqMwCHK4e6DnbMonxKM6e1AL+Qo7beEMNxOMMZdyyxEUaMFquddrTFWw== X-Received: by 2002:a0d:f183:0:b0:58f:bda3:8dd with SMTP id a125-20020a0df183000000b0058fbda308ddmr27916442ywf.32.1693249263384; Mon, 28 Aug 2023 12:01:03 -0700 (PDT) Received: from [10.230.45.5] ([38.32.73.2]) by smtp.gmail.com with ESMTPSA id en4-20020a05690c2b8400b0059565f338b2sm114963ywb.98.2023.08.28.12.01.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Aug 2023 12:01:03 -0700 (PDT) Message-ID: <21ef6e61-8985-9c62-b400-fe4200063e35@FreeBSD.org> Date: Mon, 28 Aug 2023 15:00:30 -0400 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: zfs autotrim default to off now Content-Language: en-US To: Pete Wright , freebsd-current@freebsd.org References: From: Alexander Motin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4RZKdr2Z6tz3Ygg On 28.08.2023 13:56, Pete Wright wrote: > So to be clear, if we were using the default autotrim=enabled behavior > we in fact weren't having our SSDs trimmed?  I think that's my concern, > as an admin I was under the impression that it was enabled by default > but apparently that wasn't actually happening. We wanted autotrim to be enabled by default, but it was not enabled, and it was reported as not enabled, so there should be no confusion. The only confusion may have been if you tried to read the code and see it should have been enabled. -- Alexander Motin