From nobody Mon Sep 20 13:34:32 2021 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 EE779178B036 for ; Mon, 20 Sep 2021 13:34:31 +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 4HClsM6HYHz4g5h for ; Mon, 20 Sep 2021 13:34:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 B7D2211650 for ; Mon, 20 Sep 2021 13:34:31 +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 18KDYVUN084821 for ; Mon, 20 Sep 2021 13:34:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 18KDYVkJ084820 for fs@FreeBSD.org; Mon, 20 Sep 2021 13:34:31 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 245430] ZFS boot failure following memory exhaustion Date: Mon, 20 Sep 2021 13:34:32 +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: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jwb@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245430 Jason W. Bacon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Overcome By Events --- Comment #5 from Jason W. Bacon --- After repeated occurrences of the issue on my office workstation (4-disk RAIDZ), I have not been able to reproduce the problem since upgrading to 12= .2. I also set up a test machine (3-disk RAIDZ on an old tower system) running 13.0. I've given it a good pounding, filled the filesystem, and have not b= een able to reproduce the issue there. Closing this issue since it seems to be resolved by recent updates. I'll k= eep maintaining the test machine for the foreseeable future and we can use it f= or diagnostics if the problem returns. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Wed Sep 22 23:21:31 2021 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 71FC4175991C for ; Wed, 22 Sep 2021 23:21:31 +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 4HFDnl2fDRz3n90 for ; Wed, 22 Sep 2021 23:21:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 3B982203EA for ; Wed, 22 Sep 2021 23:21:31 +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 18MNLVRW090080 for ; Wed, 22 Sep 2021 23:21:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 18MNLVhX090079 for fs@FreeBSD.org; Wed, 22 Sep 2021 23:21:31 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 246962] fsck_ffs frequently requires multiple runs Date: Wed, 22 Sep 2021 23:21:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246962 --- Comment #1 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3Db31c5a25321363ab95c1642dffc6e9231= 9dc42ce commit b31c5a25321363ab95c1642dffc6e92319dc42ce Author: Kirk McKusick AuthorDate: 2021-09-22 23:16:39 +0000 Commit: Kirk McKusick CommitDate: 2021-09-22 23:20:19 +0000 Eliminate an unnecessary rerun request in fsck_ffs. When fsck_ffs is running in preen mode and finds a zero-length director= y, it deletes that directory. In doing this operation, it unnecessary set its internal flag saying that fsck_ffs needed to be rerun. This patch deletes the rerun request for this case. Reported by: Mark Johnson PR: 246962 MFC after: 1 week Sponsored by: Netflix sbin/fsck_ffs/dir.c | 1 - 1 file changed, 1 deletion(-) --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Wed Sep 22 23:26:46 2021 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 29B89175AF80 for ; Wed, 22 Sep 2021 23:26:46 +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 4HFDvp0fFJz3pWS for ; Wed, 22 Sep 2021 23:26:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 EA7CF2088B for ; Wed, 22 Sep 2021 23:26:45 +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 18MNQjh3093397 for ; Wed, 22 Sep 2021 23:26:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 18MNQj4t093396 for fs@FreeBSD.org; Wed, 22 Sep 2021 23:26:45 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 246962] fsck_ffs frequently requires multiple runs Date: Wed, 22 Sep 2021 23:26:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246962 Kirk McKusick changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress --- Comment #2 from Kirk McKusick --- I encountered this problem recently and discovered that fsck is unnecessari= ly setting the `needs rerun' flag when clearing zero-length directories. I have removed the unnecessary rerun request. If you see any recurrence of this problem, let me know. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sat Sep 25 15:19:50 2021 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 2770517C86BC for ; Sat, 25 Sep 2021 15:19:50 +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 4HGsyZ0Y4Hz4gQg for ; Sat, 25 Sep 2021 15:19:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 E65CF4BD8 for ; Sat, 25 Sep 2021 15:19:49 +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 18PFJnh9045026 for ; Sat, 25 Sep 2021 15:19:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 18PFJnXl045025 for fs@FreeBSD.org; Sat, 25 Sep 2021 15:19:49 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 258208] [zfs] locks up when using rollback or destroy on both 13.0-RELEASE & sysutils/openzfs port Date: Sat, 25 Sep 2021 15:19:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 13.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258208 --- Comment #7 from Mark Johnston --- I am not sure how best to fix this. To elaborate a bit more, the deadlock occurs because a rollback does a suspend/resume of the target fs. This involves taking the teardown write lock; one thing we do with the lock held= is call zfs_rezget() on all vnodes associated with the filesystem, which among other things throws away all data cached in the page cache. This requires pages to be busied with the ZFS write lock held, so I am inclined to think = that zfs_freebsd_getpages() should be responsible for breaking the deadlock as it does in https://cgit.freebsd.org/src/commit/?id=3Dcd32b4f5b79c97b293f7be3fe9ddfc902= 4f7d734 . zfs_freebsd_getpages() could perhaps trylock and upon failure return some EAGAIN-like status to ask the fault handler to retry, but I don't see a way= to do that - vm_fault_getpages() squashes the error and does not allow the pag= er to return KERN_RESOURCE_SHORTAGE. Alternately, zfs_freebsd_getpages() could perhaps wire and unbusy the page = upon a trylock failure. Once it successfully acquires the teardown read lock, it could re-lookup the fault page and compare or re-insert the wired page if necessary. OTOH I cannot see how this is handled on Linux. In particular, I do not see how their zfs_rezget() invalidates the page cache. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sat Sep 25 19:28:39 2021 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 8C30517DF4CB for ; Sat, 25 Sep 2021 19:28:54 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HGzTx4qgNz3KZQ for ; Sat, 25 Sep 2021 19:28:53 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-ed1-x529.google.com with SMTP id y12so14135817edo.9 for ; Sat, 25 Sep 2021 12:28:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=xVQkdG6gBoCSUXLf0OqvaxCNYN4qsrPb0pBHL0UdmO4=; b=EydMdB8vPbYGLX91LsLprL3E2jLPzv+LaPOUgz8RJoun2rELE+HiW0Jhi3G7uaYfxF cPp8w5iE9p9wpqEbGksXdULXno1kRtXiY2rPpJWVAL00Dlt825QDHQp1qHALbZm9OlQz OQkQr9YEP5afnsjrhinPwZE9oyqZwNPEFJriJX92BxTU1JbvQwaCsVxrylPKXc8ByUUO gvlQR7btalr0ZQlDT/56RGcM4dZVUeUvkFcQphtqtx7dHlPMiU43qxg+A+F/qy1SUYMC QHWOF4MNc310QSeVx5tPHtM1svF0HN8iKn0aGDFVCeTEe5dRWfVVRQT8NyShHbse3tnF TN+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xVQkdG6gBoCSUXLf0OqvaxCNYN4qsrPb0pBHL0UdmO4=; b=bg34d50AU8bY15ssZIo5AC3J6iVoTFCg60KnTUN2G8tD2H7FuHEM0FcdvdbgiRLjLS 9jDnlyq7E4bLD7j+oGjK+tuS5A9rYCFjohD+wwppvNJzIxIQj3uQQ7PN3Rn/IBGnm6Io SLomCTN1O4Ck4KLR1+cBrNmFIWS+vuhJtkSR02fnbePcpVzCcszRe9GthFqax1+gyPEw P/X3ctWhZ5pW+dxP7GkBzqCa6KkB0C/E9uxwvQkafReWmB3UdjnZeHxkxF5lvh8pXnuj Tkjr3AXl30BuJ9I3HZ+iDtcPRvdDHXOOzSQC/6Bag5iBMXYz9ywbR9AqJECf6ok7uXWs J71g== X-Gm-Message-State: AOAM532sPbnO8TAquEf4uTceOZ1f7Zj3pvntY5hV9f9eVmShJLZsFsCH qSeIeV1aLjyLDChDu/qSLTkR8hj+RoamP8Q5Mu2LVyQzog== X-Google-Smtp-Source: ABdhPJzyApdWsQScPwareuOUa7JaPz8aJFpZw05C4b+u5hOU+YHQGXmeLPZHZWvNAGdbi0qmyDb6uDoYUcHTY1Mk9sc= X-Received: by 2002:a17:906:1e16:: with SMTP id g22mr1749314ejj.471.1632598131539; Sat, 25 Sep 2021 12:28:51 -0700 (PDT) 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 From: Zaphod Beeblebrox Date: Sat, 25 Sep 2021 15:28:39 -0400 Message-ID: Subject: ZFS errors with two HEX numbers. To: freebsd-fs Content-Type: multipart/alternative; boundary="000000000000b1030f05ccd6df75" X-Rspamd-Queue-Id: 4HGzTx4qgNz3KZQ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=EydMdB8v; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of zbeeble@gmail.com designates 2a00:1450:4864:20::529 as permitted sender) smtp.mailfrom=zbeeble@gmail.com X-Spamd-Result: default: False [-3.90 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::529:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: Y --000000000000b1030f05ccd6df75 Content-Type: text/plain; charset="UTF-8" I've got a ZFS pool --- 3 x 8 x 4T disks in a RAIDZ2 configuration. Every few months I scrub them. This time, curiously, it came up with an error. All the disks in a vdev simultaneously give an error when this is scanned.... thusly: raidz2-3 ONLINE 0 0 0 gpt/v1-f0 ONLINE 0 0 1 gpt/v1-f1 ONLINE 0 0 1 gpt/v1-f2 ONLINE 0 0 1 gpt/v1-f3 ONLINE 0 0 1 gpt/v1-f4 ONLINE 0 0 1 gpt/v1-f5 ONLINE 0 0 1 gpt/v1-f6a ONLINE 0 0 1 gpt/v1-f7b ONLINE 0 0 1 ... and if I add -v to the status, I see the following right now: errors: Permanent errors have been detected in the following files: <0x57b2>:<0x73ab46> Now... since that happened, I have scrubbed twice more. The first number changes each time. Last scrub it was: <0x4223>:<0x73ab46>. Note the last number is not changing. I have done some googling and found that this might be something that got corrupted on delete or somesuch. My OCD would like to know what 0x4223 maps to (or now 0x57b2) s.t. I could find it and remove it. I _think_ this is a snapshot reference? Anyways... any help in tracking this down would be appreciated. For those who've read this far, here's the full zfs scrub -v output... If you're all intensely curious, the last letter following the drive number tracks the number of times a drive has been replaced. pool: vr1 state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A scan: scrub repaired 0B in 1 days 05:01:08 with 1 errors on Fri Sep 24 23:23:34 2021 config: NAME STATE READ WRITE CKSUM vr1 ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gpt/v1-d0 ONLINE 0 0 0 gpt/v1-d1 ONLINE 0 0 0 gpt/v1-d2 ONLINE 0 0 0 gpt/v1-d3 ONLINE 0 0 0 gpt/v1-d4a ONLINE 0 0 0 gpt/v1-d5 ONLINE 0 0 0 gpt/v1-d6a ONLINE 0 0 0 gpt/v1-d7a ONLINE 0 0 0 raidz2-2 ONLINE 0 0 0 gpt/v1-e0c ONLINE 0 0 0 gpt/v1-e1c ONLINE 0 0 0 gpt/v1-e2b ONLINE 0 0 0 gpt/v1-e3b ONLINE 0 0 0 gpt/v1-e4b ONLINE 0 0 0 gpt/v1-e5a ONLINE 0 0 0 gpt/v1-e6a ONLINE 0 0 0 gpt/v1-e7d ONLINE 0 0 0 raidz2-3 ONLINE 0 0 0 gpt/v1-f0 ONLINE 0 0 1 gpt/v1-f1 ONLINE 0 0 1 gpt/v1-f2 ONLINE 0 0 1 gpt/v1-f3 ONLINE 0 0 1 gpt/v1-f4 ONLINE 0 0 1 gpt/v1-f5 ONLINE 0 0 1 gpt/v1-f6a ONLINE 0 0 1 gpt/v1-f7b ONLINE 0 0 1 logs gpt/vr1log ONLINE 0 0 0 cache gpt/vr1cache ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: <0x57b2>:<0x73ab46> --000000000000b1030f05ccd6df75-- From nobody Sat Sep 25 22:00:59 2021 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 AE00217CD322 for ; Sat, 25 Sep 2021 22:01:11 +0000 (UTC) (envelope-from SRS0=/8x4=OP=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HH2sg3vj7z3m6H for ; Sat, 25 Sep 2021 22:01:11 +0000 (UTC) (envelope-from SRS0=/8x4=OP=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8FB2828417; Sun, 26 Sep 2021 00:01:03 +0200 (CEST) Received: from illbsd.quip.test (ip-78-45-215-131.net.upcbroadband.cz [78.45.215.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 6C79C28411; Sun, 26 Sep 2021 00:01:00 +0200 (CEST) Subject: Re: ZFS errors with two HEX numbers. To: Zaphod Beeblebrox , freebsd-fs References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> Date: Sun, 26 Sep 2021 00:00:59 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 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 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4HH2sg3vj7z3m6H X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 25/09/2021 21:28, Zaphod Beeblebrox wrote: > I've got a ZFS pool --- 3 x 8 x 4T disks in a RAIDZ2 configuration. Every > few months I scrub them. This time, curiously, it came up with an error. > All the disks in a vdev simultaneously give an error when this is > scanned.... thusly: > > raidz2-3 ONLINE 0 0 0 > gpt/v1-f0 ONLINE 0 0 1 > gpt/v1-f1 ONLINE 0 0 1 > gpt/v1-f2 ONLINE 0 0 1 > gpt/v1-f3 ONLINE 0 0 1 > gpt/v1-f4 ONLINE 0 0 1 > gpt/v1-f5 ONLINE 0 0 1 > gpt/v1-f6a ONLINE 0 0 1 > gpt/v1-f7b ONLINE 0 0 1 > > ... and if I add -v to the status, I see the following right now: > > errors: Permanent errors have been detected in the following files: > <0x57b2>:<0x73ab46> > > Now... since that happened, I have scrubbed twice more. The first number > changes each time. Last scrub it was: <0x4223>:<0x73ab46>. Note the last > number is not changing. > > I have done some googling and found that this might be something that got > corrupted on delete or somesuch. My OCD would like to know what 0x4223 > maps to (or now 0x57b2) s.t. I could find it and remove it. I _think_ this > is a snapshot reference? I have seen this in the past. It was corruption on some deleted file preserved on snapshot. Once I deleted snapshots this error disappeared. [...] Miroslav Lachman From nobody Sat Sep 25 23:20:08 2021 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 E30D617D3455 for ; Sat, 25 Sep 2021 23:20:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f47.google.com (mail-ot1-f47.google.com [209.85.210.47]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HH4d641b9z3rDY for ; Sat, 25 Sep 2021 23:20:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f47.google.com with SMTP id h9-20020a9d2f09000000b005453f95356cso18589299otb.11 for ; Sat, 25 Sep 2021 16:20:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WJd2uvBg3G9OUrE1sZBOS7dTOAMaWxSrqeR7Yqfpq7Y=; b=zRug0jnx7TRW9u/ylt2EGR9/XJzojSJUHcf6rY+9K/wHjNbYYwuXwLIHA91nsQHNtU hru36qv5CwgPdgqdkjOIMHuBbCFoY0IMhaiSg2RNPU0QEJK74/4zN3V0zjdyQrLTrQNh PzWVMaT4+k7kn+OvfIBacxuszbY0NjZ00VGj1f2dF4aDjSVfkJ9CdE6lAbjr0a+q9Ax5 9OY3Dem4+Anyoj2lbbcRq1rNbtT0l3HPO4XvLkdxOsiZjyoVIDiNKBABCeNuolaowmJ8 DdjHhhrWy+J3xNrvhHm3jPhmi2ERWuQo70fPnjc3x4moyE6IYOvk4IuUKXK8uIiMB2z5 EIUw== X-Gm-Message-State: AOAM532dU087QOCx66xLGQdnuOMjFtOb/x0mNAz2YG6wBP1ozX5iq0BE V94JyG0jqv11cFrz/oK5Q5IKyMauixSQKNN05vD26T7z X-Google-Smtp-Source: ABdhPJyTF0go2kPoP3R7oAqaQcX9nvx8uw02Hw03Ca4+WZbSKGJnI5g2cI4Vhb549TN7EvCdPXqcarEN8wAV8t9+Qtw= X-Received: by 2002:a9d:6c91:: with SMTP id c17mr10571192otr.114.1632612019609; Sat, 25 Sep 2021 16:20:19 -0700 (PDT) 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 References: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> In-Reply-To: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> From: Alan Somers Date: Sat, 25 Sep 2021 17:20:08 -0600 Message-ID: Subject: Re: ZFS errors with two HEX numbers. To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Zaphod Beeblebrox , freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HH4d641b9z3rDY X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sat, Sep 25, 2021 at 4:01 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > > On 25/09/2021 21:28, Zaphod Beeblebrox wrote: > > I've got a ZFS pool --- 3 x 8 x 4T disks in a RAIDZ2 configuration. Every > > few months I scrub them. This time, curiously, it came up with an error. > > All the disks in a vdev simultaneously give an error when this is > > scanned.... thusly: > > > > raidz2-3 ONLINE 0 0 0 > > gpt/v1-f0 ONLINE 0 0 1 > > gpt/v1-f1 ONLINE 0 0 1 > > gpt/v1-f2 ONLINE 0 0 1 > > gpt/v1-f3 ONLINE 0 0 1 > > gpt/v1-f4 ONLINE 0 0 1 > > gpt/v1-f5 ONLINE 0 0 1 > > gpt/v1-f6a ONLINE 0 0 1 > > gpt/v1-f7b ONLINE 0 0 1 > > > > ... and if I add -v to the status, I see the following right now: > > > > errors: Permanent errors have been detected in the following files: > > <0x57b2>:<0x73ab46> > > > > Now... since that happened, I have scrubbed twice more. The first number > > changes each time. Last scrub it was: <0x4223>:<0x73ab46>. Note the last > > number is not changing. > > > > I have done some googling and found that this might be something that got > > corrupted on delete or somesuch. My OCD would like to know what 0x4223 > > maps to (or now 0x57b2) s.t. I could find it and remove it. I _think_ this > > is a snapshot reference? > > I have seen this in the past. It was corruption on some deleted file > preserved on snapshot. Once I deleted snapshots this error disappeared. > > [...] > > Miroslav Lachman I believe the first number is the objset number, where the objset can be either a dataset or a snapshot. The corrupt block likely exists in multiple snapshots, but "zpool status" will show only one, whichever it happened to find first. You can see the objset numbers for datasets (but not snapshots) in the output of "sysctl kstat.zfs". The second number I believe is the object number, and that should never change. From nobody Sun Sep 26 01:45:46 2021 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 ABAE417DF644 for ; Sun, 26 Sep 2021 01:46:10 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "vtr.rulingia.com", Issuer "R3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HH7sF2k3Wz4WKD for ; Sun, 26 Sep 2021 01:46:08 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (2001-44b8-31fc-0d00-9de3-3c03-e973-46a7.static.ipv6.internode.on.net [IPv6:2001:44b8:31fc:d00:9de3:3c03:e973:46a7]) by vtr.rulingia.com (8.16.1/8.16.1) with ESMTPS id 18Q1jq4D060810 (version=TLSv1.3 cipher=AEAD-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 26 Sep 2021 11:45:58 +1000 (AEST) (envelope-from peter@rulingia.com) DKIM-Filter: OpenDKIM Filter v2.10.3 vtr.rulingia.com 18Q1jq4D060810 X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.16.1/8.16.1) with ESMTPS id 18Q1jkLG021949 (version=TLSv1.3 cipher=AEAD-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 26 Sep 2021 11:45:46 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.16.1/8.16.1/Submit) id 18Q1jkRC021948 for freebsd-fs@freebsd.org; Sun, 26 Sep 2021 11:45:46 +1000 (AEST) (envelope-from peter) Date: Sun, 26 Sep 2021 11:45:46 +1000 From: Peter Jeremy To: freebsd-fs@freebsd.org Subject: Backing up using ZFS native encryption. Message-ID: 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 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="N/Y8tXKbRJGNLlsG" Content-Disposition: inline X-PGP-Key: http://www.rulingia.com/keys/peter.pgp X-Rspamd-Queue-Id: 4HH7sF2k3Wz4WKD X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=quarantine) header.from=rulingia.com; spf=pass (mx1.freebsd.org: domain of peter@rulingia.com designates 2001:19f0:5801:ebe:5400:1ff:fe53:30fd as permitted sender) smtp.mailfrom=peter@rulingia.com X-Spamd-Result: default: False [-4.95 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[peter]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-0.05)[-0.052]; DMARC_POLICY_ALLOW(-0.50)[rulingia.com,quarantine]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5800::/38, country:US]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --N/Y8tXKbRJGNLlsG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm trying to use ZFS native encryption to allow me to do backups to a remote system without that system access to the backup contents. According to the documentation, "zfs send --raw ..." can be used to send encrypted backups but it's not clear how to create a suitable destination pool. Using a 13-stable system from about a week ago (g5f4ba94eb591), I've tried: 1) Creating the destination pool with encryption enabled: # zpool create -O encryption=3Don -O keyformat=3Dpassphrase -O keylocati= on=3Dfile:///boot/zfs/tank.key ztest1 da{0,1}p8 a) Receive without '-F' says I need to use '-F': # zfs send -Rw tank@snapshot | zfs recv -vu ztest1=20 cannot receive new filesystem stream: destination 'ztest1' exists must specify -F to overwrite it b) Receive with '-F' says I can't destroy an encrypted filesystem: # zfs send -Rw tank@snapshot | zfs recv -vuF ztest1=20 cannot receive new filesystem stream: zfs receive -F cannot be used to dest= roy an encrypted filesystem or overwrite an unencrypted one with an encrypt= ed one 2) Creating the destination pool without encryption: # zpool create ztest1 da{0,1}p8 a) Receive without '-F' says I need to use '-F': # zfs send -Rw tank@snapshot | zfs recv -vu ztest1=20 cannot receive new filesystem stream: destination 'ztest1' exists must specify -F to overwrite it b) Receive with '-F' says I can't overwrite unencrypted to encrypted # zfs send -Rw tank@snapshot | zfs recv -vuF ztest1=20 cannot receive new filesystem stream: zfs receive -F cannot be used to dest= roy an encrypted filesystem or overwrite an unencrypted one with an encrypt= ed one What is the magic incantation to actually create a copy of an encrypted pool? --=20 Peter Jeremy --N/Y8tXKbRJGNLlsG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAmFP0MVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzSgZhAAjGwIL9k//kkmgm6IUpruWrzpRax9jdNeoPBT86HBuJB9rczjkz4sUfNz 0DF7NmCZc0rS1BckGL686dqfPA3aqu+1io57/xL7pqXTmbPz+RgxeV5GL7J8LIIx OXa3Yt8D/FGU61KxvRXRt6Ifc8XN47NCM7HWQVeQnAD+p5qiEal/9wvNDyDzKYJ6 BFcfeffc1TtlOzpvQy1dpZKpUtpCer+VVQVyjO9JiJpPCE7mYUwC+dGFWnx5pdAs 6hjDWBtzsP2E8XyL+0e5GTUUVuGpvGVxMrpyiTV4JUstoer9CMA+//3SLGyt0PGB /5f773EanxKHLy2l0X8Mdyg5lWE+Qwfq90/r8BdLZOVZnx/VuChFg9330DHt42IL e/ZxH/ufuBB5aqxLtDCl1uKPxPFLxHRqbKXnaAtTLqUWAag2VqddWW8v6r/jhvMc llnMGKtc9F4GLU49Zzh6ZG0ymnDYjz/GRY2AteovX0Lcq+ENdTkqfdDpwMqa6jhF RHOpGOkAwdrYyXmtto3Yn/wRyUpi8boBm/Tua7VivwwH99ZELUbSASMjnibUUSvn 9+4iY6pzIwcQDxX/tsCRTd7/AhMZzKbAIZxjNTA2dPns9N2Frnm+4R7OvVC96fP1 aK6HkqPn2DVxNUisWKze3yOadfUd+r7hvf18aw64VxV3y18DRC8= =15SG -----END PGP SIGNATURE----- --N/Y8tXKbRJGNLlsG-- From nobody Sun Sep 26 02:04:54 2021 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 87A5917E1572 for ; Sun, 26 Sep 2021 02:05:12 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com [IPv6:2607:f8b0:4864:20::a2b]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HH8HD3J7Gz4YqP for ; Sun, 26 Sep 2021 02:05:12 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: by mail-vk1-xa2b.google.com with SMTP id z202so5570214vkd.1 for ; Sat, 25 Sep 2021 19:05:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xVlTDk/x40aouwuGpxs2OnKvjaF3OFiLPCllW6d2Qdw=; b=JaNrZfUlh/vIv5wlfKzJzRtY8dg/VEE5/4s6rqw7wd6aCMm8GVAWwBl/B2U7PQObmC C0EzvzHD9dbyypBckeuM21oOvbPSa8kUusnIaH3nAPwYytPptdaylpRiE+0DxIDLoyHO xgFUEvXz3Y/NjT00UXm0EKB6N5h7S5Z1hKaoOZ976+fBO34nsqacu1vnspxu+4EudsyA M0G/soM64jAege11s3EweBPgV5t7SJqkMTFli6BKvwQNR93xa8OYAuxYsWoS84d138M3 wjIt8TaoPE8SJ6uHOj+IQOJ5umb7rn41yFn7uhfnfdfAFZyfCBDaejWoDAuIvBhywjg2 lxaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xVlTDk/x40aouwuGpxs2OnKvjaF3OFiLPCllW6d2Qdw=; b=74P4Uvskow3vP7SuOXoOJR1VLqVPoh/T9OJ82iPM/kXmL9cfUop77sF0iscTvxcbgY NWkJnLKI+dYknlUqI2qa+1567WfLmHNX9yF04azF9BPG6VhAsvT0iCbQdtvycZTovkPk Ew7qNDYRTnSiYn9tEvfbw4I7B+9qksXVWdd8Q/FmiOzXsFvQ3CGtSz9I1JqAxhTIbu6c WdusjZ0RykqeEXCUfzxU4HOmO+dWdhrcmHBxs+3w0qnCdrOTwQm0hGUlUhAKhpp9+4qe N/0ZSkGfOvWWLQ8Ai5c1dk0Ib8dVNwYHb5/vtAIiFoy8pDhRauCwiaXxG5cnN/aOwCfE Oyzw== X-Gm-Message-State: AOAM5309Hzq57UxQNkw7xOUY9+qlZxff3D6QOgo0jQinE4+zpBNRWDCP DrIF/1VPVmq/S3/th34RsXI69seMdy0JzR10Y87/rC/5 X-Google-Smtp-Source: ABdhPJxDT6zZEFGeqyqC+oub9gd0C0BfdwhHZ0smOOhhSAOQ5+l9PRrSQP0MBdDwLF8EGZirJe44rH0u1VQ2fYGhSUU= X-Received: by 2002:a1f:1609:: with SMTP id 9mr13271347vkw.10.1632621905690; Sat, 25 Sep 2021 19:05:05 -0700 (PDT) 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 References: In-Reply-To: From: Rich Date: Sat, 25 Sep 2021 22:04:54 -0400 Message-ID: Subject: Re: Backing up using ZFS native encryption. To: Peter Jeremy Cc: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HH8HD3J7Gz4YqP X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N To backup the full contents of an encrypted pool, you can just receive it into a child dataset on another pool. You cannot overwrite an encrypted dataset in-place, or an unencrypted one with an encrypted one, so there is no way to replicate a pool 1:1 if the encryption includes the root dataset. This is one more reason not to put {settings,data} you care about preserving in the root dataset. - Rich On Sat, Sep 25, 2021 at 9:46 PM Peter Jeremy wrote: > > I'm trying to use ZFS native encryption to allow me to do backups to > a remote system without that system access to the backup contents. > According to the documentation, "zfs send --raw ..." can be used to > send encrypted backups but it's not clear how to create a suitable > destination pool. > > Using a 13-stable system from about a week ago (g5f4ba94eb591), I've tried: > 1) Creating the destination pool with encryption enabled: > # zpool create -O encryption=on -O keyformat=passphrase -O keylocation=file:///boot/zfs/tank.key ztest1 da{0,1}p8 > a) Receive without '-F' says I need to use '-F': > # zfs send -Rw tank@snapshot | zfs recv -vu ztest1 > cannot receive new filesystem stream: destination 'ztest1' exists > must specify -F to overwrite it > b) Receive with '-F' says I can't destroy an encrypted filesystem: > # zfs send -Rw tank@snapshot | zfs recv -vuF ztest1 > cannot receive new filesystem stream: zfs receive -F cannot be used to destroy an encrypted filesystem or overwrite an unencrypted one with an encrypted one > > 2) Creating the destination pool without encryption: > # zpool create ztest1 da{0,1}p8 > a) Receive without '-F' says I need to use '-F': > # zfs send -Rw tank@snapshot | zfs recv -vu ztest1 > cannot receive new filesystem stream: destination 'ztest1' exists > must specify -F to overwrite it > b) Receive with '-F' says I can't overwrite unencrypted to encrypted > # zfs send -Rw tank@snapshot | zfs recv -vuF ztest1 > cannot receive new filesystem stream: zfs receive -F cannot be used to destroy an encrypted filesystem or overwrite an unencrypted one with an encrypted one > > What is the magic incantation to actually create a copy of an > encrypted pool? > > -- > Peter Jeremy From nobody Sun Sep 26 04:25:57 2021 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 1549017CCADB for ; Sun, 26 Sep 2021 04:26:13 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HHCPw4qKYz4ljR; Sun, 26 Sep 2021 04:26:12 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-ed1-x52e.google.com with SMTP id l8so5850555edw.2; Sat, 25 Sep 2021 21:26:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2unzDKT8fbjL3d3lsMgA5oMKEDcagcItr1K7v5pJv04=; b=RmdN/EDGUIFSe3Ssrcm0vHW0d1CWNfrLyRbvlXZAsTFEpKcwnjJlZpwsIGjixEs1Vy PQ0LZalXOOX3m/k6lcABALfKWg7ELAB8DYMQntvTYGeyD1bs/BaIBf+kq5ywn2P71y2B VDBeyHsbIrSYRfMaNRZmLBTTEg5TMNKaGXkdjCyIxFhZp2Uiy9lQVsbxigafcfFbBN6+ 08bo6oNh3Y3oVYt6fbDffUF4He/ZJDg38vmSfnC6XwbbI0yYham4cX2xHqmJRHnDcege MXIDHL6rt8jLNeBQYPsNsBl2y5t6QkWna/Px5hAeKSljAccAe8ilYutm3Se1RBugAPeJ ySEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2unzDKT8fbjL3d3lsMgA5oMKEDcagcItr1K7v5pJv04=; b=8AZv1k7dmQ2i1dy6e4QajKPca8pFLb+wTSDeE3/gRmItRLS/73Qd5qoQXNeVy7iwa6 qqiPh+mP8/Slu+IrXCXQYWzJOSpfHlypzsM4RId6cjzRzcMfaalgEgjo9qOFYh50kBI4 KcG+ckQdHnNRUylqVzdkrxNrk3n0vLWXQ/7baxq5mN21lbDoU3q0MeYeiKdEGJ/8Dugd rROIH+0S8vx9bc0q1SrDQrz1zneZtHIDeOOxJOPy92qs6hkzDVHISAz7QkWQG/TKErKQ xo66l8OKs3EEveMRSTVbJHIhXYrK87PtikDyZvfrCpQHYZlDEa3yx+t3osT3oJIrL0jO rKHw== X-Gm-Message-State: AOAM531GnQ3hZpTFxthVBkONAMqjE1U5QubgktikUqTWCIzdb7d5D4Sg Ao216kPKejcabnNUVqCaSE2rBiv/tjHLUIScJD+hvGA= X-Google-Smtp-Source: ABdhPJxvFveySBcKD4tFuda0vjKUohWcQ0aqIWeNE+U8ydCJlhWcEN4DcxP+xBp2pGyRw4dv5azpACEihlk0ELXVKQU= X-Received: by 2002:a17:906:c205:: with SMTP id d5mr20469141ejz.74.1632630370184; Sat, 25 Sep 2021 21:26:10 -0700 (PDT) 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 References: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> In-Reply-To: From: Zaphod Beeblebrox Date: Sun, 26 Sep 2021 00:25:57 -0400 Message-ID: Subject: Re: ZFS errors with two HEX numbers. To: Alan Somers Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs Content-Type: multipart/alternative; boundary="00000000000043b10605ccde6151" X-Rspamd-Queue-Id: 4HHCPw4qKYz4ljR X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --00000000000043b10605ccde6151 Content-Type: text/plain; charset="UTF-8" I looked through sysctl kstat.zfs --- Neither number appears. Is there some similar way I can list snapshots? I thought ZFS listed snapshots when listing them here...? On Sat, Sep 25, 2021 at 7:20 PM Alan Somers wrote: > On Sat, Sep 25, 2021 at 4:01 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > On 25/09/2021 21:28, Zaphod Beeblebrox wrote: > > > I've got a ZFS pool --- 3 x 8 x 4T disks in a RAIDZ2 configuration. > Every > > > few months I scrub them. This time, curiously, it came up with an > error. > > > All the disks in a vdev simultaneously give an error when this is > > > scanned.... thusly: > > > > > > raidz2-3 ONLINE 0 0 0 > > > gpt/v1-f0 ONLINE 0 0 1 > > > gpt/v1-f1 ONLINE 0 0 1 > > > gpt/v1-f2 ONLINE 0 0 1 > > > gpt/v1-f3 ONLINE 0 0 1 > > > gpt/v1-f4 ONLINE 0 0 1 > > > gpt/v1-f5 ONLINE 0 0 1 > > > gpt/v1-f6a ONLINE 0 0 1 > > > gpt/v1-f7b ONLINE 0 0 1 > > > > > > ... and if I add -v to the status, I see the following right now: > > > > > > errors: Permanent errors have been detected in the following files: > > > <0x57b2>:<0x73ab46> > > > > > > Now... since that happened, I have scrubbed twice more. The first > number > > > changes each time. Last scrub it was: <0x4223>:<0x73ab46>. Note the > last > > > number is not changing. > > > > > > I have done some googling and found that this might be something that > got > > > corrupted on delete or somesuch. My OCD would like to know what 0x4223 > > > maps to (or now 0x57b2) s.t. I could find it and remove it. I _think_ > this > > > is a snapshot reference? > > > > I have seen this in the past. It was corruption on some deleted file > > preserved on snapshot. Once I deleted snapshots this error disappeared. > > > > [...] > > > > Miroslav Lachman > > I believe the first number is the objset number, where the objset can > be either a dataset or a snapshot. The corrupt block likely exists in > multiple snapshots, but "zpool status" will show only one, whichever > it happened to find first. You can see the objset numbers for > datasets (but not snapshots) in the output of "sysctl kstat.zfs". The > second number I believe is the object number, and that should never > change. > --00000000000043b10605ccde6151-- From nobody Sun Sep 26 04:26:33 2021 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 8303717CCED2 for ; Sun, 26 Sep 2021 04:26:46 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HHCQZ2t31z4mFX for ; Sun, 26 Sep 2021 04:26:46 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-ed1-x52d.google.com with SMTP id y12so17374024edo.9 for ; Sat, 25 Sep 2021 21:26:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tNt/kO/tOg3LvyaGXGq59bWBV5lHsG2WyneYYSt1qXQ=; b=AkUJ3SYzWUJzwQPqtn4bC69yDzevb3liwTt0hsGetB6jaINlgLBPiIu5BqcBlzKYxB sdYRU2Wqs8f7LCC1IY+XvhPHnjvHXrzX63raFmy1s/tGhMmb8S56YQGTjdGWNN+Mo5Gt Ex6l6JGYAImgfyAeVEvX+B4zK7qBxz/8H7HP3sPE9MSlN0gQaEZgzLIcbItzCYWtkOwK O1NZUnF8l4R3qzDMjIHnejSCEHQa3ePD5EuELnQp3+L52hXcM5RzhRSoZtdwOyKyVhZ3 8x4TFDs8/PTvd2u+bCxqEh5N2UhjT3jj2EGHkLr8LMxPomU+fkyrDGaP8qT1jqnbFus+ QiGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tNt/kO/tOg3LvyaGXGq59bWBV5lHsG2WyneYYSt1qXQ=; b=oFTHFSMU9c4uJHSQCRpyF/nzWefPm8ILyf8adu+DX7zClWXP4rByaPp6WwqfmHQgrU EkIKTiQBs9vJxqCEX+7o4KTbbpSUtmK0vOlWhd2BLGi1UTDdHbanrXS4uX/Gh+trAMYq YDhj7G3OyQxIF3i01S401thoD20MVqZzB5l9KFETxgiAxz1vhXo/8eo7HOUDRbCuVQWm vyxXCPJpe9Op2B2bymb5eQVjDe2kOUnaSRcXAg4gOpp3isa39sNpmFcV27IdfxlnXCKb id8XLUiDDcECuN7lFa9aP7sfxRQVr3Ka6yu8QhSX2tJ8NTxX37A0Lw5xq5Nc3wHBlQQu 4wVA== X-Gm-Message-State: AOAM533fsXHCrJ54iNoTYSivSHgjgiFopMGWc3TnjvwoUDvDDZOS4arV BFu4NIBYqPFmT7m/Fb3H47eU+c7lCM4lUbWd6EDRCgA= X-Google-Smtp-Source: ABdhPJyb5lB/mK4FwUPbSQW2LwthV4I8IplVV0R86q6tAw263P8k99JZ+uNA5f2mD4nUPTgltsIlm8Mc2A9Q+XZ6Mdw= X-Received: by 2002:a17:906:3b5b:: with SMTP id h27mr3407491ejf.182.1632630405559; Sat, 25 Sep 2021 21:26:45 -0700 (PDT) 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 References: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> In-Reply-To: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> From: Zaphod Beeblebrox Date: Sun, 26 Sep 2021 00:26:33 -0400 Message-ID: Subject: Re: ZFS errors with two HEX numbers. To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-fs Content-Type: multipart/alternative; boundary="0000000000005f796005ccde6397" X-Rspamd-Queue-Id: 4HHCQZ2t31z4mFX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000005f796005ccde6397 Content-Type: text/plain; charset="UTF-8" How do I find which snapshot it's in? On Sat, Sep 25, 2021 at 6:01 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > I have seen this in the past. It was corruption on some deleted file > preserved on snapshot. Once I deleted snapshots this error disappeared. > > [...] > > Miroslav Lachman > --0000000000005f796005ccde6397-- From nobody Sun Sep 26 04:52:59 2021 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 885E217CF80D for ; Sun, 26 Sep 2021 04:53:11 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-ua1-x92d.google.com (mail-ua1-x92d.google.com [IPv6:2607:f8b0:4864:20::92d]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HHD133HlKz4ntc for ; Sun, 26 Sep 2021 04:53:11 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: by mail-ua1-x92d.google.com with SMTP id r8so9691221uap.0 for ; Sat, 25 Sep 2021 21:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oAqNMKvfT5T3hpfiEmYh96IJhqREZmmY8vjZ2PaY6CA=; b=ijAGlXq9vGDEsua3Hnjy/s7IpPbAFConR5QAu7mL6pkz0RA6/1Mff/TvpqIInkxpzv AhHG6ITtyWeujCp+0phdm0pUynB/DSAbr8gFGwOOEg2cxXyNRn6ttWqElVZYErKgSDmz Awp+T10sq0cdzsxMosuNcZRt0R9BgpAZi9zU/AFVTcTSSkf/QX/SWMYyjt7Q02/Jce9h 9t9wwxKOP0CKxkzTrb2A3hdG6RJqJ07H8Ulb+ymjLyE3cqY+zfZw97mkarDnakRfwSC8 /6v64Y+HXKtUFJ0yhnNq0JEnTxpdw00AFAZB4Ds7Q0ITPhESPWwxmFwkrNbAWLjQUyRi PSog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oAqNMKvfT5T3hpfiEmYh96IJhqREZmmY8vjZ2PaY6CA=; b=akpW/P/HWeU+bOHNOcaMiXA2ckAqpK6OAMFWi78A9bNtQ4Iwaba5bMCMD421x8pmjl 2AKi0a8OwgyjOkMzzFar5nyTm2wHawnb9KNQSSZz8JQE/9iYL3M4yR36INpCcHvDaDPD lSSX6oz3bKSkAhiqjOXy/YFFEuJd3Qjqt678dSKHZ11Vi8n3+j7n0Sx626hYUaTRuO9B NLK2gsPURN2P82okH0DXONCSDxTBmQ+yY20AMh6vIKZ4dd2AhDOsLj1R/zxf1T8Tq2GS 9lU3UEgj1QNnI+VoxjO6cOAcPZ3BWUUUidj1imoauJlHb9pcIzKTdWHmE5+lWhbtwZUZ JoQA== X-Gm-Message-State: AOAM533ODzIAHur3tC7np+/jXwYOb36skymPagA0+RPgc5FyskD58tuy 2tBfm2d16tOLa2cfydlHsHPiLM/NxYdhXngTLTh7+I5jCdQ= X-Google-Smtp-Source: ABdhPJx6LIek9vb5IIc0jCfHQZHcQ8BTsH+Ec41+jDReiYASa74SgJHBaxTH+RYw540P38aKtRbSbKe2kp9oSmQH21Q= X-Received: by 2002:a9f:3852:: with SMTP id q18mr14645567uad.79.1632631990859; Sat, 25 Sep 2021 21:53:10 -0700 (PDT) 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 References: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> In-Reply-To: From: Rich Date: Sun, 26 Sep 2021 00:52:59 -0400 Message-ID: Subject: Re: ZFS errors with two HEX numbers. To: Zaphod Beeblebrox Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4HHD133HlKz4ntc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N I don't have a testpool handy to confirm it, but I would expect you to be able to do something like zdb -ddddd [pool]/[objsetid in hex] [objectid in hex] e.g. zdb -ddddd vr1/0x57b2 0x73ab46 Or failing that, drop the object id (and then probably some of the -d, that gets real verbose). - Rich On Sun, Sep 26, 2021 at 12:27 AM Zaphod Beeblebrox wrote: > > How do I find which snapshot it's in? > > On Sat, Sep 25, 2021 at 6:01 PM Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > > > > I have seen this in the past. It was corruption on some deleted file > > preserved on snapshot. Once I deleted snapshots this error disappeared. > > > > [...] > > > > Miroslav Lachman > > From nobody Sun Sep 26 21:00:29 2021 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 4AAF117D56EA for ; Sun, 26 Sep 2021 21:00:30 +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 4HHdT942lZz50Wp for ; Sun, 26 Sep 2021 21:00:29 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) 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 33FD824629 for ; Sun, 26 Sep 2021 21:00:29 +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 18QL0Tbl057001 for ; Sun, 26 Sep 2021 21:00:29 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 18QL0TRo057000 for fs@FreeBSD.org; Sun, 26 Sep 2021 21:00:29 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202109262100.18QL0TRo057000@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 26 Sep 2021 21:00:29 +0000 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 Content-Type: multipart/alternative; boundary="16326900291.BEE59feB.56155" Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: Y --16326900291.BEE59feB.56155 Date: Sun, 26 Sep 2021 21:00:29 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 211491 | System hangs after "Uptime" on reboot with ZFS Open | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 237067 | ZFS: Crash in vdev_dtl_reassess when using GELI w Open | 240831 | zfs: Panic during snapshot on 12.1-STABLE r352648 Open | 243973 | [zfs] rollback segmentation fault Open | 244656 | zfs: resilver doesn't provide enough information Open | 244692 | gjournal: Does not support TRIM Open | 244899 | [PATCH] zfs: xattr on a symlink target > 136 caus Open | 251035 | ZFS: Allow 64 bit ZFS to support 32 bit ioctls (W 9 problems total for which you should take action. --16326900291.BEE59feB.56155-- From nobody Sun Sep 26 21:31:18 2021 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 2C5D017DB39A for ; Sun, 26 Sep 2021 21:31:37 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HHf950WYLz56S0 for ; Sun, 26 Sep 2021 21:31:37 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-ed1-x529.google.com with SMTP id ee50so60712959edb.13 for ; Sun, 26 Sep 2021 14:31:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zmCa53L5IYAHYImvznLO47Qdg8XdPCgiZVNFtTWsTBE=; b=mPL/B0ebbNg1Da6ItwFLQq4oLcwXmJazKw91cQIvM8FAgvktzLqTBehBKc8WF25jmp 5rhifouqnWK61v2YQajsLL9TJ5ZQkLBd42FTtzMl/T9jnr8L2JChzJT+z6prUoW5Wwn4 JFp+Z9Pxoz026rVMgL2ypErRDdCRb8u3kUuoVBoXIvd/2xzjbaklVjBWxbnzspMP/OYl tNQ9J6xh9Qp2Vu+1woAVA6wvCN+5T9RSe/ojP71SFhfh7eNtqw4jmFJ+zrGmOqnyiF/P DgJSfBSKsp9fsIK2z86dMztlXRbyHYhi9VJ7SVY4k3oMu31xfhmGkX4uS6sNAGGhlxDC ylkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zmCa53L5IYAHYImvznLO47Qdg8XdPCgiZVNFtTWsTBE=; b=b+K9BR783TC80zziXkwz7vJ6qay+zT3DBxpNKMI/Kqhp1Ch8Lv9rpqADPKtLAdyfog bcTlv6Kh/JD9FDaoiaPU/FmhB4+fkj8XxbEOXMiQHCpdrLBKrHoSWEp34Uka9AHS6Alb i/lByzGke1SDLhuuFAfFCJPiGKRKyWv00xejUx4MODpRr48TXNMjOerdAsPAG4q+pvMK +0WEPanuLlIY90SCyHyiM4+SHw53q86cZBtX5l9ABDeqTvCz1hwLI6MqXWqCTgzmlfYZ K0ExZn7ukp9By8+G6SYJhk+9XHvsvgOpZp3Ru/IDRc5Xtht36PiEMmiA3YxrjL82rSRt jMEA== X-Gm-Message-State: AOAM5307ESZuNs2wmVqfkTJFsY97c1WbXSGnSncgvogl89Ky84/nS2Ys 8QfO+KMcwNHrAj40KOtzClqtM3v6TV7aiz7ObA== X-Google-Smtp-Source: ABdhPJxt/x38UQ+8PLVG1QO6SdSOpqzvYIvQGE5dn9oi1HtvOqitaY25G1Yqrq/nj3BnEVT/lYrBO23AvArxxARzhBo= X-Received: by 2002:a17:906:8396:: with SMTP id p22mr10753603ejx.140.1632691889924; Sun, 26 Sep 2021 14:31:29 -0700 (PDT) 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 References: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> In-Reply-To: From: Zaphod Beeblebrox Date: Sun, 26 Sep 2021 17:31:18 -0400 Message-ID: Subject: Re: ZFS errors with two HEX numbers. To: Rich Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs Content-Type: multipart/alternative; boundary="000000000000206d7f05ccecb422" X-Rspamd-Queue-Id: 4HHf950WYLz56S0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000206d7f05ccecb422 Content-Type: text/plain; charset="UTF-8" Entertaining. That (even with only two --> zdb -dd vr1/0x57b2) gives ... core dump. SIGSEGV in strlen. Dereferencing a NULL. (gdb) bt #0 strlen (str=0xd ) at /usr/src/lib/libc/string/strlen.c:101 #1 0x0000000800f6ea60 in __vfprintf (fp=, locale=0x80102eed8 <__xlocale_global_locale>, fmt0=, ap=) at /usr/src/lib/libc/stdio/vfprintf.c:854 #2 0x0000000800f6b8df in snprintf (str=0x801644400 "", n=, fmt=0x8009ad9b9 "%s/%s") at /usr/src/lib/libc/stdio/snprintf.c:74 #3 0x0000000800a58b76 in zfs_file_open (path=path@entry=0x801644000 "/etc/zfs/zpool.cache", flags=, flags@entry=0, mode=, mode@entry=0, fpp=fpp@entry =0x7fffffe58788) at /usr/src/sys/contrib/openzfs/lib/libzpool/kernel.c:1075 #4 0x0000000800b3e622 in spa_config_load () at /usr/src/sys/contrib/openzfs/module/zfs/spa_config.c:101 #5 0x0000000800b47b39 in spa_init (mode=mode@entry=SPA_MODE_READ) at /usr/src/sys/contrib/openzfs/module/zfs/spa_misc.c:2393 #6 0x0000000800a586ae in kernel_init (mode=1) at /usr/src/sys/contrib/openzfs/lib/libzpool/kernel.c:844 #7 0x0000000000405984 in ?? () #8 0x00000000004052df in ?? () #9 0x0000000800637008 in ?? () #10 0x0000000000000000 in ?? () On Sun, Sep 26, 2021 at 12:53 AM Rich wrote: > I don't have a testpool handy to confirm it, but I would expect you to > be able to do something like > zdb -ddddd [pool]/[objsetid in hex] [objectid in hex] > e.g. > zdb -ddddd vr1/0x57b2 0x73ab46 > > Or failing that, drop the object id (and then probably some of the -d, > that gets real verbose). > > - Rich > > On Sun, Sep 26, 2021 at 12:27 AM Zaphod Beeblebrox > wrote: > > > > How do I find which snapshot it's in? > > > > On Sat, Sep 25, 2021 at 6:01 PM Miroslav Lachman <000.fbsd@quip.cz> > wrote: > > > > > > > > > > > I have seen this in the past. It was corruption on some deleted file > > > preserved on snapshot. Once I deleted snapshots this error disappeared. > > > > > > [...] > > > > > > Miroslav Lachman > > > > --000000000000206d7f05ccecb422-- From nobody Sun Sep 26 21:48:09 2021 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 9699817DC858 for ; Sun, 26 Sep 2021 21:48:21 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HHfXP3R8Kz579B for ; Sun, 26 Sep 2021 21:48:21 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: by mail-ua1-x92c.google.com with SMTP id c33so10829230uae.9 for ; Sun, 26 Sep 2021 14:48:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+dWlDpJtghr+FQEjwWFsV9GpQCuzgWpEUgnNEsEaM7M=; b=FpTf+RLh6jwggmu4XSxb50AmE9AedoTdIu6qtVhOkGiTWEeulLu87ndZszfCG9Ozgb F668X8LsbyghJ2rz+v+4PbC6IvAY1GS/DM5t67TLvRdb3qsuE2eMMCe2FmiiNFQdKHOd tueQtMAlua1tHouJ6Lb09y/FJKMlbz/Yx0WmTpIYNpzjQZFWx/Z1nNIDDiVhmRNhwETA pUgY4qaSlIezt5bORWMg4tam/IA8tHh//RmcgeC4xM1i+haiPiy/xlh9VNnIO9O9QcDv OnTa7L5ECt893NGfMEjHoo9h0kdoGjXl8ob5JRcyzirk+plW0vubvIKd9WI9sOjJGEog VtBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+dWlDpJtghr+FQEjwWFsV9GpQCuzgWpEUgnNEsEaM7M=; b=bK+F2qS4WJGAVJvZP8wYFVsrpd2FQ/YPrG9TsBX3j2JTlKmkBSIEF4LMIXWVlDZgSo q9l35BD8QUAZdZ4qlnzcD7IlQFODyeGEdC54T3xtU6JAWl/QWQbh95+94nUkXiXNrl9J 1qe9KnyQluP/bbxsxhl6OlgdFehWREJXCNxE7zRZ1K7f5pssEY56RE/1m0lYbmxxBHKx pEw4GBNQVA7tHGivI9PbPOA/otkZlDvuP3LwxUDUgBqerkaMvMACw6JQQD+uISJNA6po UvHK2KUMKyZwTPaW20nh0jW6UVbU2az+HrFI7rjfSLkDiJ0E2t74QjyKMXIche5yoU1a P7cg== X-Gm-Message-State: AOAM530sDzxpfwgxRSdA96N/+mXa22ud2pVbnWQVFcAdkakP918+jaB9 bIUNNlxbSONpup0DmSvaHQ0aUCzcRoa8DvnnMYHWphNVLFk= X-Google-Smtp-Source: ABdhPJylKv3+vd81b9L2TasOxOEhKl1MKbL32cfd/PRZSDlaW/ZDQEeoaJkNJqi+w9TS1JuXF3NiOfdMsSJOwi+D8Ow= X-Received: by 2002:a9f:3412:: with SMTP id q18mr16710309uab.23.1632692900907; Sun, 26 Sep 2021 14:48:20 -0700 (PDT) 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 References: <33176b34-6929-57fb-2e3f-bd3e9396fe01@quip.cz> In-Reply-To: From: Rich Date: Sun, 26 Sep 2021 17:48:09 -0400 Message-ID: Subject: Re: ZFS errors with two HEX numbers. To: Zaphod Beeblebrox Cc: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-fs Content-Type: multipart/alternative; boundary="00000000000062ce9505ccecf042" X-Rspamd-Queue-Id: 4HHfXP3R8Kz579B X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --00000000000062ce9505ccecf042 Content-Type: text/plain; charset="UTF-8" Curious - on my 13-STABLE box that I haven't bothered updating in a minute... [root@fbsd13bed ~]# uname -a;zpool version; FreeBSD fbsd13bed 13.0-STABLE FreeBSD 13.0-STABLE #1 stable/13-n247014-e8e5d75e6a96: Mon Aug 30 16:24:56 EDT 2021 root@fbsd13bed:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 zfs-2.1.99-426_g70bf547a9 zfs-kmod-2.1.99-426_g70bf547a9 [root@fbsd13bed ~]# zdb -dd zroot/0x97 | head Dataset zroot/usr/src [ZPL], ID 151, cr_txg 17, 2.92G, 94231 objects ZIL header: claim_txg 0, claim_blk_seq 0, claim_lr_seq 0 replay_seq 0, flags 0x0 Object lvl iblk dblk dsize dnsize lsize %full type 0 6 128K 16K 29.3M 512 112M 41.01 DMU dnode -1 1 128K 512 0 512 512 100.00 ZFS user/group/project used -2 1 128K 512 0 512 512 100.00 ZFS user/group/project used -3 1 128K 512 0 512 512 100.00 ZFS user/group/project used [root@fbsd13bed ~]# zdb -dd zroot/0x98 | head failed to hold objset 152: Invalid argument zdb: can't open 'zroot/0x98': Invalid argument So what version of FBSD and ZFS are you running on? - Rich On Sun, Sep 26, 2021 at 5:31 PM Zaphod Beeblebrox wrote: > Entertaining. That (even with only two --> zdb -dd vr1/0x57b2) gives ... > core dump. SIGSEGV in strlen. Dereferencing a NULL. > > (gdb) bt > #0 strlen (str=0xd ) at > /usr/src/lib/libc/string/strlen.c:101 > #1 0x0000000800f6ea60 in __vfprintf (fp=, > locale=0x80102eed8 <__xlocale_global_locale>, > fmt0=, ap=) at > /usr/src/lib/libc/stdio/vfprintf.c:854 > #2 0x0000000800f6b8df in snprintf (str=0x801644400 "", n=, > fmt=0x8009ad9b9 "%s/%s") > at /usr/src/lib/libc/stdio/snprintf.c:74 > #3 0x0000000800a58b76 in zfs_file_open (path=path@entry=0x801644000 > "/etc/zfs/zpool.cache", flags=, > flags@entry=0, mode=, mode@entry=0, fpp=fpp@entry > =0x7fffffe58788) > at /usr/src/sys/contrib/openzfs/lib/libzpool/kernel.c:1075 > #4 0x0000000800b3e622 in spa_config_load () at > /usr/src/sys/contrib/openzfs/module/zfs/spa_config.c:101 > #5 0x0000000800b47b39 in spa_init (mode=mode@entry=SPA_MODE_READ) > at /usr/src/sys/contrib/openzfs/module/zfs/spa_misc.c:2393 > #6 0x0000000800a586ae in kernel_init (mode=1) at > /usr/src/sys/contrib/openzfs/lib/libzpool/kernel.c:844 > #7 0x0000000000405984 in ?? () > #8 0x00000000004052df in ?? () > #9 0x0000000800637008 in ?? () > #10 0x0000000000000000 in ?? () > > On Sun, Sep 26, 2021 at 12:53 AM Rich wrote: > >> I don't have a testpool handy to confirm it, but I would expect you to >> be able to do something like >> zdb -ddddd [pool]/[objsetid in hex] [objectid in hex] >> e.g. >> zdb -ddddd vr1/0x57b2 0x73ab46 >> >> Or failing that, drop the object id (and then probably some of the -d, >> that gets real verbose). >> >> - Rich >> >> On Sun, Sep 26, 2021 at 12:27 AM Zaphod Beeblebrox >> wrote: >> > >> > How do I find which snapshot it's in? >> > >> > On Sat, Sep 25, 2021 at 6:01 PM Miroslav Lachman <000.fbsd@quip.cz> >> wrote: >> > >> > > >> > > >> > > I have seen this in the past. It was corruption on some deleted file >> > > preserved on snapshot. Once I deleted snapshots this error >> disappeared. >> > > >> > > [...] >> > > >> > > Miroslav Lachman >> > > >> > --00000000000062ce9505ccecf042--