From: Goffredo Baroncelli <kreijack@libero.it>
To: Steven Davies <btrfs-list@steev.me.uk>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
John Petrini <john.d.petrini@gmail.com>
Cc: John Petrini <me@johnpetrini.com>, linux-btrfs@vger.kernel.org
Subject: Re: Filesystem Went Read Only During Raid-10 to Raid-6 Data Conversion
Date: Mon, 20 Jul 2020 19:57:49 +0200 [thread overview]
Message-ID: <507b649c-ac60-0b5c-222f-192943c50f16@libero.it> (raw)
In-Reply-To: <de9a3d52-0147-255c-4c39-09bf734e1435@steev.me.uk>
On 7/18/20 12:36 PM, Steven Davies wrote:
> On 17/07/2020 06:57, Zygo Blaxell wrote:
>> On Thu, Jul 16, 2020 at 09:11:17PM -0400, John Petrini wrote:
>
> --snip--
>
>>> /dev/sdf, ID: 12
>>> Device size: 9.10TiB
>>> Device slack: 0.00B
>>> Data,RAID10: 784.31GiB
>>> Data,RAID10: 4.01TiB
>>> Data,RAID10: 3.34TiB
>>> Data,RAID6: 458.56GiB
>>> Data,RAID6: 144.07GiB
>>> Data,RAID6: 293.03GiB
>>> Metadata,RAID10: 4.47GiB
>>> Metadata,RAID10: 352.00MiB
>>> Metadata,RAID10: 6.00GiB
>>> Metadata,RAID1C3: 5.00GiB
>>> System,RAID1C3: 32.00MiB
>>> Unallocated: 85.79GiB
>>
[...]
>
> RFE: improve 'dev usage' to show these details.
>
> As a user I'd look at this output and assume a bug in btrfs-tools because of the repeated conflicting information.
What would be the expected output ?
What about the example below ?
/dev/sdf, ID: 12
Device size: 9.10TiB
Device slack: 0.00B
Data,RAID10: 784.31GiB
Data,RAID10: 4.01TiB
Data,RAID10: 3.34TiB
Data,RAID6[3]: 458.56GiB
Data,RAID6[5]: 144.07GiB
Data,RAID6[7]: 293.03GiB
Metadata,RAID10: 4.47GiB
Metadata,RAID10: 352.00MiB
Metadata,RAID10: 6.00GiB
Metadata,RAID1C3: 5.00GiB
System,RAID1C3: 32.00MiB
Unallocated: 85.79GiB
Another possibility (but the output will change drastically, I am thinking to another command)
Filesystem '/'
Data,RAID1: 123.45GiB
/dev/sda 12.34GiB
/dev/sdb 12.34GiB
Data,RAID1: 123.45GiB
/dev/sde 12.34GiB
/dev/sdf 12.34GiB
Data,RAID6: 123.45GiB
/dev/sda 12.34GiB
/dev/sdb 12.34GiB
/dev/sdc 12.34GiB
Data,RAID6: 123.45GiB
/dev/sdb 12.34GiB
/dev/sdc 12.34GiB
/dev/sdd 12.34GiB
/dev/sde 12.34GiB
/dev/sdf 12.34GiB
The number are the chunks sizes (invented). Note: for RAID5/RAID6 a chunk will uses near all disks; however for (e.g.) RAID1 there is the possibility that CHUNKS use different disks pairs (see the two RAID1 instances).
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2020-07-20 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 16:13 Filesystem Went Read Only During Raid-10 to Raid-6 Data Conversion John Petrini
2020-07-15 1:18 ` Zygo Blaxell
[not found] ` <CADvYWxcq+-Fg0W9dmc-shwszF-7sX+GDVig0GncpvwKUDPfT7g@mail.gmail.com>
[not found] ` <20200716042739.GB8346@hungrycats.org>
2020-07-16 13:37 ` John Petrini
[not found] ` <CAJix6J9kmQjfFJJ1GwWXsX7WW6QKxPqpKx86g7hgA4PfbH5Rpg@mail.gmail.com>
2020-07-16 22:57 ` Zygo Blaxell
2020-07-17 1:11 ` John Petrini
2020-07-17 5:57 ` Zygo Blaxell
2020-07-17 22:54 ` John Petrini
2020-07-18 10:36 ` Steven Davies
2020-07-20 17:57 ` Goffredo Baroncelli [this message]
2020-07-21 10:15 ` Steven Davies
2020-07-21 20:48 ` Goffredo Baroncelli
2020-07-23 8:57 ` Steven Davies
2020-07-23 19:29 ` Zygo Blaxell
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=507b649c-ac60-0b5c-222f-192943c50f16@libero.it \
--to=kreijack@libero.it \
--cc=btrfs-list@steev.me.uk \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=john.d.petrini@gmail.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=me@johnpetrini.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.