CEPH filesystem development
 help / color / mirror / Atom feed
From: GuangYang <yguang11@outlook.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Upgrade/rollback
Date: Wed, 11 Feb 2015 12:09:24 +0000	[thread overview]
Message-ID: <BLU175-W8D101EDE23DCDD591ADF6DF250@phx.gbl> (raw)

Hi ceph-devel,
Recently we are trying the upgrade from Firefly to Giant and it goes pretty smoothly, however, the problem is that it does not support rollback and seems like that is by design. For example, there is new feature flag / metadata [1] added in the new version and they are persisted. As a result, the old version of software does not recognize those values and will crash themselves.

Ideally we never rollback, but for unknown reasons we couldn't fix in a timely manner, we might want to rollback first. Is that something we will consider to handle?

[1] https://github.com/ceph/ceph/commit/1fe8b846641486cc294fe7e1d2450132c38d2dba

Thanks,
Guang 		 	   		  --
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

             reply	other threads:[~2015-02-11 12:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 12:09 GuangYang [this message]
2015-02-11 15:17 ` Upgrade/rollback Gregory Farnum
2015-02-11 17:26   ` Upgrade/rollback Sage Weil
2015-02-12  7:40     ` Upgrade/rollback Ric Wheeler
2015-02-12  8:48     ` Upgrade/rollback GuangYang
2015-02-12 14:57       ` Upgrade/rollback Gregory Farnum
2015-02-13  1:45         ` Upgrade/rollback GuangYang

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=BLU175-W8D101EDE23DCDD591ADF6DF250@phx.gbl \
    --to=yguang11@outlook.com \
    --cc=ceph-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox