From: Stefan Priebe <s.priebe@profihost.ag>
To: Dan Mick <dan.mick@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: bug in rbd rename command?
Date: Fri, 19 Apr 2013 22:29:11 +0200 [thread overview]
Message-ID: <5171A917.6040704@profihost.ag> (raw)
In-Reply-To: <5171A883.2040006@inktank.com>
Am 19.04.2013 22:26, schrieb Dan Mick:
> It's arguable, but we wanted to treat source and destination pools
> separately in general.
>
> Note that you can also specify images as POOLNAME/a and POOLNAME/b.
Sure i know that. But then -p does not make sense at all. Nobody want to
use:
rbd -p POOLFORA rename a POOLFORB/b
Wouldn't it be constant to expand this for b? I mean renaming from poola
to poolb isn't supported anyway ;-)
Greets,
Stefan
> On 04/19/2013 12:28 AM, Stefan Priebe - Profihost AG wrote:
>> Hi,
>>
>> if i issue rbd -p POOLNAME ... rename a b
>>
>> It uses the POOL for a but not for b.
>>
>> Output is then:
>> rbd: mv/rename across pools not supported
>> source pool: vmstorssd1 dest pool: rbd
>>
>> Shouldn't it use the pool provided by -p for both?
>>
>> Stefan
>> --
>> 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
>>
next prev parent reply other threads:[~2013-04-19 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 7:28 bug in rbd rename command? Stefan Priebe - Profihost AG
2013-04-19 20:26 ` Dan Mick
2013-04-19 20:29 ` Stefan Priebe [this message]
2013-04-19 20:33 ` Sage Weil
2013-04-19 20:34 ` Stefan Priebe
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=5171A917.6040704@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.mick@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.