From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: [PATCH v3 0/4] btrfs-progs: stat info for btrfs rescue chunk-recover
Date: Wed, 2 Sep 2015 20:22:28 +0800 [thread overview]
Message-ID: <cover.1441196519.git.zhaolei@cn.fujitsu.com> (raw)
chunk-recover need to use many many time in scan_devices(),
and no output in screen:
# btrfs rescue chunk-recover /dev/sda6
(no output here, but need long time)
To notice user that "the command is not hang", this patch add
dynamic updated stat information in above period:
# btrfs rescue chunk-recover /dev/sda6
Scanning: DONE in dev[0], 19998441472 in dev[1], DONE in dev[2]
(until)
Scanning: DONE in dev0, DONE in dev1, DONE in dev2
Check chunks successfully with no orphans
Recover the chunk tree successfully.
Changelog v2->v3:
Add [PATCH 2/4] to fix a potential invalid memory access of pthread.
Changelog v1->v2:
[PATCH 3/3] in v1 lost a little cleanup, added in v2.
Zhao Lei (4):
btrfs-progs: use for loop for scan_devices
btrfs-progs: Use long type to get thread's return value
btrfs-progs: stat info for btrfs rescue chunk-recover
btrfs-progs: Fix some spelling typo in chunk-recover.c
chunk-recover.c | 89 +++++++++++++++++++++++++++++++++++++++------------------
1 file changed, 61 insertions(+), 28 deletions(-)
--
1.8.5.1
next reply other threads:[~2015-09-02 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 12:22 Zhao Lei [this message]
2015-09-02 12:22 ` [PATCH v3 1/4] btrfs-progs: use for loop for scan_devices Zhao Lei
2015-09-02 12:22 ` [PATCH v3 2/4] btrfs-progs: Use long type to get thread's return value Zhao Lei
2015-09-02 12:22 ` [PATCH v3 3/4] btrfs-progs: stat info for btrfs rescue chunk-recover Zhao Lei
2015-09-02 12:22 ` [PATCH v3 4/4] btrfs-progs: Fix some spelling typo in chunk-recover.c Zhao Lei
2015-09-02 15:01 ` [PATCH v3 0/4] btrfs-progs: stat info for btrfs rescue chunk-recover 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=cover.1441196519.git.zhaolei@cn.fujitsu.com \
--to=zhaolei@cn.fujitsu.com \
--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