From: Sidong Yang <realwakka@gmail.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: device: print num_stripes in usage command
Date: Tue, 8 Jun 2021 14:46:24 +0000 [thread overview]
Message-ID: <20210608144624.GA818085@realwakka> (raw)
In-Reply-To: <20210607192048.GM31483@twin.jikos.cz>
On Mon, Jun 07, 2021 at 09:20:49PM +0200, David Sterba wrote:
> On Sun, May 30, 2021 at 12:56:36PM +0000, Sidong Yang wrote:
> > This patch appends num_stripes for each chunks in device usage commands.
> > It helps to see profiles easily. The output is like below.
> >
> > /dev/vdb, ID: 1
> > Device size: 1.00GiB
> > Device slack: 0.00B
> > Data,single[1]: 120.00MiB
> > Metadata,DUP[2]: 102.38MiB
> > System,DUP[2]: 16.00MiB
> > Unallocated: 785.62MiB
>
Hi David. Thanks for review!
> This is example of single and dup, but the whole point was to print that
> for the striped profiles, like is shown in the issue
> https://github.com/kdave/btrfs-progs/issues/372 , so it needs to be
> conditional.
Okay, striped profiles need to be printed. I read some page from
wikipedia about raid. and I got that RAID 0,5,6,10 supports striping.
Those need to be printed and no printing for RAID 1, single, dup.
>
> As the mirrored profiles have a fixed number of copies, there's no doubt
> on how many devices are printed, same for single and dup.
>
> I'm more inclined to use the "/" as separator: 'RAID6/3' it's more like
> "raid6 on three devices", the "[]" looks like indexing. "," is used as
> separator of the type so it won't be as simple to parse that.
I agree. I'll use "/" for next version.
prev parent reply other threads:[~2021-06-08 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 12:56 [PATCH] btrfs-progs: device: print num_stripes in usage command Sidong Yang
2021-06-07 19:20 ` David Sterba
2021-06-08 14:46 ` Sidong Yang [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=20210608144624.GA818085@realwakka \
--to=realwakka@gmail.com \
--cc=dsterba@suse.cz \
--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