From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f52.google.com ([209.85.215.52]:32862 "EHLO mail-lf0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752152AbdHAUdJ (ORCPT ); Tue, 1 Aug 2017 16:33:09 -0400 Received: by mail-lf0-f52.google.com with SMTP id d17so11869561lfe.0 for ; Tue, 01 Aug 2017 13:33:08 -0700 (PDT) Subject: Re: Btrfs incremental send | receive fails with Error: File not found To: linux-btrfs@vger.kernel.org Cc: Cerem Cem ASLAN References: <59b8cc62-66fa-6665-45f9-89c6fe91ceaa@gmail.com> <403536b6-2404-8589-3536-3a91ae769cd6@freirad.at> <8dc4e2a0-3e83-9e60-c565-c86a924ceaf5@gmail.com> From: A L Message-ID: Date: Tue, 1 Aug 2017 22:33:06 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 8/1/2017 10:24 PM, Cerem Cem ASLAN wrote: > What is that mean? Can't we replicate the same snapshot with `btrfs > send | btrfs receive` multiple times, because it will have a "Received > UUID" at the first `btrfs receive You will need to make a new read-write snapshot of the received volume to fix it. Any snapshots created from the received subvolume can't be used for send-receive again, afaik. # btrfs subvolume snapshot subvolume.received subvolume