From nobody Thu Jun 8 11:48:22 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 4QcMth15ZTz4bQCb for ; Thu, 8 Jun 2023 11:49:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 4QcMtg6XCFz449t for ; Thu, 8 Jun 2023 11:48:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-3f6d7abe934so3149505e9.2 for ; Thu, 08 Jun 2023 04:48:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1686224935; x=1688816935; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hVXuI9kWQdfyJlipfVXLc7tfyHiP89BwCYZrTYQdzQ0=; b=sw3TmdD8yIjXmOtFEsOfXJJEhacKlsakWZ6h+HeIxnVyEb4gqjS1bqaCQsTV988bor 2lA8JmCAu+mDdsNvhOVDhYb/cgGCwPtJ7nsvKKfXPvrP2W+KtKViWr8wk471jm+LO+lr 3VvttmqmlYrZ9Gc4u8swt3jqgMeRlyoPoH7XW7dizK83hfCdASrfWaoX6gBMJX1Qfhz8 SC0pc8wXXlMhiOcWhfPmRcfa5aFlthY5qdINWO1xdWjzaImfL1dzvJ+EVHwtRK4vnGds igf0kgkDYyMyfIGfbOMoOf7fPz0qAOahFnZomVNiQtWOnmWSP8/Z9ISOdcBSwU3Kw58v i1ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686224935; x=1688816935; h=cc: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=hVXuI9kWQdfyJlipfVXLc7tfyHiP89BwCYZrTYQdzQ0=; b=HhGEal6hFik3gnqtjBnVJpz+Woe8tZssU8OBkPAbAl1tFvhHItMJEmMAVhIvR3Mh23 Fn2P1WRi9Qw6NB48ZPw4RSmfQeMn8qOoI5TgnmnItJb+bPCV3xD8eQWfqBRmdXuJ8wnO pLFEA9h6BX8GFIc+LLPbWWHalR+UDubTBcZf7AlG/mZwG5AvPP4mD3TBZYpACp0uR+WZ Ih+pBOL78vEstI7aTxWyWgrL/rKiAlgqxBsr3//3KpejE6Yc8rTtPVy9t1bOYHod7cli Iv6V4mnQt5uwLohyzFwrDbN3yJSBgz8IXc1H2fSgWVS4B8++CIaE8JdTaicgqOb4To4/ MpSQ== X-Gm-Message-State: AC+VfDx7E9yiATXBXS8cOUU+m2JtkDgcdg8bnAzE0Srxcdi//0/w7mnX /5CszaBVkkb1WGZB6JQhKbrJMwqO3Lw3Qdp3lGTOVFQdObdFq4Hs X-Google-Smtp-Source: ACHHUZ6nlxId60sTpIJU6RSR6uVZQE1N2H20qdmCzBUAHNYT9EQQ0xLiFIumCmf9f5NBjjC2THv40Ytf1E8EUojZ1EU= X-Received: by 2002:a17:907:868f:b0:96a:5bdd:7557 with SMTP id qa15-20020a170907868f00b0096a5bdd7557mr9110617ejc.70.1686224913943; Thu, 08 Jun 2023 04:48:33 -0700 (PDT) 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 References: <5b52fc08-fb5a-900e-b98c-817a4ab79846@bsdio.com> In-Reply-To: From: Warner Losh Date: Thu, 8 Jun 2023 04:48:22 -0700 Message-ID: Subject: Re: Seemingly random nvme (nda) write error on new drive (retries exhausted) To: Rebecca Cran Cc: Tomek CEDRO , FreeBSD CURRENT Content-Type: multipart/alternative; boundary="00000000000001e0af05fd9cd59f" X-Rspamd-Queue-Id: 4QcMtg6XCFz449t X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000001e0af05fd9cd59f Content-Type: text/plain; charset="UTF-8" On Thu, Jun 8, 2023, 4:35 AM Rebecca Cran wrote: > It's ZFS, using the default options when creating it via the FreeBSD > installer so I presume TRIM is enabled. Without a reliable way to > reproduce the error I'm not sure disabling TRIM will help at the moment. > > I don't think there's any newer firmware for it. > pci gen 4 has a highter error rate so that needs to be managed with retries. There's a whole protocol to do that which linux implements. I suspect the time has come for us to do so too. There's some code floating around I'll have to track down. Warner -- > > Rebecca Cran > > > On 6/8/23 04:25, Tomek CEDRO wrote: > > what filesystem? is TRIM enabled on that drive? have you tried > > disabling trim? i had similar ssd related problem on samsung's ssd > > long time ago that was related to trim. maybe drive firmware can be > > updated too? :-) > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > --00000000000001e0af05fd9cd59f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jun 8, 2023, 4:35 AM Rebecca Cran <rebecca@bsdio.com> wrote:
It's ZFS, using the default options when cr= eating it via the FreeBSD
installer so I presume TRIM is enabled. Without a reliable way to
reproduce the error I'm not sure disabling TRIM will help at the moment= .

I don't think there's any newer firmware for it.

pci gen 4 has a hig= hter error rate so that needs to be managed with retries.=C2=A0 There's= a whole protocol to do that which linux implements. I suspect the time has= come for us to do so too. There's some code floating around I'll h= ave to track down.

Warne= r

--

Rebecca Cran


On 6/8/23 04:25, Tomek CEDRO wrote:
> what filesystem? is TRIM enabled on that drive? have you tried
> disabling trim? i had similar ssd related problem on samsung's ssd=
> long time ago that was related to trim. maybe drive firmware can be > updated too? :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

--00000000000001e0af05fd9cd59f--