public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Graham Cobb <g.btrfs@cobb.me.uk>
To: Alex Powell <alexj.powellalt@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: space still allocated post deletion
Date: Wed, 20 Apr 2022 09:27:23 +0100	[thread overview]
Message-ID: <cac308f5-5d4a-00e2-94de-40e4f144a144@cobb.uk.net> (raw)
In-Reply-To: <CAKGv6CovkUjb92MAaM-irNcJvJk2P_2QNpybzCSsSs2RMgfz4A@mail.gmail.com>

On 20/04/2022 08: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.

I don't use either veeam or Ubuntu but I note that btrbk (which I use)
has a similar concept of storing some snapshots on the disk itself and
only moving a subset of them to the backup disk. I use this to keep
hourly snapshots on the source disk itself and move one of them to the
backup disk per day. The hourly snapshots have proved occasionally
useful when I manage to accidentally delete a chunk of a document I am
working on and then save the file - DOH!

Of course, it isn't so useful if you never knew it existed :-)


  reply	other threads:[~2022-04-20  8:34 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 [this message]
2022-04-23  6:04     ` Andrei Borzenkov

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=cac308f5-5d4a-00e2-94de-40e4f144a144@cobb.uk.net \
    --to=g.btrfs@cobb.me.uk \
    --cc=alexj.powellalt@googlemail.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