All of lore.kernel.org
 help / color / mirror / Atom feed
* Is it possible to construct snapshots manually?
@ 2018-10-19  9:41 Cerem Cem ASLAN
  2018-10-19 17:59 ` Andrei Borzenkov
  0 siblings, 1 reply; 2+ messages in thread
From: Cerem Cem ASLAN @ 2018-10-19  9:41 UTC (permalink / raw)
  To: Btrfs BTRFS

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)

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Is it possible to construct snapshots manually?
  2018-10-19  9:41 Is it possible to construct snapshots manually? Cerem Cem ASLAN
@ 2018-10-19 17:59 ` Andrei Borzenkov
  0 siblings, 0 replies; 2+ messages in thread
From: Andrei Borzenkov @ 2018-10-19 17:59 UTC (permalink / raw)
  To: Cerem Cem ASLAN, Btrfs BTRFS

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-10-19 17:59 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-19  9:41 Is it possible to construct snapshots manually? Cerem Cem ASLAN
2018-10-19 17:59 ` Andrei Borzenkov

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.