linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: 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 07:45:13 +0000 (UTC)	[thread overview]
Message-ID: <pan$b6f9d$aacea77$9bd67de4$294bec3e@cox.net> (raw)
In-Reply-To: 1402539901-22779-1-git-send-email-guihc.fnst@cn.fujitsu.com

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/ ?

(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... =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  parent reply	other threads:[~2014-06-12  7:45 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 ` Duncan [this message]
2014-06-12  8:11   ` [PATCH 1/3] btrfs-progs: fix missing parity stripe for raid6 in chunk-recover Gui Hecheng

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='pan$b6f9d$aacea77$9bd67de4$294bec3e@cox.net' \
    --to=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).