From nobody Thu Nov 30 18:59:34 2023 X-Original-To: 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 4Sh58l1hXMz52Ql7 for ; Thu, 30 Nov 2023 18:59:35 +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 4Sh58l0Gn9z3Gg9 for ; Thu, 30 Nov 2023 18:59:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1701370775; 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=j1PNPzUWQOiKK4Gz25YOpRJs1HWAl3wFjWh8mN1iZSM=; b=NnH62xMptYQ3gspaUNicmfpS2ih8q/KSs++Np6VDhfv8q21LIbMeTOfkZSGNER/YO5/JDZ XI5IU1wPJJNFPQ7BYFSR8rGdu38pIWKIoJsyvYUTVkG11rwGKXtrAzgMamomGu4WdJh2mr omjt5OPEZ8jj+Xr5sh04tUudDCQlNnJeDcWrgW9pTC1XLZbqtAEfyUFXKWi9rljfkr7SwS O9Ca6QMFjCFR57PWP/GoHIPKkB0rdNqC+xlBPtURLWgc8ePBaDnKNSP88HEb0ExgOERFj5 Ly/ooIC2Ql7Tva36CtwlkRY+mFdrHgJ0JxVrhh9PiXIB3SaAG56vIXFy71E4Ng== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1701370775; a=rsa-sha256; cv=none; b=FbU/pE9Fm8/0XY44HgvZiCEstJorhU9SfwqIZSPB5vnLv+PlMD+oAUbojS/Q75/l6Ty/TD Sk0Ovv5D8GmKitO/UyclaK179/So9Vtvl0fZAouUamdDpUWb9YFPFEIDScmVWXp4D+2kPX imFkipKtT1gj7e7Z1FLm6LE090XTFjmDr/cuWX0QzVFVwZzzaCjsP8Y00WrRQ/BuXsZWki RKvMwTvuc4l2kQmIYE2MUD27inBMThhfj8rE7x3zZMv+p4ziobpUAvDLbjn4u+KmJmOifq vhS5LvdRBdZUdmcCPjxTIxit34YsgOsEOXxkcPsfiyrC19612lOOnL7HJPLh8g== 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 4Sh58k6T07z11g8 for ; Thu, 30 Nov 2023 18:59:34 +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 3AUIxYcm096583 for ; Thu, 30 Nov 2023 18:59:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3AUIxYGr096581 for fs@FreeBSD.org; Thu, 30 Nov 2023 18:59:34 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: fs@FreeBSD.org Subject: [Bug 275308] EN tracking issue for potential ZFS data corruption Date: Thu, 30 Nov 2023 18:59:34 +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-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@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: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275308 --- Comment #28 from Ed Maste --- (In reply to mike from comment #27) The workaround actually improves performance (at the cost of possibly incor= rect hole reporting). Once the update is applied though I believe there's no benefit (from a risk mitigation perspective) in keeping the workaround. I've added a sentence to= the end of the workaround section in the draft EN: IV. Workaround Setting the vfs.zfs.dmu_offset_next_sync sysctl to 0 disables forcing TXG sync to find holes. This is an effective workaround that greatly reduces the likelihood of encountering data corruption, although it does not completely eliminate it. Note that with the workaround holes will not be reported in recently dirtied files. See the zfs(4) man page for more information of the impact of this sysctl setting. The workaround should be removed once the system is updated to include the fix described in this notice. --=20 You are receiving this mail because: You are the assignee for the bug.=