From: Jes Sorensen <jes.sorensen@gmail.com>
To: Guoqing Jiang <gqjiang@suse.com>, Shaohua Li <shli@kernel.org>,
Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Brown, Neil" <neilb@suse.com>
Subject: Re: ANNOUNCE: mdadm 4.0 - A tool for managing md Soft RAID under Linux
Date: Thu, 12 Jan 2017 11:41:53 -0500 [thread overview]
Message-ID: <4eb83aa0-6245-d499-f18a-e8456aad9f98@gmail.com> (raw)
In-Reply-To: <587704FC.6030701@suse.com>
On 01/11/17 23:24, Guoqing Jiang wrote:
>
>
> On 01/12/2017 12:59 AM, Jes Sorensen wrote:
>> On 01/11/17 11:52, Shaohua Li wrote:
>>> On Tue, Jan 10, 2017 at 11:49:04AM -0600, Bruce Dubbs wrote:
>>>> Jes Sorensen wrote:
>>>>> I am pleased to announce the availability of
>>>>> mdadm version 4.0
>>>>>
>>>>> It is available at the usual places:
>>>>> http://www.kernel.org/pub/linux/utils/raid/mdadm/
>>>>> and via git at
>>>>> git://git.kernel.org/pub/scm/utils/mdadm/mdadm.git
>>>>> http://git.kernel.org/cgit/utils/mdadm/
>>>>>
>>>>> The update in major version number primarily indicates this is a
>>>>> release by it's new maintainer. In addition it contains a large number
>>>>> of fixes in particular for IMSM RAID and clustered RAID support. In
>>>>> addition this release includes support for IMSM 4k sector drives,
>>>>> failfast and better documentation for journaled RAID.
>>>> Thank you for the new release. Unfortunately I get 9 failures
>>>> running the
>>>> test suite:
>>>>
>>>> tests/00raid1... FAILED
>>>> tests/07autoassemble... FAILED
>>>> tests/07changelevels... FAILED
>>>> tests/07revert-grow... FAILED
>>>> tests/07revert-inplace... FAILED
>>>> tests/07testreshape5... FAILED
>>>> tests/10ddf-fail-twice... FAILED
>>>> tests/20raid5journal... FAILED
>>>> tests/10ddf-incremental-wrong-order... FAILED
>>> Yep, several tests usually fail. It appears some checks aren't always
>>> good. At
>>> least the 'check' function for reshape/resync isn't reliable in my
>>> test, I saw
>>> 07changelevelintr fails frequently.
>> That is my experience as well - some of them are affected by the kernel
>> version too. We probably need to look into making them more reliable.
>
> If possible, it could be a potential topic for lsf/mm raid discussion as
> Coly suggested
> in previous mail.
>
> Is current test can run the test for different raid level, say, "./test
> --raidtype=raid1" could
> execute all the *r1* tests, does it make sense to do it if we don't
> support it now.
We could have a discussion about this at LSF/MM, if someone is willing
to sponsor getting it accepted and we can get the right people there.
Note that the test suite also allows you to run all the 01 tests by
specifying ./test 01. I do like to see the test suite improved and made
more resilient.
Cheers,
Jes
next prev parent reply other threads:[~2017-01-12 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 1:11 Jes Sorensen
2017-01-10 17:49 ` Bruce Dubbs
2017-01-11 16:52 ` Shaohua Li
2017-01-11 16:59 ` Jes Sorensen
2017-01-12 4:24 ` Guoqing Jiang
2017-01-12 16:41 ` Jes Sorensen [this message]
2017-02-13 5:08 ` zhilong
2017-02-13 5:54 ` zhilong
2017-02-13 17:44 ` Jes Sorensen
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=4eb83aa0-6245-d499-f18a-e8456aad9f98@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=bruce.dubbs@gmail.com \
--cc=gqjiang@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=shli@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
all inboxes | Powered by JetHome®