From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A29AAC432BE for ; Wed, 1 Sep 2021 18:29:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7E71961090 for ; Wed, 1 Sep 2021 18:29:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233094AbhIASaE (ORCPT ); Wed, 1 Sep 2021 14:30:04 -0400 Received: from mail-lf1-f42.google.com ([209.85.167.42]:41857 "EHLO mail-lf1-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229510AbhIASaE (ORCPT ); Wed, 1 Sep 2021 14:30:04 -0400 Received: by mail-lf1-f42.google.com with SMTP id y34so877859lfa.8 for ; Wed, 01 Sep 2021 11:29:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=x0mMqPiz2pYzsaAAsc4FAO8doltfuP30eZzeDehrrlk=; b=MxRgMBU9e89TwV0kBecJY+MBcW88gQvn58Hj2fTK0GFj6LP4GGofFW9ku+Cb3tYPwo JT4PKTEYVA4baL5vdCkuF+XT0ZQdDqmEiq+9NNE/IooOiLYMP/Wd6rPyF2Ajaqfy9WWH oDC77+NfYY+h0xwZqF/mPTivEMg7Cfxoz7Yr+dz/O4m4TNDYRQuRCvm3w+HH2cV6Xt+a /uPC0xeiTdHASgf05A3IFTrKNJlMti/kb6zlJz8FdwqGIze13Itd/9IdHbW+dd9BO6QA pz8gtItZ3B6kCsHrsnwX2cQAsnNW+FJpzOpadRmz9RCtWOFwCFezi4a0mbu5SuvLPXv2 cSbA== X-Gm-Message-State: AOAM530OvS8SYkDI9rNQMbtIL5GW+iqQ+bn4kJIhPyqTmsahmVL5saUc y8drwTFj0JKu2iffIpxG3iXxu1jZ0XLEkE9QGXquotd7 X-Google-Smtp-Source: ABdhPJySg7rbaai/9BEYeYlcIXAl0aNm2vF346TP7FtD6nYTiXdeubyEvg1QPjc8LkwWqcSExX9ePnjW4zrcUAAQmcU= X-Received: by 2002:a05:6512:21c3:: with SMTP id d3mr565517lft.226.1630520945922; Wed, 01 Sep 2021 11:29:05 -0700 (PDT) MIME-Version: 1.0 References: <06e92a0b-e71b-eb21-edb5-9d2a5513b718@gmail.com> In-Reply-To: <06e92a0b-e71b-eb21-edb5-9d2a5513b718@gmail.com> From: Darrell Enns Date: Wed, 1 Sep 2021 11:28:54 -0700 Message-ID: Subject: Re: Backup failing with "failed to clone extents" error To: Andrei Borzenkov Cc: fdmanana@gmail.com, linux-btrfs Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org > There was proposed patch to clear received_uuid on > clearing read-only subvolume property, but it has never been applied. Exactly this was about to be my next suggestion. I don't know all the details, but it sounds like that makes sense if matching received_uuid's is considered to mean the data is identical. > What will surely work is cloning you root subvolume and switching to > clone. If course you will need to restart all replication streams > beginning with full send of new root. But as it looks like you will need > to restart it anyway. I will give this a try. Thank you very much for all your help diagnosing this!