All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave T <davestechshop@gmail.com>
To: Graham Cobb <g.btrfs@cobb.uk.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: reorganizing my snapshots: how to move a readonly snapshot? (btrbk)
Date: Wed, 28 Jul 2021 11:29:07 -0400	[thread overview]
Message-ID: <CAGdWbB6qy+aSbCQB8pBxwZAO2M6hS3PSPONCMOOqqCEMfEaobg@mail.gmail.com> (raw)
In-Reply-To: <d6444a8d-f232-0744-1bcc-34457f0fcc3e@cobb.uk.net>

On Tue, Jul 27, 2021 at 1:34 PM Graham Cobb <g.btrfs@cobb.uk.net> wrote:
>
>
> On 27/07/2021 17:47, Dave T wrote:
> > I'm using btrbk to create regular snapshots. I see a way I can improve
> > the organization of my snapshots now that I have more experience with
> > this tool, but it requires moving existing snapshots to a different
> > directory.
> >
> > I would prefer to avoid re-creating the full initial snapshot in the
> > new location and I would prefer to avoid losing the existing
> > incremental snapshots. I also want to preserve the existing parent
> > relationships used by my snapshot tools (mainly btrbk).
> >
> > I'm thinking about using the solution mentioned here:
> > https://unix.stackexchange.com/a/149933
> >
> >> To set a snapshot to read-write, you do something like this:
> >> btrfs property set -ts /path/to/snapshot ro false
> >
> > My plan would be to change the ro property to false, move the
> > snapshots, reset the ro property to true, and change my btrbk.conf to
> > match the new path.
> >
> > What are the caveats in this plan?
>
> I believe that setting snapshots read-write and then back to ro is not
> recommended and is unsupported.

I have heard something vague about that before, which is why I asked
before doing it. It still seems unclear, but I'll avoid that approach
unless someone confirms it is OK.

> It may work but I am sure I have seen
> reports of problems with send/receive when snapshots have been made rw,
> changed and then set ro again.
>
> I recommend using the btrbk archive feature to move your existing
> snapshots and then start building on top of those. I think I did exactly
> this a long time ago when I was in a similar position of wanting to move
> my btrbk setup.

Thank you for the idea. The archive feature is the one btrbk feature I
have not explore yet. It looks simple to use. btrbk is a nice tool.

>
> Graham

  reply	other threads:[~2021-07-28 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 16:47 reorganizing my snapshots: how to move a readonly snapshot? (btrbk) Dave T
2021-07-27 17:33 ` Graham Cobb
2021-07-28 15:29   ` Dave T [this message]
2021-07-29  0:57   ` Dave T
2021-07-29 10:10     ` Graham Cobb

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=CAGdWbB6qy+aSbCQB8pBxwZAO2M6hS3PSPONCMOOqqCEMfEaobg@mail.gmail.com \
    --to=davestechshop@gmail.com \
    --cc=g.btrfs@cobb.uk.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 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.