From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Alex Powell <alexj.powellalt@googlemail.com>,
Graham Cobb <g.btrfs@cobb.me.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: space still allocated post deletion
Date: Sat, 23 Apr 2022 09:04:47 +0300 [thread overview]
Message-ID: <7a9e7e85-e7d6-cd68-83e7-76ebc6cffee5@gmail.com> (raw)
In-Reply-To: <CAKGv6CovkUjb92MAaM-irNcJvJk2P_2QNpybzCSsSs2RMgfz4A@mail.gmail.com>
On 20.04.2022 10:17, Alex Powell wrote:
> Thank you,
> The issue was veeam keeping snapshots in .veeam-snapshots above the
> root subvolume. I have no idea why this is the expected behaviour,
> because the backups are set to go to /mnt/data.
>
Snapshots are the source of backup data. Veeam always creates snapshot
to get stable state, either using own driver or (on btrfs) using btrfs
native snapshots. Then Veeam reads data from those snapshots and stores
in location where you have specified it. See Veeam Agent for Linux
documentation (I assume this is what you are using).
> I'm confident that if I wait 7 days, the backup retention period, this
> will fix itself. So this itself is not a bug in btrfs, it is more a
> misconfiguration by Ubuntu or Veeam.
>
I fail to see any misconfiguration. If you imply that btrfs snapshots
should be located on external disk - that is simply not possible.
prev parent reply other threads:[~2022-04-23 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:41 space still allocated post deletion Alex Powell
2022-04-19 11:21 ` Graham Cobb
2022-04-19 12:42 ` Hugo Mills
2022-04-20 7:17 ` Alex Powell
2022-04-20 8:27 ` Graham Cobb
2022-04-23 6:04 ` 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=7a9e7e85-e7d6-cd68-83e7-76ebc6cffee5@gmail.com \
--to=arvidjaar@gmail.com \
--cc=alexj.powellalt@googlemail.com \
--cc=g.btrfs@cobb.me.uk \
--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