From: Graham Cobb <g.btrfs@cobb.uk.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Used disk size of a received subvolume?
Date: Sat, 18 May 2019 00:15:25 +0100 [thread overview]
Message-ID: <04d3b1ac-2a3e-f79e-59be-513c00eb8bb1@cobb.uk.net> (raw)
In-Reply-To: <24f44d54-a560-0b6e-5fe0-026626d1d2c5@steev.me.uk>
On 17/05/2019 17:39, Steven Davies wrote:
> On 17/05/2019 16:28, Graham Cobb wrote:
>
>> That is why I created my "extents-list" stuff. This is a horrible hack
>> (one day I will rewrite it using the python library) which lets me
>> answer questions like: "how much space am I wasting by keeping
>> historical snapshots", "how much data is being shared between two
>> subvolumes", "how much of the data in my latest snapshot is unique to
>> that snapshot" and "how much space would I actually free up if I removed
>> (just) these particular directories". None of which can be answered from
>> the existing btrfs command line tools (unless I have missed something).
>
> I have my own horrible hack to do something like this; if you ever get
> around to implementing it in Python could you share the code?
>
Sure. The current hack (using shell and command line tools) is at
https://github.com/GrahamCobb/extents-lists. If the python version ever
materialises I expect it will end up there as well.
next prev parent reply other threads:[~2019-05-17 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 14:54 Used disk size of a received subvolume? Axel Burri
2019-05-16 17:09 ` Remi Gauvin
2019-05-17 14:14 ` Axel Burri
2019-05-17 16:22 ` Remi Gauvin
2019-05-16 17:12 ` Hugo Mills
2019-05-17 13:57 ` Axel Burri
2019-05-17 15:28 ` Graham Cobb
2019-05-17 16:39 ` Steven Davies
2019-05-17 23:15 ` Graham Cobb [this message]
2019-05-23 16:06 ` Axel Burri
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=04d3b1ac-2a3e-f79e-59be-513c00eb8bb1@cobb.uk.net \
--to=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 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).