From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Cerem Cem ASLAN <ceremcem@ceremcem.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Is it possible to construct snapshots manually?
Date: Fri, 19 Oct 2018 20:59:37 +0300 [thread overview]
Message-ID: <225de89a-8a7f-a8aa-4250-15d7e7dd0350@gmail.com> (raw)
In-Reply-To: <CAN4oSBcEi7Lxt7D3KrZ=jtU3g=DtN7mwUpPQ8zLrvwRjtKRCXw@mail.gmail.com>
19.10.2018 12:41, Cerem Cem ASLAN пишет:
> By saying "manually", I mean copying files into a subvolume on a
> different mountpoint manually, then mark the target as if it is
> created by "btrfs send | btrfs receive".
>
> Rationale:
>
> When we delete all common snapshots from source, we have to send whole
> snapshot for next time. This ability will prevent sending everything
> from scratch unless it's necessary.
> (https://unix.stackexchange.com/q/462451/65781)
>
You can set received UUID as this link suggests. How it can be done was
posted on this list more than once.
> Possible workaround:
>
> I've got an idea at the moment: What I want can be achieved by
> dropping usage of "btrfs send | btrfs receive" completely and using
> only rsync for transfers. After transfer, a snapshot can be created
> independently on the remote site. Only problem will be handling the
> renamed/relocated files, but `rsync --fuzzy` option might help here:
> https://serverfault.com/a/489293/261445
>
> Anyway, it would be good to have a built in support for this.
>
No. It is already possible to shoot oneself in the foot; there is no
need to make it easily done by accident or misunderstanding.
prev parent reply other threads:[~2018-10-19 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 9:41 Is it possible to construct snapshots manually? Cerem Cem ASLAN
2018-10-19 17:59 ` Andrei Borzenkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=225de89a-8a7f-a8aa-4250-15d7e7dd0350@gmail.com \
--to=arvidjaar@gmail.com \
--cc=ceremcem@ceremcem.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).