From: David Sardari <d@duxsco.de>
To: Andrei Borzenkov <arvidjaar@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs failing to make incremental backups
Date: Sat, 30 Oct 2021 21:17:08 +0200 [thread overview]
Message-ID: <c3212facb413379cfc216d481f97939132051093.camel@duxsco.de> (raw)
In-Reply-To: <a83899eaf5e747ec1b007b890d8550958d8760bb.camel@duxsco.de>
That seems to have solved the issue. Ticket closed :) Thanks a lot
--
My GnuPG public key:
gpg --auto-key-locate clear,dane --locate-external-key <MyMailAddress>
On Sat, 2021-10-30 at 17:36 +0200, David Sardari wrote:
> 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.
prev parent reply other threads:[~2021-10-30 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 12:49 Btrfs failing to make incremental backups 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
2021-10-30 19:17 ` David Sardari [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=c3212facb413379cfc216d481f97939132051093.camel@duxsco.de \
--to=d@duxsco.de \
--cc=arvidjaar@gmail.com \
--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).