From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] btrfs-progs: fix missing parity stripe for raid6 in chunk-recover
Date: Thu, 12 Jun 2014 16:11:24 +0800 [thread overview]
Message-ID: <1402560684.28107.2.camel@localhost.localdomain> (raw)
In-Reply-To: <pan$b6f9d$aacea77$9bd67de4$294bec3e@cox.net>
On Thu, 2014-06-12 at 07:45 +0000, Duncan wrote:
> Gui Hecheng posted on Thu, 12 Jun 2014 10:24:59 +0800 as excerpted:
>
> > When deal with the p & q stripes for data profile raid6, chunk-recover
> > forgets to insert them into the chunk record. Just insert them back
> > freely.
> > Also wrap the inert procedure into a new function, fill_chunk_up.
>
> If there's a v2 anyway: s/inert/insert/ ?
Oh, yes, 'insert' is the right thing. Thanks very much! I'll send a v2.
-Gui
> (For a moment I was contemplating the reasons one might wrap a stub,
> which is how I was translating inert procedure. Then it hit me... =:^)
>
prev parent reply other threads:[~2014-06-12 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 2:24 [PATCH 1/3] btrfs-progs: fix missing parity stripe for raid6 in chunk-recover Gui Hecheng
2014-06-12 2:25 ` [PATCH 2/3] btrfs-progs: fix max mirror number error for chunk-recover Gui Hecheng
2014-06-25 2:17 ` Eric Sandeen
2014-06-25 2:20 ` Wang Shilong
2014-06-25 2:22 ` Gui Hecheng
2014-06-25 5:14 ` Eric Sandeen
2014-06-25 5:25 ` Eric Sandeen
2014-06-25 6:51 ` Gui Hecheng
2014-06-12 2:25 ` [PATCH 3/3] btrfs-progs: cleanup unused assignment " Gui Hecheng
2014-06-12 7:45 ` [PATCH 1/3] btrfs-progs: fix missing parity stripe for raid6 in chunk-recover Duncan
2014-06-12 8:11 ` Gui Hecheng [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=1402560684.28107.2.camel@localhost.localdomain \
--to=guihc.fnst@cn.fujitsu.com \
--cc=1i5t5.duncan@cox.net \
--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).