From nobody Thu Apr 13 11:25:36 2023 X-Original-To: freebsd-hardware@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 4Pxy1c5KcJz44pBf; Thu, 13 Apr 2023 11:25:40 +0000 (UTC) (envelope-from egoitz@ramattack.net) Received: from cu1208c.smtpx.saremail.com (cu1208c.smtpx.saremail.com [195.16.148.183]) (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 4Pxy1b3YKyz49hW; Thu, 13 Apr 2023 11:25:38 +0000 (UTC) (envelope-from egoitz@ramattack.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of egoitz@ramattack.net designates 195.16.148.183 as permitted sender) smtp.mailfrom=egoitz@ramattack.net; dmarc=pass (policy=reject) header.from=ramattack.net Received: from www.saremail.com (unknown [194.30.0.183]) by sieve-smtp-backend02.sarenet.es (Postfix) with ESMTPA id 652DB60C234; Thu, 13 Apr 2023 13:25:36 +0200 (CEST) List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_88fd3998bafc93f27a15061a2f6d1095" Date: Thu, 13 Apr 2023 13:25:36 +0200 From: egoitz@ramattack.net To: Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org Subject: M2 NVME support Message-ID: X-Sender: egoitz@ramattack.net User-Agent: Saremail webmail X-Spamd-Result: default: False [0.70 / 15.00]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_SPAM_SHORT(0.61)[0.605]; DMARC_POLICY_ALLOW(-0.50)[ramattack.net,reject]; R_SPF_ALLOW(-0.20)[+ip4:195.16.148.0/24]; NEURAL_HAM_MEDIUM(-0.11)[-0.115]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:3262, ipnet:195.16.128.0/19, country:ES]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org,freebsd-hackers@freebsd.org,freebsd-hardware@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_DKIM_NA(0.00)[]; FROM_NO_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Pxy1b3YKyz49hW X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --=_88fd3998bafc93f27a15061a2f6d1095 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hi!, We are in the process of buying new hardware for use with FreeBSD and ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks (probably Samsung PM* ones). How is you experience with them?. Do you recommend one over the another?. Is perhaps better support from some of them from a specificic version to newer?. Or do they perhaps work better with some specific disk controller?. Best regards, --=_88fd3998bafc93f27a15061a2f6d1095 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

Hi!,

We are in the process of buying new hardware for use with FreeBSD and ZF= S. We are planning whether to buy M2 NVME disks or just SATA SSD disks (pro= bably Samsung PM* ones). How is you experience with them?. Do you recommend= one over the another?. Is perhaps better support from some of them from a = specificic version to newer?. Or do they perhaps work better with some spec= ific disk controller?.

Best regards,

--=_88fd3998bafc93f27a15061a2f6d1095-- From nobody Thu Apr 13 11:35:52 2023 X-Original-To: freebsd-hardware@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 4PxyFY3Mrqz44qFM; Thu, 13 Apr 2023 11:36:01 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from edna.lautre.net (edna.lautre.net [80.67.160.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "lautre.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PxyFX6zSCz3Dvh; Thu, 13 Apr 2023 11:36:00 +0000 (UTC) (envelope-from thierry@pompo.net) Authentication-Results: mx1.freebsd.org; none Received: from graf.pompo.net (graf.pompo.net [82.66.0.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by edna.lautre.net (Postfix) with ESMTPSA id D29FD10B8EE; Thu, 13 Apr 2023 13:35:52 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id 73E0D587ED7; Thu, 13 Apr 2023 13:35:52 +0200 (CEST) Date: Thu, 13 Apr 2023 13:35:52 +0200 From: Thierry Thomas To: egoitz@ramattack.net Cc: Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org Subject: Re: M2 NVME support Message-ID: Mail-Followup-To: egoitz@ramattack.net, Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org References: List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bjt3ILRrrR97TDbB" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 13.1-STABLE amd64 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc;y=\ipKMNm<1J>lv@PP~7Z<.tKjAnXLs: X-PGP: 0xF1C516B3C8359753 X-Rspamd-Queue-Id: 4PxyFX6zSCz3Dvh X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20766, ipnet:80.67.160.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --bjt3ILRrrR97TDbB Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le jeu. 13 avr. 23 =E0 13:25:36 +0200, egoitz@ramattack.net =E9crivait=A0: > Hi!,=20 Hello, > We are in the process of buying new hardware for use with FreeBSD and > ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks > (probably Samsung PM* ones). How is you experience with them?. Do you > recommend one over the another?. Is perhaps better support from some of > them from a specificic version to newer?. Or do they perhaps work better > with some specific disk controller?.=20 I have a bad experience, the problem seems to be caused by the driver. See . Regards. --=20 Th. Thomas. --bjt3ILRrrR97TDbB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJkN+kYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFNTM2QkU4NTM4NTM5OUQwMEI2RkFBNzZG MUM1MTZCM0M4MzU5NzUzAAoJEPHFFrPINZdTYWIP/3zxEIk+TVYh+rpMaFGBm7fh BrkPAOrKVfdfVuwpqQAaxwkHX5C5ISSSg8QMY+DrzpwEjX0wzDhgDaZnG3f1Glen 14e/yHxyCY1R5QzzM5C2aZV+I/tI+AVWRgCaHVsNVT1+u5yE4XDyUP5Qosb6EaR1 4QTYD8nxHUkyAH31GcshLcnJVBbLSVPRkoAoZOrs0a5r2J8E8plkwnwrF6R7t+L8 rZ4Iw9PuZi6LIjkkwqRYQjGFQkJ8oLkRQBMKvGltnwXhhumsMrFe4UEkD3hC+rzd XDUyMhFPrPL9LNS3uikPYuowTJGxmhBxYIuwmrd3p/B2vi2McdQxJ+oH82CfgPzk Kq+yjnUap28mjrl0MhI3AkjoPXQsXHTJ8JHta1BhWxJdCeU1sGtbcUsvJOWk789F ih4FW31HfEduNg9GakUIGnGLyxb3pzYc1nCZ/oYSrwKDIboOFqehMauqFyWdr+Ts Iouxv8pwReKa/J54E27lZBuRUlNsv8pXcfMJ75qH0Fpg5crFmJLyEs00a7EyOTSH hOYY1ZCyXnh2R5uJMsUbthGr+bk7qeP/UxDXAERwagdp3T2/VJEnqZmZVviouKq5 LTWe3m0FjWUqXX5IDuDav5EshGKuKDnWvy6io4w7mu2DLkKqnArenIjQLTp8rco9 J92LBA+tgAvlDtGZ1FY/ =OBnS -----END PGP SIGNATURE----- --bjt3ILRrrR97TDbB-- From nobody Thu Apr 13 11:43:32 2023 X-Original-To: freebsd-hardware@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 4PxyQK6zZ6z44qmB; Thu, 13 Apr 2023 11:43:37 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (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 4PxyQK5LT7z3kPv; Thu, 13 Apr 2023 11:43:37 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi by fc.opsec.eu with local (Exim 4.96 (FreeBSD)) (envelope-from ) id 1pmvMS-000Hca-19; Thu, 13 Apr 2023 13:43:32 +0200 Date: Thu, 13 Apr 2023 13:43:32 +0200 From: Kurt Jaeger To: egoitz@ramattack.net Cc: Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org Subject: Re: M2 NVME support Message-ID: References: List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4PxyQK5LT7z3kPv X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hi! > We are in the process of buying new hardware for use with FreeBSD and > ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks > (probably Samsung PM* ones). How is you experience with them? One box with two NVMe (my packet-builder host), running CURRENT. Model Number: Samsung SSD 970 PRO 1TB Works fine, no problems. I have not measured throughput, but I guess NVMe is faster than SSD, due to the SATA bottleneck etc. Several boxes with SSD Sata (mostly Samsung SSD 850/960 and some with Intel S4510/S4610/S4500/S4600 Series SSDs), all work fine. There were issues with Samsung SSDs and AMD EPYC 3251 CPUs. That's when we brought in the Intel SSDs... > Do you recommend one over the another?. Is perhaps better support from > some of them from a specificic version to newer?. > Or do they perhaps work better > with some specific disk controller?. -- pi@FreeBSD.org +49 171 3101372 Now what ? From nobody Thu Apr 13 11:47:27 2023 X-Original-To: freebsd-hardware@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 4PxyW13JpFz44rTJ for ; Thu, 13 Apr 2023 11:47:41 +0000 (UTC) (envelope-from tomek@cedro.info) 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 4PxyW03j60z3s7m for ; Thu, 13 Apr 2023 11:47:40 +0000 (UTC) (envelope-from tomek@cedro.info) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cedro.info header.s=google header.b=HHrJ7BBg; spf=none (mx1.freebsd.org: domain of tomek@cedro.info has no SPF policy when checking 2607:f8b0:4864:20::112c) smtp.mailfrom=tomek@cedro.info; dmarc=none Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-54fa9da5e5bso76203917b3.1 for ; Thu, 13 Apr 2023 04:47:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cedro.info; s=google; t=1681386459; x=1683978459; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=ihV8HoluZxy2lJxSKGH+0a12aS1o68Y3MTJ5s8iMGn0=; b=HHrJ7BBg99esj1DT16PrqRZzuarehUbnwKEIUJRJ/xXY/rc36cx7tgElUAR5IGnt/8 TfU3hcjGlL2L+CN9a4q/0i2PCMpBfgnj0Bs/+cOB4pnan4eN8kHQhnpLYgceGPkBIzwW 9ukX1CZjvSnl85XtZvSkNSZwpgBWMaEIhllnqF01FDzyFAEoW7D9qUKbsn6rE/YxnOJg C2KVc609ZV8PSDzEk6Vr4lMSIiI3gLrF3NkT1WMp9Miz1Hl43KioMiWg01RlwhGyXULg Uq+EdTwQ1jEsbgIjaI/79N3+SDxUmtdbNgNw4HEj59m++x4BnP5LKM80VttBTb8bJJU7 zyCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681386459; x=1683978459; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ihV8HoluZxy2lJxSKGH+0a12aS1o68Y3MTJ5s8iMGn0=; b=jDXrela/7YcdwrDKWVEo2TMzqcgs4obsAQP6QLOnnJxpdebCMn+RykQqnz/4jn2Vxt AUt9Aa0CcvdNIViI4nqMLmyoN0CrklPhM36mohsUTEFULTilgMBcu4AIzmnxnjlZMMaj 5Qd0/HOjYmFC8NSTcS+IWZJgM2QJWX1i9sZBQ5kwAfhOvpH0o0Wa8sIDr6EfViEBdALe iEeQApMEVoei28n4t/C4oC7jpmH4YBBtJ3EMq6Jc0vn/0cLiWT7tNall9C5lM1FmSfdz rkgzAIUj339ARwSbGYW1hdm3MpjXKYUy4UlN4v9DylCPNyoKe48DgNctOltQbWYOcKR3 ZHVQ== X-Gm-Message-State: AAQBX9dFzgfUm4a+KAbe6Wr7HnuiqMj5VdweSShhg/g8daDbprt2zcyJ XlxAOenRRzXa2jIDb2dVrZ2dSiSbAqZpNghKAmw= X-Google-Smtp-Source: AKy350a2qAO0klQPL8G1rib7DRhxjGdmGzKD3BmQzsz4OzXyEz3qZ/uWwQGeSgp9d1BpNa9v9kbbmA== X-Received: by 2002:a0d:d982:0:b0:54f:8b2b:adec with SMTP id b124-20020a0dd982000000b0054f8b2badecmr1625943ywe.33.1681386459735; Thu, 13 Apr 2023 04:47:39 -0700 (PDT) Received: from mail-yb1-f173.google.com (mail-yb1-f173.google.com. [209.85.219.173]) by smtp.gmail.com with ESMTPSA id 141-20020a810393000000b0054fba955474sm401373ywd.17.2023.04.13.04.47.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Apr 2023 04:47:39 -0700 (PDT) Received: by mail-yb1-f173.google.com with SMTP id h198so21486974ybg.12; Thu, 13 Apr 2023 04:47:39 -0700 (PDT) X-Received: by 2002:a25:77cb:0:b0:b21:5fb4:c6e6 with SMTP id s194-20020a2577cb000000b00b215fb4c6e6mr985861ybc.11.1681386458841; Thu, 13 Apr 2023 04:47:38 -0700 (PDT) List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Tomek CEDRO Date: Thu, 13 Apr 2023 13:47:27 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: M2 NVME support To: egoitz@ramattack.net, Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[cedro.info:s=google]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112c:from,209.85.219.173:received]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[cedro.info:+]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hardware@freebsd.org]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[cedro.info]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4PxyW03j60z3s7m X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Sorry, I missed the initial post. I am using Samsung 980 1TB NVME M2 SSD on a ICY BOX PCI-E 4.0x4 1xM.2 NVMe with ZFS as my root pool, works like a charm on old 2013 mainboard where only SATA is available.. just note that maximum chipset efficiency will be the bottleneck but with a good chipset it may be faster than SATA :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From nobody Thu Apr 13 12:56:21 2023 X-Original-To: freebsd-hardware@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 4Py02L6Q5bz44xWb; Thu, 13 Apr 2023 12:56:26 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (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 "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Py02L3F9Bz3PDP; Thu, 13 Apr 2023 12:56:26 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; none Received: from [10.1.2.18] (mailserver.netfence.it [78.134.96.152]) (authenticated bits=0) by soth.netfence.it (8.17.1/8.17.1) with ESMTPSA id 33DCuLgA090917 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 13 Apr 2023 14:56:21 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host mailserver.netfence.it [78.134.96.152] claimed to be [10.1.2.18] Message-ID: Date: Thu, 13 Apr 2023 14:56:21 +0200 List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: M2 NVME support Content-Language: en-US To: egoitz@ramattack.net References: Cc: Freebsd fs , freebsd-hardware@freebsd.org, Freebsd hackers From: Andrea Venturoli In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.86 X-Rspamd-Queue-Id: 4Py02L3F9Bz3PDP X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 4/13/23 13:25, egoitz@ramattack.net wrote: > We are in the process of buying new hardware for use with FreeBSD and > ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks > (probably Samsung PM* ones). How is you experience with them? I've never had any trouble with any SATA disks. As for M.2, I only have a RAID-1 root pool on one box: # nvmecontrol devlist nvme0: SPCC M.2 PCIe SSD nvme0ns1 (244198MB) nvme1: SPCC M.2 PCIe SSD nvme1ns1 (244198MB) So far, so good, but it's quite new. > Do you recommend one over the another? M.2 should be a lot faster than SATA. A good SATA RAID might be fast enough, however, depending on your needs. In the low-end market I would go with M.2, provided you have two slots on the MB. In the high-end, I'm not so sure... SATA enterprise SSDs are available, M.2, AFAIK, not. The new U.2 standard looks promising, but I'm not so sure it will catch on, while SATA will eventually disappear, but not any time soon. > Or do they perhaps work better with some specific disk controller?. You mean NVMe? There is really no controller (as it is intended in SATA/SCSI/SAS/...), they just appear on the PCI bus. bye av. From nobody Fri Apr 14 06:07:20 2023 X-Original-To: freebsd-hardware@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 4PyQw354dwz44Wy5; Fri, 14 Apr 2023 06:07:31 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (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 "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PyQw31w0Fz3x0d; Fri, 14 Apr 2023 06:07:31 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; none Received: from [10.1.2.18] (mailserver.netfence.it [78.134.96.152]) (authenticated bits=0) by soth.netfence.it (8.17.1/8.17.1) with ESMTPSA id 33E67K81017479 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 14 Apr 2023 08:07:21 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host mailserver.netfence.it [78.134.96.152] claimed to be [10.1.2.18] Message-ID: <70dd5c7a-d37d-2463-ea34-e05c081ab325@netfence.it> Date: Fri, 14 Apr 2023 08:07:20 +0200 List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: M2 NVME support Content-Language: en-US To: Freddie Cash , egoitz@ramattack.net, Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org References: From: Andrea Venturoli In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.86 X-Rspamd-Queue-Id: 4PyQw31w0Fz3x0d X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 4/13/23 18:43, Freddie Cash wrote: > If you want the best performance, and money isn't a restriction, then > you'll want to look into servers that have U.2 (or whatever the next-gen > small form factor interface name is) slots and backplanes. The > drives cost a lot more than regular M.2 SSDs But, being "enterprise" drive, this is perhaps justified. Actually they can even cost less than (slower) SATA "enterprise" drives. Of course you'll need to add the cost of a controller, which you have almost always "for free" for SATA. bye av.