From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 53D6E1FF140 for ; Fri, 13 Mar 2026 15:19:03 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 594D348CA; Fri, 13 Mar 2026 15:19:08 +0100 (CET) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pve-devel@lists.proxmox.com, Stoiko Ivanov Subject: applied: [PATCH zfsonlinux] fix scrub breaking with newer userspace utils and older kernel module Date: Fri, 13 Mar 2026 15:18:34 +0100 Message-ID: <177341149827.1342115.10663025637452610271.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260312101651.301181-1-s.ivanov@proxmox.com> References: <20260312101651.301181-1-s.ivanov@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773411503393 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: BMKVXMKZ3AETRHC5GBDCKKMPJ3NDAF4J X-Message-ID-Hash: BMKVXMKZ3AETRHC5GBDCKKMPJ3NDAF4J X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu, 12 Mar 2026 11:15:01 +0100, Stoiko Ivanov wrote: > currently when running an older kernel with ZFS 2.3 modules (e.g. by > actively pinning it) running zfs scrub fails, due to some changes in > 2.4, which are not backward compatible. > > This patch was submitted upstream at: > https://github.com/openzfs/zfs/pull/18314 > > [...] Applied, thanks! [1/1] fix scrub breaking with newer userspace utils and older kernel module commit: 68461c06b4d4d6ded2c7c1136cc5c70162325370 Best regards, -- Fabian Grünbichler