archive mirror
 help / color / mirror / Atom feed
From: David Sardari <>
To: Andrei Borzenkov <>,
Subject: Re: Btrfs failing to make incremental backups
Date: Sat, 30 Oct 2021 17:36:05 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Thanks for the info, I keep that in mind. For me the content of
"${SRC}" and "${DST}" is of no relevance. They just should point out
what we are dealing with: source or destination side

On Sat, 2021-10-30 at 18:02 +0300, Andrei Borzenkov wrote:
> Please understand that mailing list is not a web forum where you can
> scroll up and see previous posts. You previous mail may not be
> available
> when reading so context is lost.
> > bash-5.1# btrfs subvolume show "${DST}/@2021-10-30-095620_files"

OK, I interpreted your message wrongly. You were asking for "involved"
snapshots and I assumed those involved in the "buggy" "btrfs
send/receive" command.

I decided to start with new subvolumes (btrfs subvolume create
@files_new; cp -av --reflink @files/ @files_new/; btrfs subvolume
delete @files; mv @files_new @files). Thereafter, I test again.

> I asked you to show this information for all snapshots that you have
> listed on github for a reason. You so far only provided two source
> snapshots and one received snapshot.
> Anyway, your two source snapshots show the same received UUID which
> confirms what I suspected. It means that every snapshot on
> destination
> will have the same received UUID as well and "btrfs receive" will use
> the wrong snapshot as base to apply change stream.
> The same problem was discussed just recently and pops up with
> regrettable frequency.

  reply	other threads:[~2021-10-30 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 12:49 David Sardari
2021-10-30 13:38 ` Andrei Borzenkov
2021-10-30 14:14   ` David Sardari
2021-10-30 14:20     ` David Sardari
2021-10-30 15:02       ` Andrei Borzenkov
2021-10-30 15:36         ` David Sardari [this message]
2021-10-30 19:17           ` David Sardari

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Btrfs failing to make incremental backups' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).