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=-10.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham 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 D6A9EC432BE for ; Wed, 1 Sep 2021 18:16:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B44AB61053 for ; Wed, 1 Sep 2021 18:16:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344260AbhIASRy (ORCPT ); Wed, 1 Sep 2021 14:17:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55174 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230063AbhIASRy (ORCPT ); Wed, 1 Sep 2021 14:17:54 -0400 Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1932BC061575 for ; Wed, 1 Sep 2021 11:16:57 -0700 (PDT) Received: by mail-lf1-x130.google.com with SMTP id m18so786801lfl.10 for ; Wed, 01 Sep 2021 11:16:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ZQG2Hfgl0JVGYXm3RIIniMiTnbhhQ7Pv0z/zZygImMk=; b=II3Q0ExxKRq0qpqrS7+v5w0pwNbuL0CNZYlI+Ddge3YawfrxUdgA9RAfGTA24j66Kg xZ9uEs1wzqrtyEdD/zN9yA10aZlkp45uebGaM9bgrvzcCQZU7ezDn4l/UD3Vsr9t/ZVk ctIYXBqUJKsodiJT0aAGE3Efiouy4PyF8BJSTJEo/DT/GnnTxWEK6jXa/YmgEfFbMuQf 97QrrTOd1FXEIp92iYLGNKPhuwzplIgYIKsVd/KOXhQSwyD89jrMdDtyHrEfghw1RTaX tmn3KPdulkR7NxYxS8npdsPQqU5Gwi22NCuxVrXZw8lEoJQrhrFcIioVJxCJc0ZX9gJ2 ojuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ZQG2Hfgl0JVGYXm3RIIniMiTnbhhQ7Pv0z/zZygImMk=; b=SqmKmfvr09d22uKfUcAoFoQv6H2CidjQ2Xj8itbRbE6JIE/SaHbyUftqO7dffArgDp StGawe7yju9o3iSTpxNmMPvT9gfSbN+mThCjgC9deIWor4SoNlXdIxnztILK9w5JJjb7 WyeiKAS2NjOW/9jPMIAl1fstGLS/YNBh2hqwShUHc6RtbO7Z1BLu1YbAT5LjS3ny3XKt /2BpxLzW1/JrogkpAz6oL9U+6DLsZEThRMnWA6FkBq3sgKBZjm4oF8TMKGUsttQEAPu2 B32Q+4/Ad4qeyqlnNZE9UgqyIEDBcEC2qZutCinJQ9YC6TqbYedGgTkUxamBHRwP1A45 t8cw== X-Gm-Message-State: AOAM532eX+mCqHv2H5FSq8nK6zXJxW+V21V/59jv49mof7kwuhMFSy3n K/TdDBTS+I4MXh2rAeVbY7edECu1EIc= X-Google-Smtp-Source: ABdhPJwJ/5dIHhNpy5GDtmgxYUDfRdvQbn3trjJX/jPjl0s+CmbTdlr5aopvlx6DgNrUKqpro468lg== X-Received: by 2002:a05:6512:2356:: with SMTP id p22mr533954lfu.524.1630520214957; Wed, 01 Sep 2021 11:16:54 -0700 (PDT) Received: from ?IPv6:2a00:1370:812d:8deb:5c9c:cef9:590c:9452? ([2a00:1370:812d:8deb:5c9c:cef9:590c:9452]) by smtp.gmail.com with ESMTPSA id b21sm22027lfi.104.2021.09.01.11.16.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 01 Sep 2021 11:16:54 -0700 (PDT) Subject: Re: Backup failing with "failed to clone extents" error To: Darrell Enns Cc: fdmanana@gmail.com, linux-btrfs References: From: Andrei Borzenkov Message-ID: <06e92a0b-e71b-eb21-edb5-9d2a5513b718@gmail.com> Date: Wed, 1 Sep 2021 21:16:52 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On 01.09.2021 20:52, Darrell Enns wrote: >> Most likely. Did you simply make received subvolume read-write? > > I believe so. Well, here you are. There was proposed patch to clear received_uuid on clearing read-only subvolume property, but it has never been applied. > Is there a different way of doing it that would have > avoided this situation? Yes. You should have created clone (read-write snapshot) of received sibvolume and use it as your root. Received_uuid is automatically cleared in writable snapshot. > On a new subvol, would the received uuid > normally be blank? Yes. > Any suggestions on how to "fix" mine? > I am not sure if it is even possible to clear received_uuid from user space - the only available IOCTL is for setting it (there are extra mandatory parameters and I do not know how to set them in this case). You may try ./examples/set_received_uuid.py from git://github.com/knorrie/python-btrfs while setting stransid and stime to zero. 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.