From: "Stéphane Lesimple" <stephane_btrfs@lesimple.fr>
To: linux-btrfs@vger.kernel.org
Cc: "Stéphane Lesimple" <stephane_btrfs@lesimple.fr>
Subject: [PATCH 0/2] btrfs-progs: check: enhanced progress indicator
Date: Wed, 4 Jul 2018 21:20:12 +0200 [thread overview]
Message-ID: <1530732014-5449-1-git-send-email-stephane_btrfs@lesimple.fr> (raw)
This patch replaces the current ".oOo."-style progress indicator of
btrfs check (-p), by a more helpful live indication of the check progress.
I've been using it on a custom btrfs-progs version since 2015.
Here's how the output looks like on a 22 Tb 5-disk RAID1 FS:
# btrfs check -p /dev/mapper/luks-ST10000VN0004-XXXXXXXX
Opening filesystem to check...
Checking filesystem on /dev/mapper/luks-ST10000VN0004-XXXXXXXX
UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
[1/7] checking extents (0:20:21 elapsed, 950958 items checked)
[2/7] checking root items (0:01:29 elapsed, 15121 items checked)
[3/7] checking free space cache (0:00:11 elapsed, 4928 items checked)
[4/7] checking fs roots (0:51:31 elapsed, 600892 items checked)
[5/7] checking csums (0:14:35 elapsed, 754522 items checked)
[6/7] checking root refs (0:00:00 elapsed, 232 items checked)
[7/7] checking quota groups skipped (not enabled on this FS)
found 5286458060800 bytes used, no error found
The code is also viewable at https://github.com/kdave/btrfs-progs/pull/69
Stéphane Lesimple (2):
btrfs-progs: fix nanosecs in task_period_start
btrfs-progs: check: enhanced progress indicator
check/main.c | 176 ++++++++++++++++++++++++++++++++++------------------
check/mode-common.h | 20 ++++++
check/mode-lowmem.c | 1 +
convert/main.c | 2 +-
qgroup-verify.c | 7 +++
qgroup-verify.h | 2 +
task-utils.c | 10 ++-
task-utils.h | 3 +-
8 files changed, 155 insertions(+), 66 deletions(-)
--
2.7.4
next reply other threads:[~2018-07-04 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 19:20 Stéphane Lesimple [this message]
2018-07-04 19:20 ` [PATCH 1/2] btrfs-progs: fix nanosecs in task_period_start Stéphane Lesimple
2018-07-05 7:53 ` Su Yue
2018-07-04 19:20 ` [PATCH 2/2] btrfs-progs: check: enhanced progress indicator Stéphane Lesimple
2018-07-11 5:18 ` Qu Wenruo
2018-07-16 16:55 ` David Sterba
2018-07-17 1:23 ` Misono Tomohiro
2018-07-17 12:09 ` David Sterba
2018-07-16 16:48 ` [PATCH 0/2] " 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=1530732014-5449-1-git-send-email-stephane_btrfs@lesimple.fr \
--to=stephane_btrfs@lesimple.fr \
--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;
as well as URLs for NNTP newsgroup(s).