All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
To: ceph-users-Qp0mS5GaXlQ@public.gmane.org,
	ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: v0.67.6 non-release
Date: Fri, 14 Feb 2014 18:29:03 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1402141810381.20749@cobra.newdream.net> (raw)

Hi all,

We built a v0.67.6 but discovered two problems shortly after it was pushed 
out to the public repository.  We've pulled the packages from the 
repositories (you'll now find 0.67.5 there).  

We will have a v0.67.7 shortly that addresses the problem but not until we 
run it through its paces and verify the upgrade will be safe.

If you installed the v0.67.6 release in the last 24 hours, and it is a 
branc new deployment, we recommend you reinstall.

If it was a live cluster that got upgraded, let us know, as you may want 
to move to a test build instead of waiting for v0.67.7.  Downgrading a 
production cluster from v0.67.6 to v0.67.5 is not recommended.

Specifically, there were two issues with the v0.67.6 build:

 1- A recently backported librbd cache behavior change leaks memory.  
    This is now reverted for v0.67.7.
 2- A backported fix for xattr behavior did not include a follow-on fix, 
    which can cause an incorrect ENOENT reply from the cluster.  The 
    follow-on fix is now in the dumpling branch.

Fixes for both issues are queued up, but as I said we want to make sure it 
goes through its paces in QA before building a follow-on v0.67.7 release.

Thanks!
sage

                 reply	other threads:[~2014-02-15  2:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.DEB.2.00.1402141810381.20749@cobra.newdream.net \
    --to=sage-4gqslpfj+cxbdgjk7y7tuq@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.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 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.