From owner-freebsd-stable@freebsd.org Tue Feb 25 14:14:34 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DC99725CAF8 for ; Tue, 25 Feb 2020 14:14:34 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.21.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp-sofia.digsys.bg", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48Rgt05Tzyz3G1P for ; Tue, 25 Feb 2020 14:14:32 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from [193.68.6.100] ([193.68.6.100]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.15.2/8.15.2) with ESMTPSA id 01PEESQY029905 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 25 Feb 2020 16:14:29 +0200 (EET) (envelope-from daniel@digsys.bg) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Subject: Re: Running FreeBSD on M.2 SSD From: Daniel Kalchev In-Reply-To: <1821830b-e43f-b23a-49d6-e1a2d1e4aa83@ingresso.co.uk> Date: Tue, 25 Feb 2020 16:14:28 +0200 Cc: Mario Olofo , freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <202002250115.01P1F9KX090465@mail.karels.net> <188F34DA-192C-4D44-96B5-18A7DAE8EC67@digsys.bg> <6028c786-8610-01d9-818e-6f69a2fe9645@ingresso.co.uk> <1821830b-e43f-b23a-49d6-e1a2d1e4aa83@ingresso.co.uk> To: Pete French X-Mailer: Apple Mail (2.3608.60.0.2.5) X-Rspamd-Queue-Id: 48Rgt05Tzyz3G1P X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of daniel@digsys.bg designates 193.68.21.125 as permitted sender) smtp.mailfrom=daniel@digsys.bg X-Spamd-Result: default: False [-1.87 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:193.68.21.125:c]; MV_CASE(0.50)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[digsys.bg]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.978,0]; IP_SCORE(-0.09)[ipnet: 193.68.0.0/19(-0.10), asn: 3245(-0.41), country: BG(0.04)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3245, ipnet:193.68.0.0/19, country:BG]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2020 14:14:35 -0000 If my memory serves well, TRIM was originally not enabled by default on = FreeBSD, because there were many drives that claimed to support it, but = didn=E2=80=99t, or didn=E2=80=99t support it properly. That sort of is = resolved today and WD Green is supposedly relatively recent drive. I am not aware of disabling TRIM creating any kind of problem for data = consistency or drive longevity, except that it leads to slower writes, = as the drive runs out of pre-erased blocks to write to. This is = typically more pronounced on =E2=80=9Ccheaper=E2=80=9D drives like this = one where there is not much over-provisioning but much less pronounced = on =E2=80=9Cserver=E2=80=9D drives that keep certain buffer capacity on = the driv eunused for precisely that purpose. But why should a drive without TRIM wear more quickly? Daniel > On 25 Feb 2020, at 16:07, Pete French = wrote: >=20 >=20 >=20 > On 25/Feb/2020 13:28, Mario Olofo wrote: >> Good morning all, >> @Pete French, you have trim activated on your SSDs right? I heard = that if its not activated, the SSD disc can stop working very quickly. >=20 > On the curent dfives, yes, but I have run with trim disabled in the = past, It kinds of depends on the drive - so were horirbly slow on trim, = and trim could be a big bottleneck. Havent seen that on a recent drive = though, and they all now have trim enabled on them. >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"