ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Dan van der Ster <dan@vanderster.com>, John Spray <jspray@redhat.com>
Cc: Abhishek L <abhishek.lekshmanan@gmail.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Upcoming 10.2.4
Date: Tue, 11 Oct 2016 12:48:33 +0200	[thread overview]
Message-ID: <57FCC381.1070605@dachary.org> (raw)
In-Reply-To: <CABZ+qqnOUTZun6SS4m4VpC5aMQcfvfU6W+9Po=ai-p04zMzvdw@mail.gmail.com>



On 11/10/2016 12:33, Dan van der Ster wrote:
> On Tue, Oct 11, 2016 at 12:15 PM, John Spray <jspray@redhat.com> wrote:
>> On Mon, Oct 10, 2016 at 11:59 AM, Loic Dachary <loic@dachary.org> wrote:
>>> Hi Abhishek,
>>>
>>> Since you're now release manager, it is my understanding that we'll be asking you if the release should be cut or not. I updated the issue tracking the progress of 10.2.4 accordingly. This is a heads up to let you know we'll most likely ask that question for 10.2.4 some time next week ;-)
>>
>> I've just done a test run of the following jewel PRs:
>> [11389]  mon: don't crash on invalid standby_for_fscid
>> [10997]  jewel: multimds: allow_multimds not required when max_mds is
>> set in ceph.conf at startup
>> [10958]  jewel: client: fix shutdown with open inodes
>> [10921]  jewel client: add missing client_lock for get_root
>> [10107]  jewel: client: FAILED assert(root_ancestor->qtree == __null)
>>
>> http://pulpito.ceph.com/jspray-2016-10-10_15:27:25-fs-wip-jcsp-backports-20161010-distro-basic-mira/
>>
>> No (real) failures -- can we go ahead and merge all these before 10.2.4?
>>
>> Cheers,
>> John
> 
> John/Loic, did "client: kill QuotaTree" fall off the backport radar?
> 
>   https://github.com/ceph/ceph/pull/9591/commits/161954bbfeb13d5588668637d5258221948128ea
>   http://tracker.ceph.com/issues/16066
> 
> Tracker's offline now, but AFAICT this wasn't yet backported to jewel.
> And this is unfortunate because jewel's ceph-fuse is still crashy with
> client quota enabled.

I'll make sure it lands in 10.2.4.

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre

  reply	other threads:[~2016-10-11 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 10:59 Upcoming 10.2.4 Loic Dachary
2016-10-11 10:15 ` John Spray
2016-10-11 10:33   ` Dan van der Ster
2016-10-11 10:48     ` Loic Dachary [this message]
2016-10-11 10:36   ` Loic Dachary
2016-10-11 16:59 ` Ken Dreyer
2016-10-11 17:35   ` Loic Dachary
2016-10-11 18:38 ` Orit Wasserman
2016-10-11 18:48   ` Loic Dachary
2016-10-19  9:52 ` Loic Dachary
2016-10-19 14:26   ` Jason Dillaman
2016-10-19 14:54     ` 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=57FCC381.1070605@dachary.org \
    --to=loic@dachary.org \
    --cc=abhishek.lekshmanan@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dan@vanderster.com \
    --cc=jspray@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).