From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, william.brown@suse.com
Subject: Re: [PATCH 0/3] btrfs-progs: subvolume-list: add qgroup sizes output
Date: Wed, 6 Dec 2023 22:30:19 +0100 [thread overview]
Message-ID: <20231206213019.GT2751@twin.jikos.cz> (raw)
In-Reply-To: <cover.1701160698.git.wqu@suse.com>
On Tue, Nov 28, 2023 at 07:14:50PM +1030, Qu Wenruo wrote:
> ZFS' management tool is way better received than btrfs-progs, one of the
> user-friendly point is the default `zpool list`, which includes the size
> of each subvolume.
The output of 'subvol list' needs a rework, it's from the early times.
Unfortunatelly lots of tools depend on the output format so it's not
easy to change it.
There's a WIP https://github.com/kdave/btrfs-progs/issues/515 with
outlined problems and proposed solutions.
To work around the compatibility problem and to bring a nice UI I've
proposed to create a completely new command and shamelessly copying what
https://github.com/speed47/btrfs-list does. Instead of adding new
features to current 'list' incrementally.
Adding the qgroups column is probably ok, I'll take another look.
next prev parent reply other threads:[~2023-12-06 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 8:44 [PATCH 0/3] btrfs-progs: subvolume-list: add qgroup sizes output Qu Wenruo
2023-11-28 8:44 ` [PATCH 1/3] btrfs-progs: separate root attributes into a dedicated structure from root_info Qu Wenruo
2023-11-28 8:44 ` [PATCH 2/3] btrfs-progs: use root_attr structure to pass various attributes Qu Wenruo
2023-11-28 8:44 ` [PATCH 3/3] btrfs-progs: subvolume-list: output qgroup sizes for subvolumes Qu Wenruo
2023-12-06 21:30 ` David Sterba [this message]
2024-03-21 3:21 ` [PATCH 0/3] btrfs-progs: subvolume-list: add qgroup sizes output Qu Wenruo
2024-03-25 22:44 ` David Sterba
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=20231206213019.GT2751@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=william.brown@suse.com \
--cc=wqu@suse.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
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