From nobody Thu Apr 13 21:20:16 2023 X-Original-To: freebsd-fs@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 4PyCCp2VSnz44fQY; Thu, 13 Apr 2023 21:20:22 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 4PyCCp0K7Pz442h; Thu, 13 Apr 2023 21:20:22 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; none Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 8EE845C0163; Thu, 13 Apr 2023 17:20:20 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 13 Apr 2023 17:20:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :cc:content-transfer-encoding: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=fm2; t= 1681420820; x=1681507220; bh=dcAci4eppcE6CtbW52vyUfa1M4EBtQjHWmC zKLRJlhs=; b=WEkk00xmzGXDgTUVzt7FbrRLaHmspC6RXbRW4OQFxqX7sEPjfk+ eDgfEpgsf+01aQBuiewFN9h6kWRklc6SdQYCsplKPuu78HAnnJ9HQ33zoTnJuvYY NBRhCpW7NnK/F+UqHDZE/9MJjW3pHTJeN1TeidL/uUU7lx4aD2G8tEgpDKhyeyGg qC34Xx2IOMOO0m7XLtCJBOQXTp4lq6yYYtHaJwh3uxjpwLt4I9Jl+gxcW7j+Qd0z ROhtit5VYDhcrWwZXC084rVks6dDZWI+KxXIH/HSUIC2B3MfYOtTmAWVObOoBOd4 O1dm6cB9DbyRMbd5qj055a2/4VwspLr6+Cg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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= 1681420820; x=1681507220; bh=dcAci4eppcE6CtbW52vyUfa1M4EBtQjHWmC zKLRJlhs=; b=DQ26q9YwM2lPGd/JL6kPKlw2wlxaHxyY9Re0Xb3NtjRVZgERrQr 9y3pWGEexWC0f6y8CRpTLK046r5a/vpdnm99OLBpxq8748NF+mIkjIawd+XdxmPu FZe6YNf+T8WPpwpBo7WN90x5RU5qfvYZKxatC74BWYxY8o/MshceQbgQoNCB+4QJ BnsM+yZtLpZ2S4kSY984mjy8t5Fj4D0SanOR/uonIegYfUUv2S2pv3Lai78pfiE9 yuhOKUcd8EvM9J1c3MD+Jhzs8NNIXpm4ltEJfBO75z2wlDTtl5bD7DmjQqAEPjoT G2EdWu+roELDZXl20blvf+10kSnGIWxRzNA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdekkedgudeivdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttdefjeenucfhrhhomhepjghu rhhiuceohihurhhisegrvghtvghrnhdrohhrgheqnecuggftrfgrthhtvghrnhepvdektd fhkeeuueevleefudethffgkeeigfetveduieeggfejueegheffjeefgffhnecuffhomhgr ihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg hmpehmrghilhhfrhhomhephihurhhisegrvghtvghrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 13 Apr 2023 17:20:18 -0400 (EDT) Message-ID: <26febe50-a854-08df-13f9-d1629436c1f3@aetern.org> Date: Thu, 13 Apr 2023 23:20:16 +0200 List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: M2 NVME support Content-Language: en-US To: andy thomas , Thierry Thomas Cc: egoitz@ramattack.net, Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org References: From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4PyCCp0K7Pz442h X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N andy thomas wrote: > On Thu, 13 Apr 2023, Thierry Thomas wrote: > >> Le jeu. 13 avr. 23 ? 13:25:36 +0200, egoitz@ramattack.net >> >> ?crivait : >> >>> Hi!, >> >> 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?. >> >> I have a bad experience, the problem seems to be caused by the driver. >> >> See . > > I thought I would mention I have been using a WD Blue SA510 250GB M2 > NVME SSD mounted on a PCIe to NVME adapter card under FBSD 13.1 for some > months now with no problems or any special drivers being installed. Only it looks like it's actually SATA and not NVMe, based on the output? > The server is a Dell PowerEdge 430 1U server fitted with four SATA disks > in a ZFS pool, with a 4 GB partition on each disk being used for the > swap (since using SSDs for swap space can wear them out quite quickly). > > Attached is a screenshot showing FreeBSD version, the NVME SSD type, > mounted SSD partitions, the server make & model and some info about the > spinning disks too (there is a known issue with the built-in Megaraid > driver in the FreeBSD 13.1 kernel not working with the camcontrol > utility nor converting disk device names like /dev/mfisyspd0 to > traditional names such as /dev/ada0 but these controllers & disks do > work with FBSD 13.1 as you cna see from the zpool output).