From: Wido den Hollander <wido@42on.com>
To: Nathan Cutler <ncutler@suse.cz>, Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: preparing v0.80.11
Date: Wed, 03 Jun 2015 20:22:01 +0200 [thread overview]
Message-ID: <556F45C9.7080003@42on.com> (raw)
In-Reply-To: <5564D772.9080909@suse.cz>
On 05/26/2015 10:28 PM, Nathan Cutler wrote:
> Hi Loic:
>
> The first round of 0.80.11 backports, including all trivial backports
> (where "trivial" is defined as those I was able to do by myself without
> help), is now ready for integration testing in the "firefly-backports"
> branch of the SUSE fork:
>
> https://github.com/SUSE/ceph/commits/firefly-backports
>
> The non-trivial backports (on which I hereby solicit help) are:
>
> http://tracker.ceph.com/issues/11699 Objecter: resend linger ops on split
> http://tracker.ceph.com/issues/11700 make the all osd/filestore thread
> pool suicide timeouts separately configurable
> http://tracker.ceph.com/issues/11704 erasure-code: misalignment
> http://tracker.ceph.com/issues/11720 rgw deleting S3 objects leaves
> __shadow_ objects behind
>
Could I also ask for this one to be backported?
https://github.com/ceph/ceph/pull/4844
It breaks a couple of setups I know of. It's not in master yet, but it's
a very trivial fix.
> Nathan
> --
> 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
--
Wido den Hollander
42on B.V.
Ceph trainer and consultant
Phone: +31 (0)20 700 9902
Skype: contact42on
next prev parent reply other threads:[~2015-06-03 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 8:35 preparing v0.80.11 Loic Dachary
2015-05-25 10:04 ` Nathan Cutler
2015-05-26 20:28 ` Nathan Cutler
2015-05-26 20:44 ` Loic Dachary
2015-05-28 4:53 ` Wido den Hollander
2015-05-28 10:10 ` Nathan Cutler
2015-06-03 18:22 ` Wido den Hollander [this message]
2015-06-04 12:53 ` Nathan Cutler
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=556F45C9.7080003@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
--cc=ncutler@suse.cz \
/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.