From nobody Tue Jul 6 23:01:25 2021 X-Original-To: freebsd-stable@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 7E8E611DC70C for ; Tue, 6 Jul 2021 23:01:37 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GKJ2m3sLXz3jfP; Tue, 6 Jul 2021 23:01:36 +0000 (UTC) (envelope-from pete@nomadlogic.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1625612487; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7IBLG7ASEsWDl92bcSOFtJPQdTZVAbzg6cFNbKmAjkI=; b=2f969ornikTFlR/GOYoynm00UOV7V7OqAjU3G4XFN48VyPlj1VGn4qLWHjXSBtG73ArrEu 6uRCOVIcZpzFeJXvqmXuO8nE3P7bF60BCP9zHC2WDuYev0bbTqzpcZiokuuTRCqWTK9RP0 eekkCeOUaMDkoLqeLOINfPeFahZD2dQ= Received: from [192.168.1.160] (cpe-24-24-163-126.socal.res.rr.com [24.24.163.126]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 4bdf87fd (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 6 Jul 2021 23:01:27 +0000 (UTC) Subject: Re: ZFS + mysql appears to be killing my SSD's To: Alan Somers , Pete French Cc: Stefan Esser , FreeBSD Stable Mailing List References: <89c37c3e-22e8-006e-5826-33bd7db7739e@ingresso.co.uk> <2fd9b7e4-dc75-fedc-28d7-b98191167e6b@freebsd.org> <9c71d627-55b8-2464-6cc9-489e4ce98049@ingresso.co.uk> Message-ID: <2e6dbe13-e08f-1dab-1f5b-76a90c3a2ea7@nomadlogic.org> Date: Tue, 6 Jul 2021 16:01:25 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4GKJ2m3sLXz3jfP X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=2f969orn; dmarc=pass (policy=quarantine) header.from=nomadlogic.org; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 66.165.241.226 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-3.57 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-0.57)[-0.575]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[66.165.241.226:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[nomadlogic.org:+]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.165.241.226:from]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable]; RCVD_COUNT_TWO(0.00)[2] Reply-To: pete@nomadlogic.org From: Pete Wright via freebsd-stable X-Original-From: Pete Wright X-ThisMailContainsUnwantedMimeParts: N On 7/5/21 7:51 AM, Alan Somers wrote: > > If you're using 4K sectors anyway, then GELI does not create any extra > write amplification. But if you're extra paranoid and you use the "-T" > option to "geli attach", then GELI will block TRIM commands. That could > hurt SSD lifetime. But I don't think "-T" is the default. You are using > 4K sectors, right? ZFS's ashift is set to 12? > -Alan > i also wonder if this could be a TRIM related issue.  according to zpoolprops(8) TRIM is not enabled by default on pools - but it also has this note (see autotrim): "Be aware that automatic trimming of recently freed data blocks can put significant stress on the underlying storage devices. This will vary depending of how well the specific device handles these commands.  For lower end devices it is often possible to achieve most of the benefits of automatic trimming by running an on-demand (manual) TRIM periodically using the zpool trim command." I wonder if adjusting the autotrim feature will address these issues - i manually enable autotrim for my pools and have seen no bad effects under quite of bit of bursty i/o.  if it is enabled i wonder if the ssd you are using doesn't play nice with autotrim and should stay disabled? -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA