From owner-freebsd-bugs@freebsd.org Mon Dec 28 21:06:33 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 409F74C14CB for ; Mon, 28 Dec 2020 21:06:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4D4VTj1BhTz4kFn for ; Mon, 28 Dec 2020 21:06:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 28A6D4C14CA; Mon, 28 Dec 2020 21:06:33 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 286B14C190E for ; Mon, 28 Dec 2020 21:06:33 +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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D4VTj0WH6z4kCj for ; Mon, 28 Dec 2020 21:06:33 +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 EE60620288 for ; Mon, 28 Dec 2020 21:06:32 +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 0BSL6WbR028905 for ; Mon, 28 Dec 2020 21:06:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0BSL6Wmt028904 for bugs@FreeBSD.org; Mon, 28 Dec 2020 21:06:32 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 252240] "zfs send -R -I | zfs receive -F" not destroying snapshots that don't exist on the sending side Date: Mon, 28 Dec 2020 21:06:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lew@perftech.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Dec 2020 21:06:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252240 Bug ID: 252240 Summary: "zfs send -R -I | zfs receive -F" not destroying snapshots that don't exist on the sending side Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: lew@perftech.com This is similar to 169964, but that was due to lack of the -R option, so I'm submitting this as a new bug. This appears to be new to 12.2-RELEASE. If the receiving side is running 12= .1 or 12.0, everything works properly, but if the receiving side is running 12= .2, then snapshots that don't exist on the sending side are not destroyed on the receiving side. The version of the sending side doesn't appear to make any difference, the problem appears to be strictly on the receive side, and consistently fails = with 12.2 and withs with 12.1 or prior. In fact, on a given system, running freebsd-update to upgrade from 12.1 to 12.2 causes the problem to appear, a= nd reverting back to 12.1, the problem disappears. Sample commands: zfs create ds/test zfs snapshot ds/test@1 zfs snapshot ds/test@2 zfs snapshot ds/test@3 zfs snapshot ds/test@4 zfs snapshot ds/test@5 zfs send -R ds/test@5 | ssh desthost zfs receive -F ds/test desthost now has the filesystem and all snapshots. zfs snapshot ds/test@6 zfs send -R -I ds/test@5 ds/test@6 | ssh desthost zfs receive -F ds/test desthost now has the test@6 snapshot zfs destroy ds/test@2 zfs destroy ds/test@3 zfs send -R -I ds/test@5 ds/test@6 | ssh desthost zfs receive -F ds/test If desthost is running 12.2, then test@2 and test@3 remain. If desthost is running 12.1 or 12.0, then test@2 and test@3 are destroyed. And it doesn't matter whether the snapshot has previously synced or not, for example: zfs snapshot ds/test@7 zfs send -R -I ds/test@6 ds/test@7 | ssh desthost zfs receive -F ds/test still doesn't cause @2 and @3 to get destroyed. However, zfs send -R -I ds/test@1 ds/test@7 | ssh desthost zfs receive -F ds/test does cause @2 and @3 to get destroyed. But that's not an acceptable work-around, and this appears to be a regression from prior versions. --=20 You are receiving this mail because: You are the assignee for the bug.=