CEPH filesystem development
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Josh Durgin <josh.durgin@inktank.com>,
	Gregory Farnum <greg@inktank.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: rbd volume upgrades
Date: Fri, 09 Nov 2012 13:27:06 -0600	[thread overview]
Message-ID: <509D590A.2010807@inktank.com> (raw)
In-Reply-To: <CAC-hyiEx3DatO+-5GEP7DiiZZEOgyYYFfNKhW1ebSpYmo464Tw@mail.gmail.com>

On 11/09/2012 01:08 PM, Yehuda Sadeh wrote:
> On Fri, Nov 9, 2012 at 11:04 AM, Josh Durgin <josh.durgin@inktank.com> wrote:
>> On 11/09/2012 11:01 AM, Gregory Farnum wrote:
>>>
>>> I was asked today if there's a way to upgrade RBD volumes from v1 to
>>> v2. I didn't think so, but wanted
>>> 1) to make sure I'm right,
>>> 2) to ask how hard it would be,
>>> 3) to ask if we haven't done it because it didn't occur to us or
>>> because it's too hard.
>>> -Greg
>>>
>>
>> This was addressed in the original discussions about format 2.
>>
>> You need to export and then import the volume as format 2. Format 2 uses
>> different names for objects, so providing an 'upgrade' path would still
>> require copying all the data around.
>>
> Couldn't we just set a flag in the header specifying the object naming
> version, which would then only require updating the header?

That's an interesting thought.  A bit confusing, but only
to the code...

I think it's worth considering.

					-Alex


> Yehuda
> --
> 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:[~2012-11-09 19:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 19:01 rbd volume upgrades Gregory Farnum
2012-11-09 19:04 ` Josh Durgin
2012-11-09 19:06   ` Gregory Farnum
2012-11-09 19:08   ` Yehuda Sadeh
2012-11-09 19:27     ` Alex Elder [this message]
2012-11-09 19:30     ` Josh Durgin
2012-11-09 19:44       ` Yehuda Sadeh
2012-11-09 19:52         ` Alex Elder
2012-11-09 20:03         ` Josh Durgin
2012-11-09 20:09           ` Alex Elder
2012-11-09 20:26             ` Josh Durgin
2012-11-09 20:30               ` Yehuda Sadeh
2012-11-09 20:31                 ` Yehuda Sadeh
2012-11-09 20:34                   ` Josh Durgin

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=509D590A.2010807@inktank.com \
    --to=elder@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --cc=josh.durgin@inktank.com \
    --cc=yehuda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox