From: Goffredo Baroncelli <kreijack@libero.it>
To: waxhead@dirtcellar.net
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS list of grievances
Date: Thu, 3 Oct 2024 19:10:26 +0200 [thread overview]
Message-ID: <401088cf-85c0-4ea2-bc4c-b34138eae5e9@libero.it> (raw)
In-Reply-To: <4f672a82-28d8-490e-bdce-e794748d41fd@libero.it>
On 30/09/2024 23.43, Goffredo Baroncelli wrote:
> On 27/09/2024 13.20, waxhead wrote:
[...]
>>
>> 6. DEVICE STATS:
>> ================
>> Again device ID's are not used, but also why is this info not listed in a table? Showing this in a table would make 5x lines become 1x line which would be far more readable.
This was an already solved problem
$ sudo ./btrfs dev stat -T /mnt/btrfs-raid1/
Id Path Write errors Read errors Flush errors Corruption errors Generation errors
-- --------- ------------ ----------- ------------ ----------------- -----------------
1 /dev/sda2 0 0 0 763 0
2 /dev/sdb2 0 0 0 3504 0
3 /dev/sdd2 13 0 0 6218 0
--
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:[~2024-10-03 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 11:20 BTRFS list of grievances waxhead
2024-09-27 16:27 ` Roman Mamedov
2024-09-27 18:05 ` Remi Gauvin
2024-09-27 19:01 ` Colin S
2024-10-02 19:31 ` Chris Murphy
2024-10-02 23:18 ` Colin S
2024-09-28 10:15 ` Paul Jones
2024-09-28 17:51 ` Roman Mamedov
2024-09-27 17:44 ` Mark Harmstone
2024-09-30 21:43 ` Goffredo Baroncelli
2024-10-03 17:10 ` Goffredo Baroncelli [this message]
2024-10-03 17:26 ` Remi Gauvin
2024-10-03 18:24 ` Goffredo Baroncelli
2024-10-03 18:32 ` Remi Gauvin
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=401088cf-85c0-4ea2-bc4c-b34138eae5e9@libero.it \
--to=kreijack@libero.it \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=waxhead@dirtcellar.net \
/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