From: Mykola Golub <to.my.trociny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Sage Weil <sweil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ceph-users-Qp0mS5GaXlQ@public.gmane.org
Subject: Re: removing 'rados cppool' command
Date: Sat, 7 May 2016 10:06:26 +0300 [thread overview]
Message-ID: <20160507070625.GA2167@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1605061538160.1841-Wo5lQnKln9t9PHm/lf2LFUEOCMrvLtNR@public.gmane.org>
On Fri, May 06, 2016 at 03:41:34PM -0400, Sage Weil wrote:
> This PR
>
> https://github.com/ceph/ceph/pull/8975
>
> removes the 'rados cppool' command. The main problem is that the command
> does not make a faithful copy of all data because it doesn't preserve the
> snapshots (and snapshot related metadata). That means if you copy an RBD
> pool it will render the images somewhat broken (snaps won't be present and
> won't work properly). It also doesn't preserve the user_version field
> that some librados users may rely on.
>
> Since it's obscure and of limited use, this PR just removes it.
Copying a pool sometimes is useful, even with those limitations.
Until there is an alternative way to do the same I would not remove
this. A better approach to me is to move this functionality to
something like `ceph_radostool` (people use such tools only when
facing extraordinary situations so they are more careful and expect
limitations).
--
Mykola Golub
prev parent reply other threads:[~2016-05-07 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 19:41 removing 'rados cppool' command Sage Weil
[not found] ` <alpine.DEB.2.11.1605061538160.1841-Wo5lQnKln9t9PHm/lf2LFUEOCMrvLtNR@public.gmane.org>
2016-05-06 21:18 ` Yehuda Sadeh-Weinraub
2016-05-06 21:27 ` Sage Weil
2016-05-06 21:48 ` Yehuda Sadeh-Weinraub
2016-05-07 7:06 ` Mykola Golub [this message]
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=20160507070625.GA2167@gmail.com \
--to=to.my.trociny-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
--cc=sweil-H+wXaHxf7aLQT0dZR+AlfA@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.