From: wangyf <wangyf-fnst@cn.fujitsu.com>
To: Omar Sandoval <osandov@fb.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] btrfs: add a test of replace missing dev in diff raid
Date: Tue, 30 Jun 2015 09:51:27 +0800 [thread overview]
Message-ID: <5591F61F.7060009@cn.fujitsu.com> (raw)
In-Reply-To: <5591893B.2020309@fb.com>
On 06/30/2015 02:06 AM, Omar Sandoval wrote:
> On 06/29/2015 02:13 AM, wangyf wrote:
>> Hello, Omar:
>>
>> To update some cases to support RAID5/6 is necessary.
>> Like btrfs/011 btrfs/071 , and the man page of BTRFS-REPLACE,
>> they all should be modified.
>>
>> But equipment damage and missing device is small probability event when
>> we use disks in our daily life. So it shouldn't be so important that we let
>> _btrfs_get_profile_confilgs know it.
>> Besides, every case tests a different direction of replace is good. e.g.
>> 011 071 020 etc.
>>
>> So I think to test it in a new case is better. What is your opinion?
>>
>> cheers,
>> wangyf
> Hi, Yanfeng,
>
> Sorry, I think I might have been unclear. I definitely agree that the
> missing case should be tested in a separate test case. However, I do
> think that _btrfs_get_profile_configs should be updated so we can keep
> things in one place and make sure that all profiles are thoroughly
> tested. With _btrfs_get_profile_configs aware of RAID 5/6 and missing
> device replacement, the new test case can just make use of that instead
> of hardcoding the profiles to test. Does that sound alright?
>
> Thanks!
Hi, Omar:
I think it again, and now I think you are right.
To let _btrfs_get_profile_confilgs be aware of replace+missing
many redundant codes can be evitable.
We can use it in a new test case to test missing device.
regards.
prev parent reply other threads:[~2015-06-30 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 5:21 [PATCH] btrfs: add a test of replace missing dev in diff raid Wang Yanfeng
2015-06-26 22:24 ` Omar Sandoval
2015-06-29 9:13 ` wangyf
2015-06-29 18:06 ` Omar Sandoval
2015-06-30 1:51 ` wangyf [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=5591F61F.7060009@cn.fujitsu.com \
--to=wangyf-fnst@cn.fujitsu.com \
--cc=fstests@vger.kernel.org \
--cc=osandov@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.