From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Eric Sandeen <sandeen@redhat.com>,
Gui Hecheng <guihc.fnst@cn.fujitsu.com>,
<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] btrfs-progs: fix max mirror number error for chunk-recover
Date: Wed, 25 Jun 2014 10:20:00 +0800 [thread overview]
Message-ID: <53AA31D0.40603@cn.fujitsu.com> (raw)
In-Reply-To: <53AA313C.9010802@redhat.com>
On 06/25/2014 10:17 AM, Eric Sandeen wrote:
> On 6/11/14, 9:25 PM, Gui Hecheng wrote:
>> When run chunk-recover on a health btrfs(data profile raid0, with
>> plenty of data), the program has a chance to abort on the number
>> of mirrors of an extent.
>>
>> According to the kernel code, the max mirror number of an extent
>> is 3 not 2:
>> ctree.h: BTRFS_MAX_MIRRORS 3
>> chunk-recover.c : BTRFS_NUM_MIRRORS 2
>> just change BTRFS_NUM_MIRRORS to 3, and everything goes well.
> Wouldn't it make a lot more sense, then, to change the userspace
> macro to be called BTRFS_MAX_MIRRORS as well?
Yeah, agree, Nice review. :-)
Wang
>
> -Eric
>
>> Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
>> ---
>> chunk-recover.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/chunk-recover.c b/chunk-recover.c
>> index 9b46b0b..d5a688e 100644
>> --- a/chunk-recover.c
>> +++ b/chunk-recover.c
>> @@ -42,7 +42,7 @@
>> #include "btrfsck.h"
>> #include "commands.h"
>>
>> -#define BTRFS_NUM_MIRRORS 2
>> +#define BTRFS_NUM_MIRRORS 3
>>
>> struct recover_control {
>> int verbose;
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-06-25 2:24 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 [this message]
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
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=53AA31D0.40603@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=guihc.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).