From nobody Sun Aug 13 03:42:39 2023 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 4RNjzL6qbxz4mNrv for ; Sun, 13 Aug 2023 03:42:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 4RNjzL4l5Jz3T76 for ; Sun, 13 Aug 2023 03:42:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-5236a9788a7so4336269a12.0 for ; Sat, 12 Aug 2023 20:42:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1691898171; x=1692502971; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tjHqP9uqVJyurk/vN/w8ByNNFiWowiTPgmj9vj68K0k=; b=5qFwrhWBtzbfvuBIHcZnwpF3fNkxFjFiQdJLxRSFeRf7Lp2C40d8hBkMuRpSjE4qpG GTjGmIWLIZwBltwSKVldKhAdsOZD1Zt31ls46lRlaHaCc0DN/c5FLMdTG9br5V2NegwL FQ5Rqafjnkd2z09ccir65NsJWuFbwOeYYfjGZnYVp+jrT76NLYmDv/+cKFUv42LlXJFR n2irfpTJAIky10aXr//2zGYFIVh/Bf6jRNS6cTClMLbDe7RIIZZCBqDOyOntqnEqyvax 08+rMfi5vIWd5tNmXuK6AX+dkpSomo1uJln6fwtcB2BzOa1esxFGK8cBWjgDr6zNZzzB KS4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691898171; x=1692502971; 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=tjHqP9uqVJyurk/vN/w8ByNNFiWowiTPgmj9vj68K0k=; b=XtcHUnvXjCYtiimv+p2IT/I4KfOkCbOOigbUpqJ5qKtkY6n82bGqvoSij7DVpcUgCW KTGwR2t3J/5RzzTCulUpyDgsH4Fi9nb7bnJyPxaAsrRTgEyhqnqdzBTVGLhs53QY2T6d J+Rxj+9S/0Sofsxs9Gm9JIPfJrzvA3lfKcD9fLEpcGY5ope7uZjPT+QKztpIIoVtRSKr MXgRE9Yu94BfOsDuUKwk2eoQdyzzIK0Ec10l2u5DlEARbi4Mqm4JXQLV+E2wdC/biz6E B/L+t/tZJFTDGVuZwMGuWSL7TSLMc/wDRWyIwJK4zSSE+hw2fPkjo5O5EZJU5xoKYUQh 91gA== X-Gm-Message-State: AOJu0YwguVW3X4V+5h6avg12ZdkX9pfWD+pzGkX10qmvRCUtKPP1eS0d gpWqmenY9FanXtF20VvknbRHIbKCXEE7VX2oufBfJrw0AAItkMQr X-Google-Smtp-Source: AGHT+IGf+GvOB3XmQS9H7MWrzp3e5/lv6N7rX8xP30tikRd9QK9SQ+0ESjMsbCDrSrJWUBLkaGe5PH/fWdPhuz5bmNo= X-Received: by 2002:a05:6402:1245:b0:525:5ed2:abed with SMTP id l5-20020a056402124500b005255ed2abedmr132440edw.30.1691898171180; Sat, 12 Aug 2023 20:42:51 -0700 (PDT) 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 References: <25816.16958.659259.797522@hergotha.csail.mit.edu> In-Reply-To: <25816.16958.659259.797522@hergotha.csail.mit.edu> From: Warner Losh Date: Sat, 12 Aug 2023 21:42:39 -0600 Message-ID: Subject: Re: Interesting (Open)ZFS issue To: Garrett Wollman Cc: FreeBSD-STABLE Mailing List Content-Type: multipart/alternative; boundary="0000000000007d59ab0602c5bd48" X-Rspamd-Queue-Id: 4RNjzL4l5Jz3T76 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --0000000000007d59ab0602c5bd48 Content-Type: text/plain; charset="UTF-8" On Sat, Aug 12, 2023, 8:39 PM Garrett Wollman wrote: > On Friday, a server that I had upgraded to 13.2 the day before > suddenly developed faults on both SSDs in its root pool. The > machine was a Dell R430, so the two SSDs were behind a LSI/whoever HBA > (new enough that it's an mpr(4) and not mps or mpt). The first disk > started reporting the exceedingly obscure: > > (da0:mpr0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:74,79 (Security conflict > in translated device) > > (This error is so obscure that the only place I could find it was in > the SCSI-ATA translator specification and all of the lists of SCSI > sense codes that copy the message directly from it.) > Oh... I've seen this when one of the SATA drives we use at work loses it's mind... nothing I've done has been able to rehab it or get any data out of it... not entirely sure what it means either Can't help with the rest :( Warner --0000000000007d59ab0602c5bd48 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Aug 12, 2023, 8:39 PM Garrett Wollman <wollman@bimajority.org> wrote:=
On Friday, a server that I had upg= raded to 13.2 the day before
suddenly developed faults on both SSDs in its root pool.=C2=A0 The
machine was a Dell R430, so the two SSDs were behind a LSI/whoever HBA
(new enough that it's an mpr(4) and not mps or mpt).=C2=A0 The first di= sk
started reporting the exceedingly obscure:

(da0:mpr0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:74,79 (Security conflict = in translated device)

(This error is so obscure that the only place I could find it was in
the SCSI-ATA translator specification and all of the lists of SCSI
sense codes that copy the message directly from it.)
=

Oh... I've seen thi= s when one of the SATA drives we use at work loses it's mind...=C2=A0 n= othing I've done has been able to rehab it or get any data out of it...= not entirely sure what it means either

Can't help with the rest :(

=
Warner
--0000000000007d59ab0602c5bd48--