From nobody Tue Nov 5 13:16:15 2024 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 4XjTRt5JhWz5c5Wn for ; Tue, 05 Nov 2024 13:18:34 +0000 (UTC) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (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 "uucp.dinoex.sub.de", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XjTRs0Wp7z4y4T for ; Tue, 5 Nov 2024 13:18:32 +0000 (UTC) (envelope-from li-fbsd@citylink.dinoex.sub.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of li-fbsd@citylink.dinoex.sub.org designates 2a0b:f840::12 as permitted sender) smtp.mailfrom=li-fbsd@citylink.dinoex.sub.org; dmarc=none; arc=pass ("uucp.dinoex.org:s=M20221114:i=1") Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]) by uucp.dinoex.org (8.18.1/8.18.1) with ESMTPS id 4A5DI7Tv017041 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 5 Nov 2024 14:18:08 +0100 (CET) (envelope-from li-fbsd@citylink.dinoex.sub.org) ARC-Seal: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1730812690; cv=none; b=EhQglI+EuGflFnBl5MePKgoZ04waVz4zcE46MlGdJWBC6UzuYFBwjegnbR8FD7pIP+JBUlh0HtbXdTgR66oSu5opimgNTO6Qs2Gotfmq5y+u6yY3uzp72+hsSoaPKtqu8Uu3a5Tb4IWjb0BL2Rz6tgfVINq1uhFjeB/7ukXTXf8= ARC-Message-Signature: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1730812690; c=relaxed/simple; bh=YBEJ1EXpiFIU+kzFyCkTod/XaIifYMqlUi/lI8o2AQE=; h=Received:Received:Received:X-Authentication-Warning:From: X-Newsgroups:Subject:Date:Message-ID:References:Injection-Date: Injection-Info:User-Agent:To:X-Milter:X-Greylist; b=EqWalCHgSQuqcYwycWxvEFtcCry3gZEQs8p5DJoVMCAqRv3+SI0cRjlLdF27FhbijhzTTZau+dzT9QPae4OkaIh9SqA5v1vP0gGTn+QHVF4CRvOsKVLjhRT57pJCrtBiM12B75wJrew985PdUPYvYCqNgP6io50bKr1YD9KzvFE= ARC-Authentication-Results: i=1; uucp.dinoex.org X-MDaemon-Deliver-To: Received: (from uucp@localhost) by uucp.dinoex.org (8.18.1/8.18.1/Submit) with UUCP id 4A5DI7ZT017039 for freebsd-fs@freebsd.org; Tue, 5 Nov 2024 14:18:07 +0100 (CET) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from admn.intra.daemon.contact (localhost [127.0.0.1]) by admn.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 4A5DGY52008785 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 5 Nov 2024 14:16:34 +0100 (CET) (envelope-from li-fbsd@citylink.dinoex.sub.org) Received: from intra.daemon.contact (news@localhost) by admn.intra.daemon.contact (8.18.1/8.18.1/Submit) with NNTP id 4A5DGFj6008551 for freebsd-fs@freebsd.org; Tue, 5 Nov 2024 14:16:15 +0100 (CET) (envelope-from li-fbsd@citylink.dinoex.sub.org) X-Authentication-Warning: admn.intra.daemon.contact: news set sender to li-fbsd@citylink.dinoex.sub.org using -f From: "Peter 'PMc' Much" X-Newsgroups: m2n.fbsd.fs Subject: Re: nvme device errors & zfs Date: Tue, 5 Nov 2024 13:16:15 -0000 (UTC) Message-ID: References: <3293802b-3785-4715-8a6b-0802afb6f908@app.fastmail.com> <620f4e82-aa69-4af0-bd22-b21203ab8745@app.fastmail.com> Injection-Date: Tue, 5 Nov 2024 13:16:15 -0000 (UTC) Injection-Info: admn.intra.daemon.contact; logging-data="87927"; mail-complaints-to="usenet@citylink.dinoex.sub.org" User-Agent: slrn/1.0.3 (FreeBSD) To: freebsd-fs@freebsd.org X-Milter: Spamilter (Reciever: uucp.dinoex.org; Sender-ip: 0:0:2a0b:f840::; Sender-helo: uucp.dinoex.org;) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]); Tue, 05 Nov 2024 14:18:10 +0100 (CET) X-Spamd-Result: default: False [-3.92 / 15.00]; ARC_ALLOW(-1.00)[uucp.dinoex.org:s=M20221114:i=1]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.99)[-0.992]; NEURAL_HAM_SHORT(-0.93)[-0.927]; FORGED_SENDER(0.30)[pmc@citylink.dinoex.sub.org,li-fbsd@citylink.dinoex.sub.org]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_XAW(0.00)[]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; FROM_NEQ_ENVFROM(0.00)[pmc@citylink.dinoex.sub.org,li-fbsd@citylink.dinoex.sub.org]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[sub.org]; RCVD_TLS_LAST(0.00)[]; TO_DN_NONE(0.00)[] X-Rspamd-Queue-Id: 4XjTRs0Wp7z4y4T X-Spamd-Bar: --- 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 On 2024-11-05, Dave Cottlehuber wrote: > I would hope temperature throttling would not be quite so brutal, to > remove itself from the bus entirely, but its a reasonable explanation. It might be a reasonable choice to protect the data first. Also people will then notice that there is a problem and not complain about bad performance. If a more elegant reaction is desired, that might be implemented by obtaining the current temperature and dynamically issuing some "nvmecontrol power -p x -w y ..." as appropriate. (From what I hear, these options behave rather device specific, so some testing may be required) https://gitr.daemon.contact/tools/tree/heatctl.rb#n218 I'm not yet doing temperature-driven nvme performance steering, but practically everything else: fan engage, scrub pausing, cpu consumtion (via rctl) etc. cheerio, PMc