From: Graham Cobb <email@example.com> To: firstname.lastname@example.org Subject: Re: Used disk size of a received subvolume? Date: Sat, 18 May 2019 00:15:25 +0100 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> 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 index Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-16 14:54 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 publically 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
Linux-BTRFS Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \ firstname.lastname@example.org email@example.com public-inbox-index linux-btrfs Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs AGPL code for this site: git clone https://public-inbox.org/ public-inbox