From nobody Fri Apr 05 21:28:12 2024 X-Original-To: bugs@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 4VBBRd5Zxgz5HDmT for ; Fri, 5 Apr 2024 21:28:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VBBRd4Mvkz53Fx for ; Fri, 5 Apr 2024 21:28:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1712352493; a=rsa-sha256; cv=none; b=eurvJ3sEfHJ6zSJ6mySgz49ij26/UfSjeE01ItiV6n9GJZRs0pl721naTWTpY5SM+YkNVy ZTUW5qQAiQLY+3LH0Oot+CGfWU84widCEA7bitmHUhvPk6u5KauUOFByUR0WLP9/4rkGvm KhLJfRY7jytXjemlWGx1fS75ffrwgplSshmidTzD6HgNobTYus74/7NG8F2YfqoYMRv4Pc 8TyhQov0WDk3dCp8BP51+lnpEWkYkwWpGd/ZhSOYmvF2Wmy9h2dnXboxhUtxwxRWTYwZm8 zMhen+tjhfOA7AUNfqTN7xeAh2gkJC3+6L+1aAMAFm0ilQA8epr64fb9CK/kZA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1712352493; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5r7l1iim15SdAgBIRr7bzeZqlV16oT8ya6xFtRDrbNk=; b=Z4fpxiT7tjCod1pu+sVJ/S4/fKcRD6NpixWRPfsNT0Z59C690iGtPmcUaJY1HO04MSglKS FYCIazXyho1UgoB9PYtVuun3dvqUoL+qg7mB1mP7hl8uhoYoj9UByM5zg0K9oYOk9CByAZ d+5CmUwC4tAeNu9u8HvZDvofhlaXmRHRPIjZD8BHzZEsh67i1fTVIk4xsVgoFj4NVhMVKZ VTi5vpM23hGBR0vvrKGkuwmV4QnvaFHNNLI6ewBy1YIQjd7bHJdCez45JXJ8ZHQlF7TPec sWuFN72/EWyWWOtcQtnQ9OoZ9Sny+xTYhrZOwHOk3nxqUGxYBh44EU0hEe/LZw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4VBBRd3zczzGXb for ; Fri, 5 Apr 2024 21:28:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 435LSDM4091406 for ; Fri, 5 Apr 2024 21:28:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 435LSDIU091391 for bugs@FreeBSD.org; Fri, 5 Apr 2024 21:28:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 277992] mpr and possible trim issues Date: Fri, 05 Apr 2024 21:28:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: imp@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277992 --- Comment #2 from Warner Losh --- "Power on reset" sense code means that the drive dropped off the bus (typically). Usually if you can eliminate flakey power (either bad connecto= rs, or inadequate power to cope with maximum power draw), then you are left with "commands sent to the drive freaked it out". I always bet at least a nickel= on 'TRIM'. If you think that this is TRIM related, then you can try disabling TRIM at = the da device level by changing the delete method to 'none': kern.cam.da.0.delete_method: NONE It may also be too large a TRIM, you can see what delete_max is, and try reducing it (I usually go by 1/2 when looking for problems like this). I've never had to do this, but it is tunable, and 'too large' is a known issue, = or used to be years ago: kern.cam.da.0.delete_max: 1048576 You can do the trim type at normal to trim everything, and then you can tur= n it off in the drive to do the zfs send / receive. For testing purposes, trim doesn't matter in terms of drive life (it only matters when you write to the drive day in / day out and keep some parts of the drive unused for more tha= n, say, a few hours or a day). It may also be that weird commands are being sent by something like smartd, etc. If you can reproduce this, then we may be able to adopt a prototype dt= race script I have to make a tcpdump-like script. We can use it to dump the last= N commands when we get a unit attention. Now, having said all this, I think that this sense code might be mishandled right now. Regardless of how we got here, I think that this should pause the I/O, and reset the parameters we've set in the drive to reset its state to = what the driver expects (though I think only the write through cache and similar settings might matter). --=20 You are receiving this mail because: You are the assignee for the bug.=