From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <gfarnum@redhat.com>,
Patrick Donnelly <pdonnell@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: CephFS and the next jewel release v10.2.3
Date: Wed, 24 Aug 2016 23:02:04 +0200 [thread overview]
Message-ID: <57BE0B4C.6060104@dachary.org> (raw)
In-Reply-To: <CAJ4mKGbOzdxCoFhzmXmbQbs0G2MuxwSR2Qb83WkGGJNXg8TgFg@mail.gmail.com>
On 24/08/2016 22:46, Gregory Farnum wrote:
> On Wed, Aug 24, 2016 at 11:11 AM, Gregory Farnum <gfarnum@redhat.com> wrote:
>> On Tue, Aug 23, 2016 at 1:59 AM, Loic Dachary <loic@dachary.org> wrote:
>>> Hi John,
>>>
>>> The next jewel release as found at https://github.com/ceph/ceph/tree/jewel passed the fs suite (http://tracker.ceph.com/issues/16344#note-30 except for three valgrind failures). Do you think the jewel branch is ready for QE to start their own round of testing ?
>>>
>>> Cheers
>>>
>>> P.S. CC'ing Greg because John is on vacation, in case a decision is to be made before he returns.
>>
>> Ugh, I went to check these valgrind failures and they're a failed
>> mutex assert on shutdown. Let me dig into what's happening. :(
>> -Greg
>
> Hmm, we seem to have some badly-colliding backports. If you look at
> commit ac449472df2978123192d5f22247d8b8bc5efb28 and MDSRank.cc line
> 242, you'll see it does mds_lock.Unlock() twice in quick succession.
> :(
>
> One of them came in from 7c2eab19, and the other from 1d3a8168. I
> think maybe the patches got reordered in their backport order or
> something.
>
> Patrick, can you give https://github.com/ceph/ceph/pull/10847 a quick
> review? Loic, can you then run the failed tests against a backport
> branch which includes that patch?
https://github.com/ceph/ceph/pull/10847 has been pushed as part of the jewel-backports integration branch right now and I'll schedule a fs run as soon as it finishes building. Thanks for the quick fix !
> -Greg
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
next prev parent reply other threads:[~2016-08-24 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 8:59 CephFS and the next jewel release v10.2.3 Loic Dachary
2016-08-24 18:11 ` Gregory Farnum
2016-08-24 20:46 ` Gregory Farnum
2016-08-24 21:02 ` Loic Dachary [this message]
2016-08-24 21:03 ` Gregory Farnum
2016-08-25 21:13 ` Loic Dachary
2016-08-25 21:33 ` Gregory Farnum
2016-08-25 22:47 ` Loic Dachary
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=57BE0B4C.6060104@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=pdonnell@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 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.