From: Wido den Hollander <wido@42on.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: stuff for v0.56.4
Date: Wed, 06 Mar 2013 09:37:45 +0100 [thread overview]
Message-ID: <51370059.4050403@42on.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1303051503480.1162@cobra.newdream.net>
On 03/06/2013 12:10 AM, Sage Weil wrote:
> There have been a few important bug fixes that people are hitting or
> want:
>
> - the journal replay bug (5d54ab154ca790688a6a1a2ad5f869c17a23980a)
> - the - _ pool name vs cap parsing thing that is biting openstack users
> - ceph-disk-* changes to support latest ceph-deploy
>
> If there are other things that we want to include in 0.56.4, lets get them
> into the bobtial branch sooner rather than later.
>
> Possible items:
>
> - pg log trimming (probably a conservative subset) to avoid memory bloat
> - omap scrub?
> - pg temp collection removal?
> - buffer::cmp fix from loic?
>
> Are there other items that we are missing?
>
I'm still seeing #3816 on my systems. The fix in wip-3816 did not
resolve it for me.
Wido
> sage
>
> --
> 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.
Phone: +31 (0)20 700 9902
Skype: contact42on
next prev parent reply other threads:[~2013-03-06 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 23:10 stuff for v0.56.4 Sage Weil
2013-03-06 8:37 ` Wido den Hollander [this message]
2013-03-07 15:08 ` Travis Rhoden
2013-03-07 18:24 ` Yehuda Sadeh
2013-03-07 21:05 ` Bryan K. Wright
2013-03-07 21:27 ` Sage Weil
2013-03-11 15:10 ` Estimating OSD memory requirements (was Re: stuff for v0.56.4) Bryan K. Wright
2013-03-11 15:51 ` Greg Farnum
2013-03-11 18:01 ` Jim Schutt
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=51370059.4050403@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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.